In some cases its beneficial to support multiple levels of nesting for components, beyond the level of nesting that represent the deployment target (a k8s cluster, a cloud region ), a good example for this cloud be a directory level that represent team ownership.
I use team ownership to make the repo more readable, make CODEOWNERS easier to manage and inject ownership labels to ArgoCD application via the ApplicationSet configuration.
This new feature will allow telefonistka to identify a component by multiple folders.
Description
In some cases its beneficial to support multiple levels of nesting for components, beyond the level of nesting that represent the deployment target (a k8s cluster, a cloud region ), a good example for this cloud be a directory level that represent team ownership. I use team ownership to make the repo more readable, make CODEOWNERS easier to manage and inject ownership labels to ArgoCD application via the ApplicationSet configuration.
This new feature will allow telefonistka to identify a component by multiple folders.
Type of Change
Checklist