fix: register DynamoDB Table template in Backstage catalog location#728
Open
csantanapr wants to merge 2 commits into
Open
fix: register DynamoDB Table template in Backstage catalog location#728csantanapr wants to merge 2 commits into
csantanapr wants to merge 2 commits into
Conversation
The customtemplates/ddb-table template was not appearing in Backstage because the manual catalog import UI silently fails to create Location entities — the backend processor cannot resolve relative paths from GitLab blob URLs submitted via the import form. Fix: add the ddb-table template directly to the existing working Location entity in templates/catalog-info.yaml, which is already polled by Backstage's catalog processor. Verified end-to-end: template loads, DynamoDB table created via ACK/kro.
Participants uncomment this line as part of the GenAI lab to register their AI-generated DynamoDB Backstage template using GitOps. Fixes #727
Contributor
|
@csantanapr this is strange, this was working fine before, and the manual importing was an alternative way to showcase this. but I agree that Gitops first may be better, but that also needs update in the instructions |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #727
Adds the DynamoDB Table template as a commented-out entry in
platform/backstage/templates/catalog-info.yaml. Participants uncomment the line as part of the GenAI lab to register their AI-generated template via GitOps.Change
- ./cicd-pipeline/template-cicd-pipeline.yaml - ./platform-entities.yaml + # Uncomment the line below to register the custom DynamoDB template (Module 1 - GenAI section) + # - ../customtemplates/ddb-table/template.yamlWhy this approach
templates/catalog-info.yamlis the only catalog location Backstage polls (confirmed inbackstage-configConfigMap)Participant flow (replaces broken import UI steps)
# - ../customtemplates/ddb-table/template.yamlincatalog-info.yamlgit add / commit / pushkubectl rollout restart deployment/backstage -n backstage && kubectl rollout status ...(~60s)Note: The companion workshop content change (updating
005_Section4_Gitlab_Push/index.en.mdto replace the broken import steps with the GitOps steps above) must be applied in the workshop content repo (GitLab).Testing
Verified end-to-end:
/backstage/create/templates/default/ddb-table-template-ack-kro✅