Closed davidferlay closed 2 months ago
Action names, as listed in available actions, is based on discovery plugin
Except for removing /actions/**/action.yaml from string, naming stricly follows directory path
/actions/**/action.yaml
So for instance:
integration/applications/roles/event_bus/actions/event-bus/action.yaml
integration.applications.roles.event_bus:event-bus
integration/applications/roles/actions/event-bus/action.yaml
integration.applications.roles:event-bus
integration/applications/actions/event-bus/action.yaml
integration.applications:event-bus
Directory architecture may be under external constraints, like matching Ansible pattern for instance, where is required
/roles/
_
.{binary-name}/config.yaml
launchrctl
launcrctl: actions_naming: - s/\/roles\///g # To remove /roles/ - s/_/-/g # To convert _ to -
Observed
Action names, as listed in available actions, is based on discovery plugin
Except for removing
/actions/**/action.yaml
from string, naming stricly follows directory pathSo for instance:
integration/applications/roles/event_bus/actions/event-bus/action.yaml
integration.applications.roles.event_bus:event-bus
integration/applications/roles/actions/event-bus/action.yaml
integration.applications.roles:event-bus
integration/applications/actions/event-bus/action.yaml
integration.applications:event-bus
Directory architecture may be under external constraints, like matching Ansible pattern for instance, where is required
/roles/
_
Expected
.{binary-name}/config.yaml
file could introduce a sectionlaunchrctl
that allow user to specify regex to transform naming in specific ways, like