This issue - https://github.com/crossplane-contrib/function-cue/issues/79 - around injecting multiple fields is quite cumbersome and problematic for users. Allowing the EnvironmentConfigs created on Compositions to be converted into CUE and made available would alleviate this problem.
There may still be a use case for also injecting multiple nested fields as is requested in issue #79 but this seems to require a more native crossplane solution
How could this Function help solve your problem?
multiple nested fields could be better alleviated with the conversion of the Environment Configs into CUE it can be injected into the build through an #Env variable, thus allowing multiple injected variable configurations for environments
This should be fairly straightforward to do with cuecontext
What problem are you facing?
This issue - https://github.com/crossplane-contrib/function-cue/issues/79 - around injecting multiple fields is quite cumbersome and problematic for users. Allowing the EnvironmentConfigs created on Compositions to be converted into CUE and made available would alleviate this problem.
There may still be a use case for also injecting multiple nested fields as is requested in issue #79 but this seems to require a more native crossplane solution
How could this Function help solve your problem?
multiple nested fields could be better alleviated with the conversion of the Environment Configs into CUE it can be injected into the build through an
#Envvariable, thus allowing multiple injected variable configurations for environmentsThis should be fairly straightforward to do with cuecontext