Skip to content

Update severity level for public access warnings in Azure storage hea…#24

Open
answersamir wants to merge 1 commit intorunwhen-contrib:mainfrom
answersamir:sev-fixes
Open

Update severity level for public access warnings in Azure storage hea…#24
answersamir wants to merge 1 commit intorunwhen-contrib:mainfrom
answersamir:sev-fixes

Conversation

@answersamir
Copy link
Copy Markdown

…lth runbook to enhance issue prioritization.

…lth runbook to enhance issue prioritization.
Copilot AI review requested due to automatic review settings July 10, 2025 06:29
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR increases the priority of public-access warnings within the Azure storage health runbook.

  • Bumps severity for public access findings from 3 to 4 to reflect higher issue priority.
Comments suppressed due to low confidence (2)

codebundles/azure-storage-health/runbook.robot:230

  • Update any runbook or repository documentation that describes severity levels so that the new level 4 entry is defined and users understand its meaning.
            ...    severity=4

codebundles/azure-storage-health/runbook.robot:230

  • Add or update automated tests to verify that the runbook correctly emits severity 4 for public-access containers, ensuring higher-priority alerts are flagged as intended.
            ...    severity=4

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