Enable OAuth2 UI login in e2e environment #10189
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
productionplayground configuration suffers from a chicken-and-egg problem wrt to the encryption key. Let's see if it makes sense / is possible to reproduce it in e2e tests.[EDIT] Actually, it's fine. It found it eventually. But let's see what e2e says about
skipper_oauth2_ui_login: truein e2e tests anyways.