Skip to content

fix: temporarily skip publishing to ME regions#11

Merged
macdonst merged 1 commit intomainfrom
aws-me
Mar 2, 2026
Merged

fix: temporarily skip publishing to ME regions#11
macdonst merged 1 commit intomainfrom
aws-me

Conversation

@macdonst
Copy link
Copy Markdown
Contributor

@macdonst macdonst commented Mar 2, 2026

The ME aws regions are currently down so skip publishing to them for now.

Signed-off-by: Simon MacDonald <simon.macdonald@gmail.com>
@macdonst macdonst requested a review from ryanbethel March 2, 2026 17:26
Copy link
Copy Markdown
Contributor

@ryanbethel ryanbethel left a comment

Choose a reason for hiding this comment

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

Looks good. Left a comment as a note for future us.

Comment thread scripts/lib.js
let regions = results
.map(({ Value }) => Value)
.filter(r => !r.startsWith('cn-') && !r.startsWith('us-gov-'))
// TODO Remove next line when ME AWS regions are back up
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this is good for now. I will mention so we will hopefully remember that if we publish and a layer is skipped of a region (either because the publish workflow fails intermittently or in this case we are explicitly skipping) then it can mess up the auto versioning of the layers. Like if we just publish another update we may end up with one region that is named <stuff>:3 and the rest are <stuff>:4.

@macdonst macdonst merged commit 68549ce into main Mar 2, 2026
15 checks passed
@macdonst macdonst deleted the aws-me branch March 2, 2026 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants