rugged halo
Different teams use different “main” branches . Eg one of them uses “trunk” as their main development branch . Another uses “develop”
(In addition to most teams which use main or master)
Would you use the annotation managed-by-origin-location, which would point from the “main” to the “develop” branch ?
midnight vault
I am not fully understanding your question. Are you using github? Are you aware that github has a default branch option. If you set this to the correct branch whether its develop, main or master, then backstage can be configured to discover catalog yaml files from the default branch.
rugged halo
I am not fully understanding your question. Are you using github? Are you aware ...
GitLab.
Okay let me clarify. If you don’t add branch into the app-config.yaml, it will auto go to the default branch, regardless of the name.
So that solved my original problem 🙂
Another issue is that some teams want to “test” their catalog-info on a test branch. Can they do that by clicking “register an existing component”
midnight vault
Im not as familliar with gitlab but I can see here that there is provision for the default branch. https://backstage.io/docs/integrations/gitlab/discovery/#configuration
rugged halo
Yeah I’m reading that rn
midnight vault
You can use register existing component for tests on a branch.
Make sure to unregister it so that the item on the default branch does not make a conflict with the branch.
rugged halo
So when we define a default branch. It is NOT using their default branch but instead using the defined branch