Skip to content

fix(ci): make partition layer deployment resumable - #8440

Open
dreamorosi wants to merge 1 commit into
ci/retire-python39-layer-automationfrom
ci/resumable-partition-deployment
Open

fix(ci): make partition layer deployment resumable#8440
dreamorosi wants to merge 1 commit into
ci/retire-python39-layer-automationfrom
ci/resumable-partition-deployment

Conversation

@dreamorosi

Copy link
Copy Markdown
Contributor

Issue number: closes #8433

Summary

Changes

  • Validate partition deployment inputs before any AWS operation.
  • Preflight immutable target versions and require the expected preceding version before publication.
  • Treat existing matching versions as resumable no-ops and repair missing public permissions.
  • Separate publication, permission creation, and final SHA and visibility verification.
  • Disable matrix fail-fast, add safe download retries, and make artifacts overwrite-safe.
  • Preserve target metadata after partial failures for recovery.
  • Complete the reusable workflow partition input.

User experience

Maintainers can safely rerun a partially completed China or GovCloud deployment without republishing successful layers at the next immutable version. Existing versions must match the commercial SHA and visibility, missing public permissions can be repaired independently, and unsafe target positions fail before publication.

This PR is stacked on #8439 so deployment matrices retain only supported Python runtimes.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Preflight immutable target versions, recover missing permissions, and preserve metadata across partial failures. Validate inputs and make downloads and artifacts safe to retry without republishing completed layers.

Fixes GH-8433
@dreamorosi
dreamorosi requested a review from a team as a code owner September 4, 2026 23:06
@dreamorosi
dreamorosi requested a review from svozza September 4, 2026 23:06
@boring-cyborg boring-cyborg Bot added the github-actions Pull requests that update Github_actions code label Sep 4, 2026
@powertools-for-aws-oss-automation powertools-for-aws-oss-automation Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 4, 2026
@powertools-for-aws-oss-automation

Copy link
Copy Markdown

Not all issues are linked correctly.

Please link each issue to the PR either manually or using a closing keyword in the format fixes #<issue-number> format.

If mentioning more than one issue, separate them with commas: i.e. fixes #<issue-number-1>, closes #<issue-number-2>.

@sonarqubecloud

sonarqubecloud Bot commented Sep 4, 2026

Copy link
Copy Markdown

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

Labels

github-actions Pull requests that update Github_actions code size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tech debt: make partition layer deployment safe to resume

1 participant