search

cnoe-io / reference-implementation-aws

This is the reference implementation of CNOE and its toolings on AWS
Apache License 2.0
57 stars 30 forks source link

How to add new Platform templates to this reference implementation. #34

Open elamaran11 opened 6 months ago

elamaran11 commented 6 months ago

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.

csantanapr commented 6 months ago

you can update the locations of templates by updating the app-config.yaml that comes from a configmap https://github.com/cnoe-io/reference-implementation-aws/blob/main/packages/backstage/dev/cm-backstage-config.yaml#L111-L115

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

elamaran11 commented 6 months ago

Thankyou, let me try this out.

elamaran11 commented 6 months ago

@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?

iron87 commented 6 months ago

@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

elamaran11 commented 6 months ago

Sounds good @iron87 Closing the issue.