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.

Sign up for GitHub

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

Jump to bottom

Support e2e armada server auth configs as env variable options #182

Open
sync-by-unito bot opened this issue Apr 7, 2023 · 0 comments
Open

Support e2e armada server auth configs as env variable options #182

sync-by-unito bot opened this issue Apr 7, 2023 · 0 comments

Comments

@sync-by-unito
Copy link

sync-by-unito bot commented Apr 7, 2023 •
edited
Loading

There are limited ways that auth will be setup for armada for CI and Development. These should be supported as an env var for the armada server component.

For example, ARMADA_CONFIG_AUTH="insecure" this config would automatically be injected https://github.com/armadaproject/armada/blob/master/e2e/setup/insecure-armada-auth-config.yaml

If the user has specified config, this would override this env var.

┆Issue is synchronized with this Jira Task by Unito
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants