Is this a new feature, an enhancement, or a change to existing functionality?
Enhancement
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
component_manager.nvos_password_rotation_enabled controls whether the RMS backend advertises and executes NVOS password rotation. The setting defaults to false, so a valid rotation request can return FailedPrecondition unless operators explicitly enable the gate.
The minimum supported RMS version will provide the required password-update behavior. The rollout gate will therefore no longer distinguish supported from unsupported deployments and can cause inconsistent behavior between password-update callers.
Feature Description
- Remove the stored rollout-gate state from
RmsBackend.
- Make the RMS backend report password-rotation support unconditionally.
- Remove the RMS runtime rejection based on the configuration value.
- Retain the configuration field and constructor argument as ignored compatibility inputs.
- Update operator documentation to describe the compatibility-only behavior.
- Add tests for omitted, false, and true configuration values and for RMS construction with the legacy value set to false.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
Enhancement
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
component_manager.nvos_password_rotation_enabledcontrols whether the RMS backend advertises and executes NVOS password rotation. The setting defaults tofalse, so a valid rotation request can returnFailedPreconditionunless operators explicitly enable the gate.The minimum supported RMS version will provide the required password-update behavior. The rollout gate will therefore no longer distinguish supported from unsupported deployments and can cause inconsistent behavior between password-update callers.
Feature Description
RmsBackend.Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct