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

Make options to define/generate app-config's baseUrls and backendSecret in CR #354

Open
gazarenkov opened this issue May 7, 2024 · 1 comment
Labels
jira Issue will be sync'ed to Red Hat JIRA kind/feature

Comments

@gazarenkov
Copy link
Member

Context:
To make Backstage plugins work correct app-configs fields: app.baseUrl, backend.baseUrl, backend.cors.origin (usually all of them have the same value) should be properly configured based on route/ingress on top of Backstage deployment.
The same thing for backend.auth.key.secret - it should be configured with (usually random) string.
For the time being the only way for Operator is to create a configMap with this configuration and Secret with backend auth secret value. It should be done for every installation.

To improve UX, avoiding User of creating extra objects and associating them with CR, we can make Operator do that.
Here is the initial proposed changes in Backstage CR API

@github-actions github-actions bot added the jira Issue will be sync'ed to Red Hat JIRA label May 7, 2024
@rm3l
Copy link
Member

rm3l commented May 15, 2024

This makes sense, as pointed out in the past in #113. Additional things to keep in mind with the URLs:
#113 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira Issue will be sync'ed to Red Hat JIRA kind/feature
Projects
None yet
Development

No branches or pull requests

2 participants