Skip to content

Conversation

@nc-shahidazim
Copy link
Contributor

Description

This PR enables the secret expiry alerting feature introduced in the shared Key Vault module and removes the now‑unnecessary Key Vault dependency from the monitor action group module. Alerts are now configured directly through the module inputs, and the action group email configuration is supplied via pipeline variables instead of Key Vault.

Context

This repository already uses the shared Key Vault module but did not previously consume its new capability to generate alerts for expired or near‑expiry secrets. In addition, the monitor action group module historically depended on Key Vault to retrieve the monitoring email address. This created an unnecessary coupling and required secret lookups during deployment.
A recent update moved the monitoring email address into Azure DevOps environment variables, eliminating the need for the module to reference Key Vault.

What’s Included

  • Enabled Key Vault SecretNearExpiry and SecretExpired alert rules through the module configuration
  • Updated monitor action group usage to stop reading email addresses from Key Vault
  • Replaced email source with Azure DevOps environment variables

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

@nc-shahidazim nc-shahidazim changed the title Feat/dtoss 12086 alert secrets expiry feat: add secret expiry alerts and switch action group email to pipeline variables Jan 28, 2026
@github-actions
Copy link

github-actions bot commented Jan 28, 2026

Unit Test Results

✔️ Tests 975 / 975 - passed in 71.2s
📝 Coverage 47.76%
📏 4755 / 10228 lines covered 🌿 1167 / 2172 branches covered
🔍 click here for more details

✏️ updated for commit 325feaa

@nc-shahidazim nc-shahidazim changed the title feat: add secret expiry alerts and switch action group email to pipeline variables feat: added secret expiry alerts and switch action group email to pipeline variables Jan 28, 2026
rfk-nc
rfk-nc previously approved these changes Jan 28, 2026
@nc-shahidazim nc-shahidazim force-pushed the feat/DTOSS-12086-alert-secrets-expiry branch from 6d74540 to c8743c0 Compare January 29, 2026 09:16
@sonarqubecloud
Copy link

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants