-
Notifications
You must be signed in to change notification settings - Fork 147
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.
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
fix(setting): check both setting and definition default for possible … #2573
Merged
shuo-wu
merged 1 commit into
longhorn:master
from
james-munson:7755-setting-definition-default
Mar 8, 2024
Merged
fix(setting): check both setting and definition default for possible … #2573
shuo-wu
merged 1 commit into
longhorn:master
from
james-munson:7755-setting-definition-default
Mar 8, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shuo-wu
reviewed
Feb 9, 2024
james-munson
force-pushed
the
7755-setting-definition-default
branch
from
February 9, 2024 20:00
aece765
to
66f515e
Compare
james-munson
force-pushed
the
7755-setting-definition-default
branch
from
February 19, 2024 18:07
66f515e
to
8fd1c05
Compare
Rebased and re-pushed. |
james-munson
force-pushed
the
7755-setting-definition-default
branch
from
February 26, 2024 16:58
8fd1c05
to
5b350e9
Compare
Rebased and re-pushed. What is holding up this PR? |
ejweber
previously approved these changes
Feb 26, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
james-munson
force-pushed
the
7755-setting-definition-default
branch
from
February 27, 2024 22:21
5b350e9
to
c56bc11
Compare
james-munson
force-pushed
the
7755-setting-definition-default
branch
2 times, most recently
from
March 6, 2024 21:03
1a73a40
to
bd0c0c5
Compare
shuo-wu
approved these changes
Mar 8, 2024
…change. Signed-off-by: James Munson <james.munson@suse.com>
shuo-wu
force-pushed
the
7755-setting-definition-default
branch
from
March 8, 2024 01:36
bd0c0c5
to
32bbec0
Compare
@mergify backport v1.6.x v1.5.x |
✅ Backports have been created
|
This was referenced Mar 8, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…change.
Which issue(s) this PR fixes:
Issue longhorn/longhorn#7755
What this PR does / why we need it:
When checking a potential configmap change for default settings, check not only the current setting value but also the setting definition default value to decide whether there is a change to apply.
Special notes for your reviewer:
Additional documentation or context