Skip to content
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

Merged
merged 1 commit into from
Dec 1, 2022

Conversation

oacob1
Copy link
Contributor

@oacob1 oacob1 commented Nov 23, 2022

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

Relates OR Closes #0000

Release note for CHANGELOG:

Set AWS credentials as `sensitive`

This will mark AWS Credentials as sensitive such that Terraform tools like Atlantis will not reveal new AWS credentials in github conversations. It has been raised in issue1537.

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

@hashicorp-cla
Copy link

hashicorp-cla commented Nov 23, 2022

CLA assistant check
All committers have signed the CLA.

@vinay-gopalan
Copy link
Contributor

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! 😄

@oacob1
Copy link
Contributor Author

oacob1 commented Nov 28, 2022

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?

@vinay-gopalan
Copy link
Contributor

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!

@oacob1
Copy link
Contributor Author

oacob1 commented Nov 30, 2022

hi @vinay-gopalan , I have signed the CLA and we should be good to go. Look forward seeing the change in next release!

Copy link
Contributor

@vinay-gopalan vinay-gopalan left a 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!

@vinay-gopalan vinay-gopalan merged commit fbd55d9 into hashicorp:main Dec 1, 2022
@oacob1
Copy link
Contributor Author

oacob1 commented Dec 5, 2022

hi @vinay-gopalan, do you know when will be a new release with this fix? Thank you.

@benashz benashz added this to the 3.12.0 milestone Dec 5, 2022
@vinay-gopalan
Copy link
Contributor

Hi @oacob1, this fix has been added to the 3.12.0 release milestone and is expected to be released on December 21.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants