This is great news, @nico. Thank you.
Let me know if you have any comments / questions.
Note that the changes may appear vast at first : 22 files, many lines, ... as reported by git
.…
Hi @nico (or other maintainers of cdist),
Is there anything I can do expedite the review process around PR #365 which I had submitted about a year ago, following your initial encouragement on…
Hi @nico (or other maintainers of cdist),
Is there anything I can do expedite the review process around this PR which I had submitted about a year ago, following your initial encouragement on…
Hi @nico,
Any idea when you could get a chance to review this? (I hope it can happen when things are still sort of fresh in my mind)
Ayhan
Hi @nico,
Tell me about it... I am quite swamped on my end, too.
Just created the PR (#365) to make sure the ball is no longer on my court... :-)
No rush; whenever you can get to…
Hi @nico,
At this point, I have got 3 branches, covering changes in different areas:
- changes in
exec/remote.py
for honoring "execute" permissions on remote scripts
- related tests…
Hi @nico,
Thank you for your prompt reaction and my apologies for the late reply.
It is certainly quite wise to keep assumptions about the remote host to a bare minimum.
And yes, you are…
For future reference (to self and others), here are two ugly workarounds that one can resort to within the script files themselves even in the absence of a proper fix on the cdist
side.
The…
Hi,
Well, I am not a fan of the solution involving the CDIST_LOCAL_SHELL
and CDIST_REMOTE_SHELL
environment variables, because of the all-or-nothing nature.
The shebang mecanism is…