Skip to content
This repository has been archived by the owner on Nov 6, 2024. It is now read-only.

Use a REST Token for trace triggering instead of API key #32

Open
beberlei opened this issue Feb 2, 2022 · 0 comments
Open

Use a REST Token for trace triggering instead of API key #32

beberlei opened this issue Feb 2, 2022 · 0 comments
Assignees
@beberlei
Labels
Loadtesting Locust

Comments

@beberlei
Copy link
Contributor

beberlei commented Feb 2, 2022

Currently two Tideways secrets need to be configured, an API Token and the projects API Key. This is confusing, since we can make this work with just one API Token to do everything.

Tideways app could have words helping people to select the right scopes for everything (since a few scopes are needed).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@beberlei beberlei

Labels
Loadtesting Locust
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@beberlei