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
{{ message }}
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Metronome job task names are prefixed with a datetime string, e.g. 20190826135622VHRSz.task-name, so the current matching can effectively only support all tasks at once via mesos:metronome:*. This means that we can't assign a specific AppRole and policy to a specific job "type". Or I don't see how.
Solution: either support an wildcard matching inside a task name, like mesos:metronome:*.task-name or introduce a more robust regexp matchers.
The text was updated successfully, but these errors were encountered:
@nemosupremo any ETA on the next release? Is it hours/days away or weeks? Asking whether @drbig and I should build and deploy our own fork in the meantime ;)
Metronome job task names are prefixed with a datetime string, e.g.
20190826135622VHRSz.task-name
, so the current matching can effectively only support all tasks at once viamesos:metronome:*
. This means that we can't assign a specific AppRole and policy to a specific job "type". Or I don't see how.Solution: either support an wildcard matching inside a task name, like
mesos:metronome:*.task-name
or introduce a more robust regexp matchers.The text was updated successfully, but these errors were encountered: