Skip to content

Comments

New: [AEA-0000] - add function to scan destructive changes#531

Merged
anthony-nhs merged 11 commits intomainfrom
scan_destructive_changes
Feb 20, 2026
Merged

New: [AEA-0000] - add function to scan destructive changes#531
anthony-nhs merged 11 commits intomainfrom
scan_destructive_changes

Conversation

@anthony-nhs
Copy link
Contributor

Summary

  • Routine Change

Details

  • add function to scan for destructive changesets

@github-actions
Copy link
Contributor

This PR is linked to a ticket in an NHS Digital JIRA Project. Here's a handy link to the ticket:

AEA-0000

expect(command.input).toEqual({ChangeSetName: "cs", StackName: "stack"})
expect(logSpy).toHaveBeenCalledWith("Change set cs for stack stack has no destructive changes.")
expect(errorSpy).not.toHaveBeenCalled()
} finally {
Copy link
Contributor

Choose a reason for hiding this comment

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

this stuff should be in afterEach not try/finally

@anthony-nhs anthony-nhs enabled auto-merge (squash) February 20, 2026 16:16
@sonarqubecloud
Copy link

@anthony-nhs anthony-nhs merged commit 5d8917b into main Feb 20, 2026
17 checks passed
@anthony-nhs anthony-nhs deleted the scan_destructive_changes branch February 20, 2026 16:21
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