feat: moved runtime defaults to spec status, fixes RHOAIENG-15033 #152
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
Signed-off-by: Dhiraj Bokde <[email protected]>
dhirajsb
force-pushed
the
feat/runtime-defaults
branch
from
d053fcf to
393af97
Compare
Al-Pragliola
approved these changes
Oct 25, 2024
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.
Description
Moved runtime default property values to spec status field json string
specDefaultsThe field is primarily for diagnostics to be able to troubleshoot operator behavior.
The generated resources (Deployments, etc.) are not affected by this change.
Fixes RHOAIENG-15033
How Has This Been Tested?
Built and tested in local cluster, also existing envtest and CI tests should pass.
Merge criteria: