Add a new storage container for config

[somesylvie]

Description

• Add a new storage container for config and exempt it from the retention policy (config shouldn't be deleted, PHI should)
• Update the timer trigger function to send a message that matches the config label
• Create initial config for local

Issue

CDCgov/trusted-intermediary#1082

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Configuration Clarity The new storage container 'config' is added but not explicitly exempted in the retention policy comments or code. This might lead to confusion or errors in understanding the policy's scope.

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add the new config container to the retention policy exemption list Ensure that the new config_container is explicitly exempted from the retention policy by adding its prefix to the prefix_match list in the azurerm_storage_management_policy resource. operations/template/storage.tf [81] -prefix_match = ["sftp/", "sftp-dead-letter/"] +prefix_match = ["sftp/", "sftp-dead-letter/", "config/"] Suggestion importance[1-10]: 8 Why: The suggestion correctly identifies a potential oversight in the PR where the newly added 'config' container might inadvertently be affected by the retention policy. Adding it to the 'prefix_match' list ensures it is exempt, thus preventing unintended deletions.	8

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[pluckyswan]

LGTM!