Adding support for project name aliases and project grouping 🎉

[DavidVujic]

The latest version of the CLI and the Poetry plugin now have support for configuring Project name aliases, and Project groups.

Project alias

This is useful for Monorepos with many and/or very long project names. Using an alias for a project name can improve the visualization when running the poly commands (such as poly info).

If there is an alias configured, it will be used in the tables instead of the project name.

Configure it in the root-level workspace.toml (or if you prefer the root-level pyproject.toml):

[tool.polylith.projects.alias]
my-api-project-name-with-a-long-name = "api"
my-kafka-handler-project-service = "kafka-handler"

Groups

This is useful for teams using Domain Driven Design practices, such as bounded contexts, or have project types to separate individual projects in a Monorepo. In the Polylith context, the grouping of projects can now be used to filter out the poly info view by group(s).

This command will display the Workspace information, but will filter out the brick-project matrix in poly info to only show the projects in the selected group(s). You can add one or several groups to the command option.

poly info --group purchase
# or --group purchase, order, something-else

Configure it in the root-level workspace.toml (or if you prefer the root-level pyproject.toml):

[tool.polylith.projects.groups]
purchase = ["project-a", "project-c"]
order = ["the-order-project", "project-x"]

A project can be in one, none or several projects.

The changes are avaliable in the CLI v1.44 and the Poetry plugin v1.50.