Small fixes on UX of Automated Root Rotation parameters #29685
+131
−41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Small fixes around the usability of the new automated root rotation parameters added to select Secret and Auth engines for 1.19 Enterprise.
This PR:
rotation_period
androtation_window
to be duration strings instead of just integers to be consistent with static role mechanismsrotation_period
— which would first de-register — and then setrotation_schedule
in a follow up call to re-register)disable_automated_rotation
was not passed in a request, it was treated as being set tofalse
, which would cause a de-registration. Now it will only de-register if the param is explicitly set tofalse
AutomatedRotationParams
struct in the DB Config read methodrotation_period
androtation_window
to 0, which was causing unnecessary errors)