Add Sensitive flag to private ssh_key properties #11984
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When generating Terraform plan outputs for OpsWorks resources that use
custom_cookbooks
, the privatessh_key
is output directly to the console. You can see below thepassword
is already obfuscated; however, thessh_key
will be printed and potentially stored in any CI/CD output or other Terraform pipelines. This property is already ignored from drift-detection because the AWS API does not return this value, given its sensitive nature.This PR affects
aws_opsworks_instance
andaws_opsworks_application
resources.With this PR, Terraform plans will now look like the following, with the private
ssh_key
properly hidden:Community Note
Release Note
Release note for CHANGELOG:
Acceptance Test
Output from acceptance testing: