-
Notifications
You must be signed in to change notification settings - Fork 548
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
Set AWS credentials sensitive #1678
Conversation
Hi @oacob1, thanks for opening this PR! Would you mind accepting HashiCorp's Licensing Agreement? We shall then be able to get this change merged to the codebase. Thanks! 😄 |
Thank you for reviewing this @vinay-gopalan My employer Fivetran has already signed this Agreement here and Fivetran is already a partner.. Would that be good enough? |
Hi @oacob1, unfortunately it looks like our partner agreement doesn't cover OSS contributions so it'll be great if you could sign the CLA as well, thanks! |
hi @vinay-gopalan , I have signed the CLA and we should be good to go. Look forward seeing the change in next release! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thank you for your contribution to HashiCorp!
hi @vinay-gopalan, do you know when will be a new release with this fix? Thank you. |
Hi @oacob1, this fix has been added to the 3.12.0 release milestone and is expected to be released on December 21. |
Community Note
Relates OR Closes #0000
Release note for CHANGELOG:
This will mark AWS Credentials as
sensitive
such that Terraform tools likeAtlantis
will not reveal new AWS credentials in github conversations. It has been raised in issue1537.Output from acceptance testing: