Skip to content

feat: [DTOSS-12152] Storage Account - enable Data Protection options#1848

Open
MacMur85 wants to merge 1 commit intomainfrom
feat/DTOSS-12152-enable-storage-account-data-protection
Open

feat: [DTOSS-12152] Storage Account - enable Data Protection options#1848
MacMur85 wants to merge 1 commit intomainfrom
feat/DTOSS-12152-enable-storage-account-data-protection

Conversation

@MacMur85
Copy link
Contributor

@MacMur85 MacMur85 commented Feb 24, 2026

Description

This PR introduces the data protection features, including Point-in-Time Restore (PITR), container soft delete, and file share soft delete, to the Azure Storage Account resources.
The implementation consists of this PR, and another one in the Templates repository (PR282).

Context

New variables included in the Storage Account module:

- blob_properties_change_feed_enabled (template default: false)
- blob_properties_restore_policy_days (template default: null)
- container_delete_retention_policy_days (template default: null)
- share_properties_retention_policy_days (template default: null)

The deployments below were conducted with specific values set by the implementation on the Cohort Manager repository side.

Successful deployments in Sandbox environment:

  • Audit before:
image
  • Audit plan:
image
  • Audit after:
image
  • Core before:
image
  • Core plan:
image
  • Core after:
image

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@github-actions
Copy link

Your Pull Request title must meet the conventional commit standards, please see the following documentation - https://www.conventionalcommits.org/en/v1.0.0/#specification

@MacMur85 MacMur85 changed the title feat:[DTOSS-12152] Storage Account - enable Data Protection options feat: [DTOSS-12152] Storage Account - enable Data Protection options Feb 24, 2026
@github-actions
Copy link

github-actions bot commented Feb 24, 2026

Unit Test Results

✔️ Tests 1014 / 1014 - passed in 66.1s
📝 Coverage 47.1%
📏 4780 / 10450 lines covered 🌿 1171 / 2186 branches covered
🔍 click here for more details

✏️ updated for commit c4a3a6a

@MacMur85 MacMur85 force-pushed the feat/DTOSS-12152-enable-storage-account-data-protection branch 2 times, most recently from 447f19a to f9cc333 Compare February 26, 2026 11:56
@stephhou stephhou added the Non-functional change A change that does not change any functions. Mainly config or database changes label Feb 26, 2026
@MacMur85 MacMur85 force-pushed the feat/DTOSS-12152-enable-storage-account-data-protection branch 2 times, most recently from f888daf to ca0752a Compare March 6, 2026 09:52
@MacMur85 MacMur85 force-pushed the feat/DTOSS-12152-enable-storage-account-data-protection branch from ca0752a to c4a3a6a Compare March 6, 2026 09:54
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 6, 2026

@MacMur85 MacMur85 marked this pull request as ready for review March 6, 2026 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Non-functional change A change that does not change any functions. Mainly config or database changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants