Skip to content
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

Backport of chore(e2e): Clean up UI docker scenario into release/0.16.x #4873

Conversation

hc-github-team-secure-boundary
Copy link
Collaborator

Backport

This PR is auto-generated from #4843 to be assessed for backporting due to the inclusion of the label backport/0.16.x.

The below text is copied from the body of the original PR.


This PR is both a clean up of the UI docker e2e test scenario as well as a follow-up to #4840.

  • This scenario previously set up an extra docker container for a worker in order to generate a worker token. However, I think we need to rethink that approach as a worker token is a one-time use token and we want to run tests on each browser type
  • In the above PR, we added some variables to support an Admin UI MinIO test. One of the variables added was not necessary.

@hc-github-team-secure-boundary hc-github-team-secure-boundary force-pushed the backport/moduli-e2e-ui-docker-cleanup/badly-welcome-roughy branch from 8b31be0 to 8dd7600 Compare June 4, 2024 17:04
@hc-github-team-secure-boundary hc-github-team-secure-boundary merged commit 3d6aab0 into release/0.16.x Jun 4, 2024
@hc-github-team-secure-boundary hc-github-team-secure-boundary deleted the backport/moduli-e2e-ui-docker-cleanup/badly-welcome-roughy branch June 4, 2024 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants