Add support for field defaults - #1630
Draft
Julian Gutierrez Oschmann (juli4n) wants to merge 1 commit into
Draft
Conversation
Populate default fields during both Create and Update RPC calls so that resources are stored with defaults instead of zero values. This is a much cleaner approach as it means that a) consumers don't need to be aware of the default value and b) default values can potentially change. Only ActorTemplate had defaults, but added default functions for all resources so that all RPC handlers are wired up Note that
Julian Gutierrez Oschmann (juli4n)
marked this pull request as draft
September 12, 2026 23:01
Julian Gutierrez Oschmann (juli4n)
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Populate default fields during both Create and Update RPC calls so that resources are stored with defaults instead of zero values. This means that a) consumers don't need to be aware of the default value and b) default values can potentially change.
Only
ActorTemplatehad defaults, but added default functions for all resources so that all RPC handlers are wired upNote that optional fields with defaults need to be tagged as
+k8s:required. This is because they are required when they are stored in the DB. This is different than required from the client perspective.Part of #1593