Skip to content

fix: filter disabled regions#401

Merged
leiicamundi merged 1 commit intomainfrom
fix/disabled-aws-regions
Feb 26, 2026
Merged

fix: filter disabled regions#401
leiicamundi merged 1 commit intomainfrom
fix/disabled-aws-regions

Conversation

@leiicamundi
Copy link
Contributor

Related to https://camunda.slack.com/archives/C05S0M7KG6A/p1772100692611709
and fixes the failure of #399

This pull request improves the robustness and reliability of the permanent_resources_audit.yml workflow by adding explicit checks for AWS and Azure region accessibility before running audit steps. If a region is disabled or inaccessible, the workflow now skips auditing and related steps for that region, preventing unnecessary errors and failures.

Key changes grouped by cloud provider:

AWS region accessibility handling:

  • Added a new step to check if the AWS region is accessible before running audit steps. If the region is disabled or access is denied, the workflow skips all subsequent steps for that region.
  • Updated all relevant steps (Install Cloud Nuke, Load allowlist for region, Run Cloud Nuke in Dry-Run mode, Slack channel/message/report steps) to conditionally run only if the region is accessible. [1] [2] [3] [4] [5]

Azure region accessibility handling:

  • Added a new step to check if the Azure region is accessible before running audit steps. If the region is disabled or access is denied, the workflow skips all subsequent steps for that region.
  • Updated all relevant steps (Audit Azure Permanent Resources, Slack channel/message/report steps) to conditionally run only if the region is accessible. [1] [2] [3]

@leiicamundi leiicamundi self-assigned this Feb 26, 2026
@leiicamundi leiicamundi added the bug Something isn't working label Feb 26, 2026
Copy link

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 pull request enhances the permanent_resources_audit.yml workflow to gracefully handle disabled or inaccessible AWS and Azure regions. The workflow now checks region accessibility before running audit steps, preventing failures when regions cannot be accessed due to being disabled, not opted-in, or having permission issues.

Changes:

  • Added region accessibility checks for both AWS and Azure before running audit operations
  • Made all audit and notification steps conditional based on region accessibility status
  • Implemented consistent error pattern matching to detect common region access issues across both cloud providers

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@leiicamundi leiicamundi merged commit cdab02d into main Feb 26, 2026
84 checks passed
@leiicamundi leiicamundi deleted the fix/disabled-aws-regions branch February 26, 2026 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants