Identify the board App by client-id, which app-id is deprecated in favour of - #159
Open
rocklambros wants to merge 1 commit into
Open
rocklambros wants to merge 1 commit into
rocklambros wants to merge 1 commit into
Conversation
…vour of
The first live run of the workflow succeeded and annotated itself twice:
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
Both values identify the same App and neither is a secret, so this is a
rename rather than a change of trust. BOARD_APP_CLIENT_ID is set on the
board-automation environment alongside the App ID, which stays in place
so a rollback needs no settings change.
Left alone on purpose: the annotation is currently a warning and the run
it appeared on completed green. Fixing it now costs one line and avoids
finding out mid-outage which release turns the warning into a failure.
Signed-off-by: Rock Lambros <rock@rockcyber.com>
rocklambros
requested review from
GangGreenTemperTatum,
afogel,
bar-capsule,
fewdisc,
mamicidal and
sclintonowasp
as code owners
September 17, 2026 22:38
|
Thanks for this. It is queued rather than ignored. This pull request does not reference an issue carrying If this is an editorial correction, tick that box in the description and this comment stops applying. |
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
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.
Small follow-up to #157 and #158, from the first live run rather than from review.
The dry-run dispatch completed green and annotated itself twice:
BOARD_APP_CLIENT_IDis already set on theboard-automationenvironment.BOARD_APP_IDstays in place, so reverting this needs no settings change. Neither value is a secret and both identify the same App, so this is a rename rather than a change of trust.Worth doing now because the warning is currently only a warning. The alternative is discovering which release of the action turns it into a failure at 04:40 UTC on a night when the board has drifted.
Separately, a least-privilege cleanup for you
The App was granted one permission more than it needs. Its live grant reads:
repository_projectscovers repository-scoped classic projects. The reconciler never touches one: it callsgh issue list,gh pr list, and two ProjectV2 GraphQL mutations against the organization project. Removing it in the App settings costs nothing and does not require reinstalling.Installation is correctly scoped to selected repositories.