I have many packages that I publish to the internal (built-in) package repo. The packages are organized on the build server like this:
There’s a set of folders for each team, and within there each team owns several projects. When we use the AWS ECR repo feed we can specify the repo name in the package feed showing the full hierarchy and path like:
It’s very easy and clean to use the ECR repo paths.
Is there a similar way to structure the built-in repo to use paths to avoid a flat list of packages?