-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--iam-instance-profile not being parsed correctly #2643
Comments
You need to specify whether you're providing a name or an arn (or both), like so: |
Oh well now I feel foolish! Thanks for the heads-up. Perhaps a pull request for a change in the error message would be accepted? |
The original issue was resolved and documentation shows expected parameter. Since the error returned notes which parameter is at fault, we wouldn't try to parse this particular specification as incorrect. |
|
Its been 4 years and i literally ran into the same issue, its almost like were all treading down the same path, running into the same mistakes. |
This stuff is not documented. This is how the the parameter needs to be passed: |
I know this issue has been raised previously in a few similar issues (#1470 and #2392) but I'm still seeing a simliar behaviour in a very recent release
--iam-instance-profile parameter causes error
I tried with the same parameter but removing the hyphen from the argument value in case it was just the value being passed. Same result:
When I remove the --iam-instance-profile argument the command is successful.
Here's the debug output which looks as if the params are correct.
Is this a regression?
Andrew
The text was updated successfully, but these errors were encountered: