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
As part of a Subscription vending implementation, I am designing a Sandbox environment, i.e. time-limited subscriptions; as part of this, an Expiry-Date tag is added for 3 months as part of the deployment, however with each deployment - this date gets extended.
Timestatic allows the time to be set in stone, but I want to be able to allow a subscription extension (ie someone can go into the Azure Portal and update the date on the Tags to a new extended timeline).
Describe the solution you'd like
Tags that are set on the: subscription_tags, allowed to be output and specific tags ignored for changes after deployment (ie expiry_date)
The text was updated successfully, but these errors were encountered:
Description
As part of a Subscription vending implementation, I am designing a Sandbox environment, i.e. time-limited subscriptions; as part of this, an Expiry-Date tag is added for 3 months as part of the deployment, however with each deployment - this date gets extended.
Timestatic allows the time to be set in stone, but I want to be able to allow a subscription extension (ie someone can go into the Azure Portal and update the date on the Tags to a new extended timeline).
Describe the solution you'd like
Tags that are set on the: subscription_tags, allowed to be output and specific tags ignored for changes after deployment (ie expiry_date)
The text was updated successfully, but these errors were encountered: