Skip to content

EIP1-13829 Deploy from main without using Github environment#11

Draft
StephenPenney wants to merge 4 commits into
mainfrom
eip1-13829-use-read-only-rule-and-avoid-dev2-environment-on-main
Draft

EIP1-13829 Deploy from main without using Github environment#11
StephenPenney wants to merge 4 commits into
mainfrom
eip1-13829-use-read-only-rule-and-avoid-dev2-environment-on-main

Conversation

@StephenPenney
Copy link
Copy Markdown

Describe your changes

Deploy from main without using Github environment

Also add todos where could switch to read only IAM Github role

Issue ticket number and link

https://mhclgdigital.atlassian.net/browse/EIP1-13829

Checklist before requesting a review

Tick all those which are done
Replace check box with ❌ if the step is not relevant for this PR

  • I double checked that ACs on the ticket are met by this code update

@StephenPenney StephenPenney force-pushed the eip1-13829-use-read-only-rule-and-avoid-dev2-environment-on-main branch from 1036d56 to c11702a Compare May 6, 2026 15:38
Copy link
Copy Markdown
Contributor

@emisto3 emisto3 left a comment

Choose a reason for hiding this comment

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

lgtm :) small comments only

bump-and-push-tag:
needs: get-latest-tag
uses: communitiesuk/eip-ero-shared-workflows/.github/workflows/bump-and-push-tag.yml@main
uses: communitiesuk/eip-ero-shared-workflows/.github/workflows/bump-and-push-tag.yml@eip1-13829-use-read-only-rule-and-avoid-dev2-environment-on-main
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.

Is this (and the others) going to be updated to main before merging?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Yes. My plan was to get this draft reviewed first to make sure the code is okay before running it on Print API then merge (after changing these back to main) once confirm it all works

Comment thread README.md
Note that this is a repository secret, not an environment secret.

The repositories should also have a repository secret `PREPROD_READ_ONLY_IAM_GITHUB_ROLE_ARN`
set to the IAM role ARN of a read only GitHub role in the AWS preprod account.
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.

Feel free to ignore but I wonder if making it clear what this is used for would make this clearer?

Suggested change
set to the IAM role ARN of a read only GitHub role in the AWS preprod account.
set to the IAM role ARN of a read only GitHub role in the AWS preprod account. This is used for actions triggered on main.

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