Skip to content

Conversation

miker985
Copy link
Contributor

@miker985 miker985 commented Sep 18, 2024

nginx-saml-proxy is a core piece of the example-flask-app that several MCI apps are based on.

This successfully ran and pushed a new image to our "containers" registry in GAR in this Action run

I haven't actually tested it live because I don't think there's anything about this that meaningfully impacts that.

It appears to me that the ghcr.io image wasn't even used as gcp-k8 shows nginx-saml-proxy is a docker.io image so I'll need to spin this up in dev and see if anything unfortunate happens...

REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
REGISTRY: us-docker.pkg.dev/uwit-mci-iam/containers
OWNER_IMAGE: ${{ github.repository }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updating REGISTRY is pretty straight-forward, but getting the image name right isn't.

github.repository is in this case uwit-iam/nginx-saml-proxy but we only want nginx-saml-proxy...

id: image_name
run: |
# GH=uwit-iam/nginx-saml-proxy; echo ${GH#*/} returns "nginx-saml-proxy"
echo "IMAGE_NAME=${OWNER_IMAGE#*/}" >> $GITHUB_OUTPUT
Copy link
Contributor Author

Choose a reason for hiding this comment

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

... so we compute it

@EricHorst
Copy link
Contributor

You may already be thinking of this but remember this repo is public so be thoughtful about what is hardcoded in workflows and files.
The current workflow is parameterized so that the registry, image name etc are supplied by variables. This makes the workflow very generic and doesn't reveal anything at all. We may not need to be so paranoid but wanted to remind.

@jprosser jprosser merged commit 96c3de6 into main Mar 27, 2025
1 check passed
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.

4 participants