Skip to content

Update Grace period for Tokens #2020

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.

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

stephanieatte
Copy link
Contributor

Notice about Agent Token Grace Period

@render
Copy link

render bot commented Apr 11, 2023

@github-actions github-actions bot added the agent label Apr 11, 2023
Copy link
Contributor

@mbelton-buildkite mbelton-buildkite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section you're editing says that tokens can only be created through the API, but your addition sounds like someone is creating a token through the UI. Does the section need to be updated to indicate that you can create a token through the UI, too?

It is possible to create multiple agent tokens using the GraphQL API. These tokens will show up on the Agents page in the UI, but can only be managed (created or revoked) using the API.

Co-authored-by: Michael Belton <[email protected]>
@mbelton-buildkite
Copy link
Contributor

@stephanieatte, I'm not sure if you saw my comment. There's no mention of what page someone is looking at when they can use this information. Where is someone creating a token that this grace period applies to?

@stephanieatte
Copy link
Contributor Author

@mbelton-buildkite you can definitely create API token in the UI. what happens is when the user creates it in the UI. It shows on the top of the page for about 10 minutes. So some user thought it was a security breach or something happening. Because usually when you create tokens on other websites it disappears right after

@mbelton-buildkite
Copy link
Contributor

It looks like this one hasn't been updated to address where this is happening in the UI and making sure it makes sense with the rest of the page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants