-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
tctl sso configure github
produces an untestable connector spec
#31396
Labels
bug
enterprise
Issue specific to our enterprise customers.
test-plan-problem
Issues which have been surfaced by running the manual release test plan
Comments
tcsc
added a commit
that referenced
this issue
Sep 4, 2023
`tctl sso configure github` was producing an untestable connector spec, or at least a spec that would _always fail_ when tested with `tctl ssl test`, due to missing GitHub endpoints in the generated spec. This change adds the default GitHub endpoint URLs as default values for the endpoint flags in `tctl sso configure github` so that the produces spec is valis and testable. Note: Our WebUI appears to magically add these values when saving a connector, so this issue only really effects `tctl sso test` Includes doc update to match new output. Fixes: #31396 Changelog: `tctl sso configure github` now includes default Github endpoints
This was referenced Sep 4, 2023
Closed
Turns out this is what happens when you use an Enterprise Using an OSS See: #31397 (comment) |
Duplicate of #31387? |
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 5, 2023
`tctl sso configure github` was producing an untestable connector spec, or at least a spec that would _always fail_ when tested with `tctl ssl test`, due to missing GitHub endpoints in the generated spec. This change adds the default GitHub endpoint URLs as default values for the endpoint flags in `tctl sso configure github` so that the produces spec is valis and testable. Note: Our WebUI appears to magically add these values when saving a connector, so this issue only really effects `tctl sso test` Includes doc update to match new output. Fixes: #31396 Changelog: `tctl sso configure github` now includes default Github endpoints
github-actions bot
pushed a commit
that referenced
this issue
Sep 5, 2023
`tctl sso configure github` was producing an untestable connector spec, or at least a spec that would _always fail_ when tested with `tctl ssl test`, due to missing GitHub endpoints in the generated spec. This change adds the default GitHub endpoint URLs as default values for the endpoint flags in `tctl sso configure github` so that the produces spec is valis and testable. Note: Our WebUI appears to magically add these values when saving a connector, so this issue only really effects `tctl sso test` Includes doc update to match new output. Fixes: #31396 Changelog: `tctl sso configure github` now includes default Github endpoints
github-actions bot
pushed a commit
that referenced
this issue
Sep 5, 2023
`tctl sso configure github` was producing an untestable connector spec, or at least a spec that would _always fail_ when tested with `tctl ssl test`, due to missing GitHub endpoints in the generated spec. This change adds the default GitHub endpoint URLs as default values for the endpoint flags in `tctl sso configure github` so that the produces spec is valis and testable. Note: Our WebUI appears to magically add these values when saving a connector, so this issue only really effects `tctl sso test` Includes doc update to match new output. Fixes: #31396 Changelog: `tctl sso configure github` now includes default Github endpoints
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 8, 2023
`tctl sso configure github` was producing an untestable connector spec, or at least a spec that would _always fail_ when tested with `tctl ssl test`, due to missing GitHub endpoints in the generated spec. This change adds the default GitHub endpoint URLs as default values for the endpoint flags in `tctl sso configure github` so that the produces spec is valis and testable. Note: Our WebUI appears to magically add these values when saving a connector, so this issue only really effects `tctl sso test` Includes doc update to match new output. Fixes: #31396 Changelog: `tctl sso configure github` now includes default Github endpoints
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 8, 2023
`tctl sso configure github` was producing an untestable connector spec, or at least a spec that would _always fail_ when tested with `tctl ssl test`, due to missing GitHub endpoints in the generated spec. This change adds the default GitHub endpoint URLs as default values for the endpoint flags in `tctl sso configure github` so that the produces spec is valis and testable. Note: Our WebUI appears to magically add these values when saving a connector, so this issue only really effects `tctl sso test` Includes doc update to match new output. Fixes: #31396 Changelog: `tctl sso configure github` now includes default Github endpoints
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
enterprise
Issue specific to our enterprise customers.
test-plan-problem
Issues which have been surfaced by running the manual release test plan
Expected behavior:
Current behavior:
NOTE: The generated connector works when added to a Teleport cluster, but it looks like something is adding the missing fields when the connector is saved
Bug details:
The text was updated successfully, but these errors were encountered: