You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After first coming in contact with the Repository CR I wondered, if it might be feasible to optionally allow url wildcard / prefix matching. This would change the semantics of Repository to something like Repositories.
Use cases:
Reducing configuration overhead
E.g. in an (GitHub) organization context where I trust all members / repositories, I do not have to create a Repository CR for each single repository, which in my case would be managed via GitOps.
Allowing a common set of custom parameter configurations (which seems to be merged in a recent commit) without copy-paste.
For the use cases above, I have running a common CI setup in a single namespace in mind. In my organization I do not make use of the auto-configuration of new repositories.
The text was updated successfully, but these errors were encountered:
After first coming in contact with the
Repository
CR I wondered, if it might be feasible to optionally allowurl
wildcard / prefix matching. This would change the semantics ofRepository
to something likeRepositories
.Use cases:
Repository
CR for each single repository, which in my case would be managed via GitOps.Notes:
The text was updated successfully, but these errors were encountered: