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.

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

introduce modularity in our playbooks #204

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

introduce modularity in our playbooks #204

wants to merge 2 commits into from

Conversation

lunika
Copy link
Member

@lunika lunika commented Dec 13, 2018

Purpose

In #175 we want to execute a task depending on a context and specific to an app. So we need to be able to execute tasks that are "application centric".

Proposal

Create a "hook" system. Tasks can live in the application folder and will be executed if they follow a pattern we choose. You should create a hooks folder and then in it files with the name of the hook you want to implement. For example for the hook vaults_created you should create this file for the forum application: apps/forum/hooks/vaults_created.yml

  • create tasks to execute hooks
  • example how to use them

We want to execute task form the app repository at a precise moment in
our playbooks. To do that this two tasks can be executed and will
include tasks if they found them
Create_vaults playbook is the first where we need a hook.
@lunika lunika self-assigned this Dec 13, 2018
@jmaupetit
Copy link
Contributor

I like the idea, but I think we must talk a bit more of what must be achieved first. This implies dependencies between applications. IMO that should be implemented first.

@lunika
Copy link
Member Author

lunika commented Dec 13, 2018

This PR is a POC and I'm open to discuss about what can be implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants