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

azurerm_data_protection_backup_vault - support for immutability property #27859

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

katbyte
Copy link
Collaborator

@katbyte katbyte commented Nov 1, 2024

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

  • azurerm_data_protection_backup_vault - support for immutability property [GH-00000]

This is a (please select all that apply):

  • Bug Fix
  • New Feature (ie adding a service, resource, or data source)
  • Enhancement
  • Breaking Change

Related Issue(s)

Fixes #22238

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

@katbyte katbyte requested a review from a team as a code owner November 1, 2024 21:22
Copy link
Member

@mbfrahry mbfrahry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @katbyte, this looks good but I think we want to update some of the functionality to line up better with what the portal is doing!

Copy link
Member

@mbfrahry mbfrahry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CustomizeDiff is perfect but the way it's currently written is a breaking change if people move between versions. I've left comments for how to get it working without it being a breaking change

@@ -55,7 +55,9 @@ The following arguments are supported:

-> **Note:** The `retention_duration_in_days` is the number of days for which deleted data is retained before being permanently deleted. Retention period till 14 days are free of cost, however, retention beyond 14 days may incur additional charges. The `retention_duration_in_days` is required when the `soft_delete` is set to `On`.

* `soft_delete` - (Optional) The state of soft delete for this Backup Vault. Possible values are `AlwaysOn`, `Off` and `On`. Defaults to `On`.
* `immutability` - (Optional) The state of immutability for this Backup Vault. Possible values are `Disabled`, `Locked`, and `Unlocked`. Defaults to `Disabled`. Changing this from `Locked` to anything else forces a new Backup Vault to be created.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is more for if we want the naming to be better but I think Unlocked isn't very clear that it's actually enabling immutability. It'd be a bit more work on our end but what are your thoughts on changing Unlocked to Enabled?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think its best if we just keep it matching the API values even if the portal uses something else here despite it being confusing

Copy link
Member

@mbfrahry mbfrahry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once linting is good!

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

Successfully merging this pull request may close these issues.

Support for Immutable vaults in Azure Backup Vault
3 participants