Is your feature request related to a problem?
Currently, there is no way to specify Updatecli manifest execution dependency because Updatecli
will read every manifest and load them as a array. As defined in the files pkg/core/engine/main.go
at line 21. Then for each configuration, it looks for autodiscovery configuration and any generated
manifest are happened to the list of configuration. This prevents us to order manifest execution for example using
file names starting with number.
Solution you'd like
Since the configuration is an array we could sort them based on a parameter but right now we don't have such parameter.
We have the parameter pipelineid but it's used to group configuration from different files together.
We could introduce two parameters
- id that store a unique manifest id, which is by default set to the hash of the manifest.
- dependson similar to the depends on the resource which always to reference id to define ordering.
Alternatives you've considered
I could think about a best way to handle this
Anything else?
No response
Reactions are currently unavailable
Is your feature request related to a problem?
Currently, there is no way to specify Updatecli manifest execution dependency because Updatecli
will read every manifest and load them as a array. As defined in the files pkg/core/engine/main.go
at line 21. Then for each configuration, it looks for autodiscovery configuration and any generated
manifest are happened to the list of configuration. This prevents us to order manifest execution for example using
file names starting with number.
Solution you'd like
Since the configuration is an array we could sort them based on a parameter but right now we don't have such parameter.
We have the parameter pipelineid but it's used to group configuration from different files together.
We could introduce two parameters
Alternatives you've considered
I could think about a best way to handle this
Anything else?
No response