-
Notifications
You must be signed in to change notification settings - Fork 9k
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_codebuild_project environment_variable type support for SECRETS_MANAGER #11331
Comments
A recent update to codebuild has deprecated the method we were using to pull secrets as environment variables via our build spec. We found a solution was to manually add the environment variables in the aws console and specify the Secrets Manager as their type. Of course with this method, when re running terraform for our codebuild we remove these environment variables and have to re add them manually. This Issue would solve our problem. |
Support this has been merged and will release with version 2.62.0 of the Terraform AWS Provider, later this week. 👍 |
This has been released in version 2.62.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 for triage. Thanks! |
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! |
Community Note
Description
The value
SECRETS_MANAGER
should be a valid value for thetype
field of anenvironment_variable
for anaws_codebuild_project
.New or Affected Resource(s)
aws_codebuild_project
environment_variable
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: