Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow to define commands to be run by triggers #41

Closed
pm98zz-c opened this issue Oct 8, 2018 · 0 comments
Closed

Allow to define commands to be run by triggers #41

pm98zz-c opened this issue Oct 8, 2018 · 0 comments

Comments

@pm98zz-c
Copy link
Contributor

pm98zz-c commented Oct 8, 2018

Once we have #40 in place, we should allow commands to be run for each service (or globally) at each steps of the triggers.
Those would be defined as a nested list in the .yml configs, eg something along the lines of:

vagrant_triggers:
  - up:
    - "my command one to run on host"
    - "a second command"
pm98zz-c pushed a commit that referenced this issue Nov 22, 2018
#41 Custom Vagrant triggers
763d92c
pm98zz-c pushed a commit that referenced this issue Nov 22, 2018
#41 custom triggers (#61)
be6cbff 
* #41 Custom Vagrant triggers

* Adding Elastic to default config

* Re-instate the order of services
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pm98zz-c