Relationship Checks

Relationship checks allow you to verify that a relationship is populated, as well as set constraints on how many resources can be associated through that definition. After populating your component types with rich Relationship Definitions, you can use this check to ensure your catalog's relationships are complete and correct.

For example, you may want to verify that each component has exactly one support team. This ensures that a support team is explicitly defined and verifies that no component has blurred lines of support ownership by configuring multiple supporting teams.

For less constrained metadata, you can simply ensure the relationship exists. For example, you can ensure any Runtimes are populated for each of the services you deploy.