This PR adds a new late-init API to skip already filled field in spec.initProvider.
Even though a field is specified in initProvider, it is late-init for forProvider. This can cause problems in some cases because forProvider is more powerful. With this new configuration API, the late-init operation of the field in forProvider can be skipped for fields set in initProvider.
Description of your changes
This PR adds a new late-init API to skip already filled field in
spec.initProvider
.Even though a field is specified in initProvider, it is late-init for forProvider. This can cause problems in some cases because
forProvider
is more powerful. With this new configuration API, the late-init operation of the field inforProvider
can be skipped for fields set ininitProvider
.I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
Tested in provider-aws by using this configuration. The example configuration for aws ec2.Subnet resource:
Generated
LateInitialize
function: