Andrew Keesler 50f9b434e7 SameIssuerHostMustUseSameSecret is a valid OIDCProvider status ... I saw this message in our CI logs, which led me to this fix. could not update status: OIDCProvider.config.supervisor.pinniped.dev "acceptance-provider" is invalid: status.status: Unsupported value: "SameIssuerHostMustUseSameSecret": supported values: "Success", "Duplicate", "Invalid" Also - correct an integration test error message that was misleading. Signed-off-by: Andrew Keesler <akeesler@vmware.com>		2020-12-15 11:53:53 -05:00
..
authentication.concierge.pinniped.dev_jwtauthenticators.yaml	Add JWTAuthenticator API type	2020-12-08 15:41:48 -05:00
authentication.concierge.pinniped.dev_webhookauthenticators.yaml	Put all of our APIs into a "pinniped" category, and never use "all".	2020-11-12 16:26:34 -06:00
config.concierge.pinniped.dev_credentialissuers.yaml	Put all of our APIs into a "pinniped" category, and never use "all".	2020-11-12 16:26:34 -06:00
config.supervisor.pinniped.dev_oidcproviders.yaml	SameIssuerHostMustUseSameSecret is a valid OIDCProvider status	2020-12-15 11:53:53 -05:00
idp.supervisor.pinniped.dev_upstreamoidcproviders.yaml	Add spec.tls field to UpstreamOIDCProvider API.	2020-11-16 20:23:20 -06:00