Closed driosalido closed 5 months ago
Using
Crossplane version: v1.15.1 function-patch-and-transform: v0.4.0
I think we still have to cut a release with that, v0.4.0 was cut before that patch was merged
I saw that the functionality was added into the release notes , this is why I tried to use it
| Add support for toFieldPath policies, replacing upstream MergeOptions by @phisco in https://github.com/crossplane-contrib/function-patch-and-transform/pull/91
I think I know what's happening. Looking at the PR the correct value is MergeObject
instead of MergeObjects
as indicated in the documentation. Using MergeObject
seems to render correctly
Ok #102 changed the value names from singular to plural, the same PR changed the documentation but the code that implemented the changes described in the documentation have not yet been released... so although currently it works in 0.4.0
it's better to wait until the new binary is released as the correct values will be changed again
Hi! I'm trying to use the new
MergeObjects
policy option and I get the following error. The same composition without the affected patch works well.In this composition resource definition
I'm pretty sure that I've followed the documentation but I don't know why my
policy.toFieldPath
attribute gets translated intotoFieldPathPolicy
Any idea why? am I doing something wrong?