Setting '--prompt false' has no effect

[svaranasi-corporate]

I'm trying to use aws-iam-authenticator in a script to add a role (without human intervention). Setting the argument '--prompt false' doesn't appear to be doing anything as I still get a prompt.

Is this a bug or am I missing something?

I tried this on Git Bash on Windows, and also in an Ubuntu environment with the same results:

$ aws-iam-authenticator.exe version
{"Version":"0.6.2","Commit":"d72e1b46444d0efcb995a28c3846223b39bc4964"}

$ aws-iam-authenticator add role --prompt false --rolearn arn:aws:iam::<snip>:role/aws-reserved/sso.amazonaws.com/<snip> --groups system:masters --cluster-id <snip> --username <snip>:{{SessionName}}
Use the arrow keys to navigate: ↓ ↑ → ←
? Ready to add "add rolearn arn:aws:iam::<snip>:role/aws-reserved/sso.amazonaws.com/<snip>, username AW
<snip>:{{SessionName}}, groups [system:masters]", should we continue?:
  > No, cancel it!
    Yes, let's add "add rolearn arn:aws:iam::<snip>:role/aws-reserved/sso.amazonaws.com/<snip>, usernam
e <snip>:{{SessionName}}, groups [system:masters]"!

[svaranasi-corporate]

Anyone?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[svaranasi-corporate]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale