Respect desired child's controlling owner reference#397
Respect desired child's controlling owner reference#397scothis merged 1 commit intovmware-labs:mainfrom scothis:child-desired-owner
Conversation
When a desired child resource has a controlling owner reference defined, we now respect that value and no longer attempt to redefine the reference. This can be useful when one of the default values needs to have a different value, or the parent resource type is not defined in the scheme. Signed-off-by: Scott Andrews <andrewssc@vmware.com>
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #397 +/- ##
=======================================
Coverage 61.36% 61.36%
=======================================
Files 17 17
Lines 2275 2275
=======================================
Hits 1396 1396
Misses 796 796
Partials 83 83
☔ View full report in Codecov by Sentry. |
|
This definitely helps, but only if I know I can avoid the |
This PR will bypass needing to lookup the type in the scheme so long as the desired child already has a controlling owner ref defined. Actually getting the underlaying behavior to work without a type registered in the scheme (or unstructured) is a bit more work and a proper fix is upstream. |
When a desired child resource has a controlling owner reference defined, we now respect that value and no longer attempt to redefine the reference.
This can be useful when one of the default values needs to have a different value, or the parent resource type is not defined in the scheme.