__git: no onchange action parameter / messaging functionality #46

Open
opened 2021-11-20 11:25:09 +00:00 by ungleich-gitea · 2 comments

It is not unthinkable that a service must be restarted or an action must be taken when the state of the repository changes.

I propose implementing both an --onchange argument and the messaging functionality as in other types

It is not unthinkable that a service must be restarted or an action must be taken when the state of the repository changes. I propose implementing both an `--onchange` argument and the messaging functionality as in other types
evilham was assigned by ungleich-gitea 2021-11-20 11:25:09 +00:00
Author
Owner

I'm curious, what is your use case here?

I only use __git to do the initial setup but then manage updates separately.
The last thing I need is doing a cdist run for some reason and it updating my working copy just because in the meantime someone made a commit.

Moreover, if now all the types get an --onchange parameter, this is a feature that should be added to cdist itself and not be reimplemented by every type.

I'm curious, what is your use case here? I only use `__git` to do the initial setup but then manage updates separately. The last thing I need is doing a cdist run for some reason and it updating my working copy just because in the meantime someone made a commit. Moreover, if now all the types get an `--onchange` parameter, this is a feature that should be added to cdist itself and not be reimplemented by every type.
Author
Owner

mentioned in merge request !894

mentioned in merge request !894
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ungleich-public/cdist#46
No description provided.