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

Use Radix Oauth2 as a feature instead of as a component in Radix Web Console #1117

Closed
18 tasks done
Richard87 opened this issue Oct 22, 2024 · 0 comments · Fixed by #1151, #1150, equinor/radix-flux#2478, equinor/radix-operator#1237 or #1152
Assignees

Comments

@Richard87
Copy link
Contributor

Richard87 commented Oct 22, 2024

To simplify management and reduce scripts, use the oauth2 feature instead of the component in Web Console.

  • Configure OAUTH feature -> radixconfig.yaml
  • Rewrite nginx config (dev)

Start

Release pr environment

  • Update app to use new radixconfig file (radixconfig.ENV.yaml)
  • resume flux (will remove old ingress)
  • update redirect urls in terraform (run terraform in post-clusters
  • run build-deploy (master and release) rx create pipeline-job build-deploy --branch master --application radix-web-console
  • Configure new secrets (Run update_auth_proxy_secret_for_console.sh)
  • make sure new ingress is in use

Environments

  • Dev
  • Playground
  • C2
  • Platform

After release

@Richard87 Richard87 self-assigned this Oct 22, 2024
@Richard87 Richard87 changed the title move radix-web-console to radix-oauth2 feature Use Radix Oauth2 as a feature instead of as a component in Radix Web Console Oct 22, 2024
@Richard87 Richard87 added the refinement needed Refinement needed label Oct 22, 2024
@emirgens emirgens removed the refinement needed Refinement needed label Oct 22, 2024
@Richard87 Richard87 self-assigned this Dec 5, 2024
@Richard87 Richard87 reopened this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment