-
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]: r/aws_amplify_app
: environment_variables
cannot be unset once configured
#39327
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Response from the upstream bug report:
fmt.Println("Deleting environment variables...")
out1, err := client.UpdateApp(ctx, &lify.UpdateAppInput{
AppId: aws.String(appId),
EnvironmentVariables: map[string]string{
" ": "",
},
}) |
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)
aws_amplify_app
Expected Behavior
When the
environment_variables
argument is removed, the existing values should be removed on the remote resource.Actual Behavior
Terraform fails with an error like:
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
environment_variables
argumentDebug Output
No response
Panic Output
No response
Important Factoids
After some initial investigation, it isn't apparent how to remove existing environment variables with the AWS SDK for Go V2 now that empty keys are no longer permitted (at one point this worked to remove values with AWS SDK for Go V1, but now this pattern does not work with either SDK). A bug report has been filed here: aws/aws-sdk-go-v2#2788.
The following acceptance test captures this workflow:
References
amplify
App aws/aws-sdk-go-v2#2788Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: