Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[pull] master from Azure:master #1185

Merged
merged 1 commit into from
Dec 2, 2020
Merged

[pull] master from Azure:master #1185

merged 1 commit into from
Dec 2, 2020

Commits on Dec 2, 2020

  1. [hostcfgd] check cached state instead of the next state (#6067) 

    - Why I did it
'always_enabled' feature can still be disabled/enabled.

- How I did it
When checking if a feature is 'always_enabled', check the cached state to prevent new change to be accepted.
Fix an issue where cache value is updated before all the check is done.
Restore 'always_enabled' value in config db if someone wants to change.

Signed-off-by: Ying Xie [email protected]

- How to verify it
Without the fix, 'always_enabled' feature can be enabled or disabled without cli protection. With the protection, the change will be rejected properly.
    @yxieca
    yxieca authored Dec 2, 2020
    Configuration menu
    Copy the full SHA
    443f81f View commit details
    Browse the repository at this point in the history