You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
The secrets can have activation and expiration date (datetime) set via Azure Portal or CLI.
Lacking the ability to set expiration date on the resource makes this security measure a manual task with the risk of forgetting and leaving the secrets valid forever.
Today, while setting the expiration date manually, also setting a timestamp in a tag is the best way I've found to provide the expiration information to applications configuration during terraforming.
But that is manually synchronized and error prone or relying on some external scripting.
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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Mar 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
The secrets can have activation and expiration date (datetime) set via Azure Portal or CLI.
Lacking the ability to set expiration date on the resource makes this security measure a manual task with the risk of forgetting and leaving the secrets valid forever.
New or Affected Resource(s)
Potential Terraform Configuration
Today, while setting the expiration date manually, also setting a timestamp in a tag is the best way I've found to provide the expiration information to applications configuration during terraforming.
But that is manually synchronized and error prone or relying on some external scripting.
and then to retrieve it
References
The text was updated successfully, but these errors were encountered: