fix(ci): pass meta-capi env vars through deploy workflows - #89
Merged
Merged
Conversation
The meta-capi action selects the Meta pixel by runtime namespace (prod/stage/uat) and requires an access token, but none of these were wired into the deploy workflows, so the stage deployment is missing them. Add META_PIXEL_ID / META_PIXEL_ID_STAGE / META_PIXEL_ID_UAT and META_ACCESS_TOKEN passthrough to both stage and prod deploys, following the ebs-sync naming convention, and document the secrets in example.env. META_BASE_URL / META_API_VERSION have in-code defaults and are omitted. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
maxakuru
changed the title
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.
Problem
The
meta-capiaction was merged intostagewithout its env vars wired into the deploy workflows. The action selects the Meta pixel by runtime namespace (prod/stage/uat) and requires an access token — none of which were being passed through, so the stage deployment is missing them (Missing META_PIXEL_ID or META_ACCESS_TOKEN).Changes
Add passthrough to both
deploy_stage.ymlanddeploy_prod.yml, following the ebs-sync naming convention:META_PIXEL_IDMETA_PIXEL_ID_STAGEMETA_PIXEL_ID_PRODMETA_PIXEL_ID_STAGEMETA_PIXEL_ID_STAGEMETA_PIXEL_ID_STAGEMETA_PIXEL_ID_UATMETA_PIXEL_ID_UATMETA_PIXEL_ID_UATMETA_ACCESS_TOKENMETA_ACCESS_TOKEN_STAGEMETA_ACCESS_TOKEN_PRODAll three pixel ids ship to every environment because the action picks one at runtime by namespace.
META_BASE_URL/META_API_VERSIONhave in-code defaults and are intentionally omitted.Also documents the new secrets in
example.env.Repo secrets required
META_PIXEL_ID_STAGE,META_PIXEL_ID_UAT,META_PIXEL_ID_PRODMETA_ACCESS_TOKEN_STAGE,META_ACCESS_TOKEN_PROD🤖 Generated with Claude Code