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

feat:Move and delete decomissioned subscriptions #351

Open
knuterik-ballestad opened this issue Mar 19, 2024 · 2 comments
Open

feat:Move and delete decomissioned subscriptions #351

knuterik-ballestad opened this issue Mar 19, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request Type: Enhancement ✨ New feature or request

Comments

@knuterik-ballestad
Copy link

  • 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

When we remove a subscription using terraform, it is simply moved to the tenant root.
Isn't the management group "Decommisioned" in the ALZ mgmt-structure supposed to be the target location for such decomissioned subscriptions?

Describe the solution you'd like

I would like that the decomissioned subscriptions would be moved to the "Decommisioned"-folder after terraform removes them.
It would also be nice with functionality to clean up/remove them altogether after the "grace period" has ended.

@knuterik-ballestad knuterik-ballestad changed the title feat:Move_And_Delete_decomissioned_subscriptions feat:Move and delete decomissioned subscriptions Mar 19, 2024
@sturlabragason-devoteam
Copy link

Doesn't solve the above, but if you change the default management group to "Decommissioned" then all subscriptions removed from the config will get disabled and dropped there.

The caveat is that all newly create subscriptions also get placed there initially.

@matt-FFFFFF
Copy link
Member

Upon destroy, the AzureRM provider will cancel and move the sub to the default MG.

If you use the new AzAPI option you have more control but you must orchestrate this outside the module.

@matt-FFFFFF matt-FFFFFF self-assigned this Apr 25, 2024
@matt-FFFFFF matt-FFFFFF added enhancement New feature or request Type: Enhancement ✨ New feature or request labels Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Type: Enhancement ✨ New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants