"relaying" messages? #136
Labels
No Label
bugfix
cleanup
discussion
documentation
doing
done
feature
improvement
packaging
Stale
testing
TODO
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ungleich-public/cdist#136
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created by: tom-ee
This is related to #624.
With PR #623 the question of "message relaying" re-surfaced (just using this PR as an example):
The re-implemented
__apt_source
manipulates files in/etc/apt/sources.list.d/
and messages for these manipulation are through the used__file
-type.We could "relay" the message by parsing
$__messages_in
in__apt_source/geocode-local
and issue a message on it's own (relay__file/etc/apt/sources.list.d/xxx
-messages as__apt_source/apt/sources.list.d/xxx
).pro:
/etc/apt/sources.list.d/xxx
).contra:
After writing this up my conclusion would be:
Relaying messages is not desirable and should only be done after thoroughly considering other ways.
Thoughts on this?
Should/could a note on this to the documentation (messaging or best practices)?
closed