How to organize built-in repo packages

I have many packages that I publish to the internal (built-in) package repo. The packages are organized on the build server like this:

foo/bar/package1
foo/bar/package2
foo/bar/other/package1
foo/bar/other/package2
foo/other_bar/package1
foo/other_bar/package2
some/other/package1
some/other/package2

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:
some/repo/path/to/my/image

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?

Hi Eric,

Thanks for getting in touch! There isn’t a way to structure the built-in repo itself to contain multiple folders, though you could set up some additional external feeds where each would point to a specific local directory.

Let me know if that helps you get the behavior you’re after, or if you have any further questions or concerns moving forward. :slight_smile:

Best regards,

Kenny