I'm having a problem where it seems like it is not patching from EnvironmentConfig in function-patch-and-transform.
I have a resources pipeline that basically does the same thing and want to change to use a Pipeline so that I can do some other functions and the issues I am having indicate it is not patching.
All of my spec values are pulled from either EnvironmentConfig or patches. Omitting spec.forProvider fails with required fields being missing even though they should be patched with valid values (and this works in a resources composition)
The external name doesn't get set
Not sure if in the pipeline the from or to field paths need to be different, it didn't seem like it from what I was reading.
The above works fine in a composition that is Resource mode, just not in Pipeline using function-patch-and-transform.
Just trying to validate that function-patch-and-transform handles EnvironmentConfig patches and if it does, is there something just wrong with the paths that is different in function-patch-and-transform?
I'm having a problem where it seems like it is not patching from EnvironmentConfig in function-patch-and-transform.
I have a resources pipeline that basically does the same thing and want to change to use a Pipeline so that I can do some other functions and the issues I am having indicate it is not patching.
Not sure if in the pipeline the from or to field paths need to be different, it didn't seem like it from what I was reading.
Below is basically what I have:
The above works fine in a composition that is Resource mode, just not in Pipeline using function-patch-and-transform.
Just trying to validate that function-patch-and-transform handles EnvironmentConfig patches and if it does, is there something just wrong with the paths that is different in function-patch-and-transform?
Thanks.
Dave