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
When I minder provider update --set-attribute=auto_registration.entities.repository.enabled=true, this should mean "register all repositories, including future repositories". Today it means "make no changes to existing registration, but new repositories should be registered".
Solution Proposal
When I minder provider update --set-attribute=auto_registration.entities.repository.enabled=true, this should mean "register all repositories, including future repositories". Today it means "make no changes to existing registration, but new repositories should be registered".
Describe alternatives you've considered
No response
Additional context
No response
Acceptance Criteria
No response
The text was updated successfully, but these errors were encountered:
…when calling repo register --all
When registering all repositories, what the user really means is
"register all future and current repositories. The current invocation of
the call only registered all current ones. Let's also flip the option to
register all future repositories at the same time.
Fixes: mindersec#3817
Please describe the enhancement
When I
minder provider update --set-attribute=auto_registration.entities.repository.enabled=true
, this should mean "register all repositories, including future repositories". Today it means "make no changes to existing registration, but new repositories should be registered".Solution Proposal
When I
minder provider update --set-attribute=auto_registration.entities.repository.enabled=true
, this should mean "register all repositories, including future repositories". Today it means "make no changes to existing registration, but new repositories should be registered".Describe alternatives you've considered
No response
Additional context
No response
Acceptance Criteria
No response
The text was updated successfully, but these errors were encountered: