Skip to content

The --profile flag not being read in Git Bash #281

@DuxVictorum

Description

@DuxVictorum

When running okta-aws-cli --profile <name> (or -p) from Git Bash on my Windows (10) machine, it fails to read the profile block in my okta.yaml config file. But when I run the same command in cmd.exe or Powershell, it works correctly. When I don't pass the -p flag, it runs just fine in Git Bash and reads the default config block in my okta.yaml.

I work on projects in a Linux cloud environment, but I mostly use my Windows machine to connect to that environment (via Appgate). For ease of going back and forth, I like to use Git Bash as much as possible. Is there something in how Go is processing the -p flag (perhaps in cmd/root/root.go?) that Git Bash interferes with?

In short, I would love to use this tool with the --profile flag in Git Bash, but I currently can't.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions