lovely plugin does not support ../ in kustomization.yaml about argocd-lovely-plugin HOT 6 CLOSED

Please see #66 and the resolution of that. See if that works for you.

from argocd-lovely-plugin.

@Joibel thank you! whole sale change in functionality is unexpected XD
Btw how does copying the directory prevent racing conditions tho?
when you merge it back into the final collection of yaml, the newly processed thing may step on something already generated earlier by another thread no?

on another note having trouble finding documentation and example of lovely plugin post processors (plugins on yaml)
will continue hunting around...

from argocd-lovely-plugin.

It's currently not the default behaviour. I'd like to remove the requirement to configure this, but I haven't decided how.
The copy of the directory is not to prevent race conditions. It is to prevent lovely running and modifying the directory, and then being asked to run again in the same directory, where the files will have been already modified by the first run.
Lovely doesn't merge it back into anything, it takes the yaml, renders it to the final version of yaml in memory and feeds that in memory copy directly to ArgoCD to put in your cluster. ArgoCD will separate up the individual application rendering to prevent the applications from interfering with each other. The lock is just because we're performing git operations to reset the repository back to how it should be, and ArgoCD tell us to take that lock if we want to do that.

Plugin documentation is here and there is a noddy example here (see env.txt for configuring it)

from argocd-lovely-plugin.

Thank you for this explanation Joibel! I now understand should the parent location's contents change, it can make the rendering of this application's yaml inconsistent.

from argocd-lovely-plugin.

(and thus "locking" on the plugin may not be a heavy as i thought it would be)

from argocd-lovely-plugin.

I apologize. I was confused. will recheck. thanks again Joibel!

from argocd-lovely-plugin.