feat(deploy-ocpp-gateway): add optional infra-portal-context input#296
Draft
tobias0106 wants to merge 1 commit into
Draft
feat(deploy-ocpp-gateway): add optional infra-portal-context input#296tobias0106 wants to merge 1 commit into
tobias0106 wants to merge 1 commit into
Conversation
The releaser URL hardcodes the context segment as ocpp-${cluster}, which
breaks when a gateway moves to a different cluster: OCPP gateway staging
now runs on main-staging, but the blue/green releaser call still targets
the ocpp-staging context.
Adds an optional infra-portal-context input used as the context segment
when provided, falling back to the existing ocpp-${cluster} derivation —
behavior for all current callers (including production) is unchanged.
Also logs the final URL for easier verification.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
deploy-ocpp-gatewaycomposite action builds the infra-portal releaser URL with a hardcoded context segment:OCPP gateway staging has moved to the
main-stagingcluster (image + ArgoCD already migrated via service-ocpp#2978), but the blue/green releaser call still drives the oldocpp-stagingcontext.This adds an optional
infra-portal-contextinput:ocpp-${cluster}(existing behavior, so production and any other caller are unchanged)Also echoes the final URL in the job log for verification.
URL rendering (tested)
infra-portal-context: main-staginghttps://infra-portal.internal.monta.app/api/public/main-staging/ocpp-gateway-staging/create-gateway-releasehttps://infra-portal.internal.monta.app/api/public/ocpp-staging/ocpp-gateway-staging/create-gateway-releasehttps://infra-portal.monta.app/ocpp-production/ocpp-gateway-production/create-gateway-releaseThe
/api/public/:context/:namespace/create-gateway-releaseroute in infra-portal authenticates with a static token (context-independent) and resolves:contextto a kubeconfig —main-stagingis already a known context there.Follow-up
service-ocpp
deploy-gateway-staging.ymlwill passinfra-portal-context: "main-staging"and bump its pinned action SHA (separate PR, depends on this one's merge SHA). Production workflow stays untouched.Part of the ocpp-staging cluster decommission.
🤖 Generated with Claude Code