Hi,
as a follow-up to the recent non-unique package name discussion, I've
noticed two further instances where this is a problem:
* ssh_authorized_key, which is has only the comment ("name") as
namevar. This is obviously easy to avoid in practice, but might run
into weird edge cases, e.g. blocking proper purge support.
* systemd --user service instances. I'm currently experimenting with
user serviceable systemd instances. The current service type is not
able to model this at all. For example, I've would have multiple
"nginx.service" instances (one for each customer), each of which
receive notifications from different sets of other resources.
Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/5326A747.8010104%40dasz.at.
For more options, visit https://groups.google.com/d/optout.