You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aims to resolve#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.
The CI currently runs a step which is validating swagger annotations - specifically the
Security
tag - https://github.com/coder/coder/blob/main/coderd/coderdtest/swaggerparser.go#L302For now, the tag has to be set to
CoderSessionToken
without allowing any other option, excepted ignoring the whole endpoint.Having some endpoints that are using PSK or ProvisionerKey - we need to be able to put these options too.
The text was updated successfully, but these errors were encountered: