-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add deploy_modules method to fabric tools #39
Comments
This issue could be broken down into as many as four releases in a series of incremental improvements. That series might look like this: Deploy and enable one module. This is the minimally functional feature.
Deployment Usage:
Enable Usage:
Deploy and enable multiple modules. This feature would be driven by the existing modules.json. It would be implemented via these methods.
Deploy and enable only as needed. This is an incremental deployment and enabling of modules. It would require these methods:
Additionally, the Deploy pre-release code. It might be useful to test unreleased code in a non-local environment. To do that we would need a method, |
To get the inputs for
|
Module updates that are done using Fabric tools have a tedious, multi-step workflow as shown here.
The fabric tools could benefit from a task designed to deploy and enable a module from a code release. See the green text above.
The text was updated successfully, but these errors were encountered: