You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the daemon names in daemons resource are interpreted as plain string. It works for all standard services but not for template services with multiple instance where an instance name is named template_service@instance, as @ is an invalid character in a dict key. A workaround is probably possible using the actions but it would be good to support such service names which probably means that metaconfig should interpret the daemon names as escaped strings. It should not really pose backward compatibility problems as it is unlikely that a standard service name matches an escaped name.
The text was updated successfully, but these errors were encountered:
@stdweird@jrha I have seen no reply to my issue and it is a real issue for us as we are relying more and more on template units for things like uwsgi, gunicorn.... Do you agree that the change would be harmless/acceptable or did I miss something?
Currently, the daemon names in
daemons
resource are interpreted as plain string. It works for all standard services but not for template services with multiple instance where an instance name is namedtemplate_service@instance
, as@
is an invalid character in a dict key. A workaround is probably possible using theactions
but it would be good to support such service names which probably means thatmetaconfig
should interpret the daemon names as escaped strings. It should not really pose backward compatibility problems as it is unlikely that a standard service name matches an escaped name.The text was updated successfully, but these errors were encountered: