-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Bug]: hashicorp/aws version 5.67.0 breaks compatibility with role_arn for dynamic naming of AWS accounts #39331
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.68.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Terraform Core Version
1.9.5
AWS Provider Version
5.67.0
Affected Resource(s)
Use case - I am trying to create an AWS commercial account using credentials from the management account of an AWS Organization. Once that account is created, I want to assume a role and create a VPC in this new commercial account. My secret/access keys are saved in my credentials file under the profile of commercial.
Expected Behavior
Terraform plan should show the following
Plan: 3 to add, 0 to change, 0 to destroy.
Changes to Outputs:
new_account_id = (known after apply)
Actual Behavior
│ Error: Missing required argument
│
│ with provider["registry.terraform.io/hashicorp/aws"].new_account,
│ on provider.tf line 7, in provider "aws":
│ 7: provider "aws" {
│
│ The argument "role_arn" is required, but no definition was found.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
The below code does NOT work as is.
provider.tf
account.tf
vpc.tf
Steps to Reproduce
terraform init
terraform plan
Debug Output
https://gist.github.com/domijana/8220eb9a1040d2d03a57279764f601c3
Panic Output
No response
Important Factoids
In order to fix this issue, I specified version 5.66.0 in my provider file. I then deleted the terraform and terraform.lock.hcl files. Then I did terraform init, terraform plan, and it works.
Below code was added to the provider.tf file to fix it.
terraform {
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 5.66.0" # Specify the desired AWS provider version
}
}
}
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: