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

Add a status variable for the AWS access key in the iam-user module #314

Closed
simonweil opened this issue Nov 22, 2022 · 3 comments · Fixed by #315
Closed

Add a status variable for the AWS access key in the iam-user module #314

simonweil opened this issue Nov 22, 2022 · 3 comments · Fixed by #315

Comments

@simonweil
Copy link
Contributor

Is your request related to a new offering from AWS?

Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

  • Yes ✅: It exists for years

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_access_key#status

Is your request related to a problem? Please describe.

Yes, I need to disable a key but can't via the module, and if I disable manually then when I apply TF again it's reactivated.

Describe the solution you'd like.

A new variable for the key status

Describe alternatives you've considered.

None

Additional context

Screen Shot 2022-11-23 at 1 17 03

@simonweil simonweil changed the title Add a status variable for the AWS access key Add a status variable for the AWS access key in the iam-user module Nov 22, 2022
@antonbabenko
Copy link
Member

This issue has been resolved in version 5.9.0 🎉

@simonweil
Copy link
Contributor Author

Thank you guys!

@github-actions
Copy link

github-actions bot commented Jan 2, 2023

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants