-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
aws_spot_fleet_request not respect key_name and iam_instance_profile #492
Comments
This is still an issue with |
|
Hey @svenwltr Since the UI does it for you, it is part of the process of doing it. I personally don't think Terraform should handle it, and hide some magic. I would like to close the issue since the bug has been fixed. Tell me what you think 😄 |
@Ninir I fully agree with not doing any magic in Terraform. Also, I am already slightly annoyed by the UI, when it created some random roles in the background. Yes, this issue is resolved to me too. |
Thank you for the quick answer @svenwltr :) 👍 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This issue was originally opened by @benjah1 as hashicorp/terraform#11447. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
Terraform v0.8.4
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
To create spot fleet request,
Actual Behavior
failed: Invalid value '' for keyPairNames. It should not be blank
.Note
I also try with
key_name = false
, but it just convert to "0".The text was updated successfully, but these errors were encountered: