umbrella | 180 TypeScript projects for general purpose | Functional Programming library

You can find leaves by examining whether a node has any descendants:

the structure of my zip folder is python/app.py + requirements.txt

It should be only app.py, not python/app.py. Also there is no need for requirements.txt as lambda is not going to use it and install any packages you have listed there.

In forEach loop Use Index

I found a workaround that requires you to refactor the contents of your global ConfigMap into a template in the umbrellas chart. You won't be able to use regular values from the umbrella chart in your ConfigMap, otherwise you'll get an error when trying to render the template in a subchart; you'll have to use global values instead.

The elixir_make docs say to set the make_executable in your mix.exs to the make command installed on the system.

And then in your shell, either set the environment variables the Windows Way (If you already set the environment variables but they aren't taking, you may need to restart your terminal or VS Code), or if you're using bash, you can put them in your .bash_profile as the bakeware docs show.

Command Prompt:

So after some research I ended up creating a fresh new umbrella project with a child phoenix app inside. The issue was nowhere to be seen and everything worked properly.

With a dict comprehension to grab all attributes of hub.Image which are upper-case only:

Turns out the issue was in my children array. Since application order DOES MATTER, my PubSub child should be before Endpoint:

Try to add the annotation checksum/config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }} to avoid the executing the child chart that was not updated. So if the spec is not changed, then the application keeps running with the old configuration resulting in an inconsistent deployment.

For more information please refer to this 'Chart Development Tips and Tricks' article

Then it's expected behaviour. What's your Helm version? Since it's was totally expected behaviour in Helm 2 and there is a Issue in GitHub with similar problem as yours.

Also we can see the resolution comment that's explaining of New 3-way Strategic Merge Patches that should resolve this issue somehow, but in their examples I can't see that it was fixed with the annotation pre-upgrade. Fell free to open that issue and ping them.