Passing vars/templates/data between git-included deployments

[senbax-admin]

Command

• check-image-updates
• delete
• deploy
• diff
• helm-pull
• helm-update
• list-images
• list-targets
• poke-images
• prune
• render
• seal
• validate
• version

Who are you?

No response

What do you want to do?

I could not find any way to pass any data between git included deployments.

I tried multiple approaches:

• Using variables from sub-deployments included via git -> Does not work. Maybe we could add smth like expose: true to expose vars to the parent deployment?
• Using templates with onlyRender: true from sub-deployments included via git f.e. with load_template() -> I could not find a path to load any templates from sub-deployments. However this does work fine with include: instead of git:. The docs only mention that you cannot use templates from the parent deployment. Maybe dynamic path/tag variables #372 could help getting the path of git-included deployments?
• Using ConfigMaps or Secrets with clusterConfigMap / clusterSecret variable sources -> does not work as noted in the docs.

I included barrier: true between all deployment items and added waitReadiness: true to all kustomize deployments.
Am i missing something or is there currently no way to pass any data?

Why do you need that?

There are many use cases where passing data between deployments is necessary.

[codablock]

@senbax-admin Sorry for the late response, I somehow missed this issue. Is this still relevant?

Generally, all git included sub-deployment inherit the templating context from the parent, meaning that all variables should be available. Files can currently not be shared between projects, as I implement some strict protections to avoid leaving a git project.