-
Notifications
You must be signed in to change notification settings - Fork 32
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
How to add new Platform templates to this reference implementation. #34
Comments
you can update the locations of templates by updating the app-config.yaml that comes from a configmap you update the config-map wait a minute or 2 and new templates show up, make sure the template names are unique and not duplicates |
Thankyou, let me try this out. |
@csantanapr I can update the ConfigMap in backstage namespace for my demo runs but how do update or add new Platform Templates at production scale? Should i have redeploy if so how? |
You could update the Location (backstage.io/v1alpha1) file on the repo that contains the Backstage catalog, adding a new target item that contains the new Templates. You can find an example of a Location file here: https://github.com/awslabs/backstage-templates-on-eks/blob/main/catalog-info.yaml |
Sounds good @iron87 Closing the issue. |
Looks like the reference implementation on AWS deploys a docker image for backstage
public.ecr.aws/cnoe-io/backstage:v0.0.2
which is prebaked. I would like to know how to add a new Platform Engineering templates at run time to the Backstage UI like these. Appreciate any documentation.The text was updated successfully, but these errors were encountered: