github: update API tokens issue template for Maestro API#3151
Open
nuclearcat wants to merge 1 commit into
Open
github: update API tokens issue template for Maestro API#3151nuclearcat wants to merge 1 commit into
nuclearcat wants to merge 1 commit into
Conversation
The template still described the retired kernelci-backend and its admin-issued permission-scoped tokens. Update it for the Maestro API (kernelci-api): access is based on user accounts with an invite flow, reads are public and need no token, and accounts are only needed to send data. Split lab owner guidance by lab type: pull labs need an API account to poll for jobs and push results, while LAVA labs use a callback token set up in the lab itself. Also fix the stale staging URL. Signed-off-by: Denys Fedoryshchenko <denys.f@collabora.com>
nuclearcat
force-pushed
the
update-api-tokens-template
branch
from
July 16, 2026 20:41
a5d9a39 to
d16baf4
Compare
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.
The template still described the retired kernelci-backend and its admin-issued permission-scoped tokens. Update it for the Maestro API (kernelci-api): access is based on user accounts with an invite flow, reads are public and need no token, and accounts are only needed to send data.
Split lab owner guidance by lab type: pull labs need an API account to poll for jobs and push results, while LAVA labs use a callback token set up in the lab itself. Also fix the stale staging URL.