Skip to content

fix(ci): use the GitHub App client ID #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
m17kea merged 1 commit into from
Jul 16, 2026
+3 −3
Merged

fix(ci): use the GitHub App client ID #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/actionlint.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
config-variables:
- SYMPHONY_DEPLOY_APP_ID
- SYMPHONY_DEPLOY_CLIENT_ID
2 changes: 1 addition & 1 deletion .github/workflows/publish-shared.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ jobs:
id: app-token
uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v3
with:
app-id: ${{ vars.SYMPHONY_DEPLOY_APP_ID }}
client-id: ${{ vars.SYMPHONY_DEPLOY_CLIENT_ID }}
private-key: ${{ secrets.SYMPHONY_DEPLOY_APP_PRIVATE_KEY }}
owner: activeviam
repositories: shared-infrastructure
Expand Down
2 changes: 1 addition & 1 deletion ACTIVEVIAM.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,7 +170,7 @@ would expand the trust boundary unnecessarily. The App is installed only on
activeviam/shared-infrastructure with repository contents and pull-request read/write access. The
source repository holds:

- Actions variable SYMPHONY_DEPLOY_APP_ID
- Actions variable SYMPHONY_DEPLOY_CLIENT_ID
- Actions secret SYMPHONY_DEPLOY_APP_PRIVATE_KEY

This deployment App is intentionally separate from the runtime App mounted in EKS. Giving the
Expand Down