- Notifications
You must be signed in to change notification settings - Fork907
chore: improve validation of Security tag in swaggerparser#15660
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Merging this one after CI - only |
Normally this step failing shouldn't be ignored, but since it's due to postgres' site being down (maybe they host on fly.io 🤔) it's fine 👍 |
8afb10e
intomainUh oh!
There was an error while loading.Please reload this page.
Aims toresolve#15605
There's currently one option valid for the
@Security
tag in swaggerparser - which fails in the CI if we try to put any other value.At least one of our endpoints does not accept
CoderSessionToken
as an option for the authentication and so we need to add new possibilities in order to keep the documentation up-to-date.In this PR , I added
ProvisionerKey
which is the way our provisioner daemon can authenticate to the backend - also modified a bit the code to simplify other options later.