You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hubverse-transform repo will have a GitHub action that deploys an AWS Lambda package by creating the package and writing it to an S3 bucket (hubverse-assets).
Thus, that repo's GitHub actions will need to assume an AWS IAM role that has permissions to write to hubverse-assets.
Definition of done
The Pulumi code base creates an IAM role with a resource policy that specifies list/get/delete/write access to s3://hubverse-assets
The new role's trust policy specifies that the role can be assumed only via GitHub OIDC provider and only by the main branch of the hubverse-transform repo
The text was updated successfully, but these errors were encountered:
Because we're getting close to the Hubverse's GitHub org name change, will plan to hold off on this work until that's completed (because the trust policy is based on GitHub org and repo name).
Background
This is related to (and a pre-requisite for) hubverse-org/hubverse-transform#6
The hubverse-transform repo will have a GitHub action that deploys an AWS Lambda package by creating the package and writing it to an S3 bucket (
hubverse-assets
).Thus, that repo's GitHub actions will need to assume an AWS IAM role that has permissions to write to
hubverse-assets
.Definition of done
s3://hubverse-assets
main
branch of thehubverse-transform
repoThe text was updated successfully, but these errors were encountered: