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
When a Pack is installed on Stackstorm using pack install - stackstorm performs a clone on the Repo (Code) - however this results in any submodules present in the repo not being checked out and only being an empty directory.
It would be useful if the clone_repo function also checked out any submodules that are present in the repo, as it would be helpful to add dependencies maintained in seperate repos to the pack as a submodule, while still being maintained externally.
In my use case a series of ansible playbooks are maintained in a seperate repo and I would like to also make them available as a pack to st2, and as I see it the best way to do that is via git submodules.
The text was updated successfully, but these errors were encountered:
I know it is does not address the feature enhancement directly, but this function can be addressed with a workflow and rule that is triggered whenever the pack is loaded. The workflow task would look something like:
Then add a rule to the pack that will run this workflow any time the pack is installed and/or expose the workflow as an alias and allow it to be run directly via Chat if the sub-module needs updating outside of the pack install.
When a Pack is installed on Stackstorm using
pack install
- stackstorm performs a clone on the Repo (Code) - however this results in any submodules present in the repo not being checked out and only being an empty directory.It would be useful if the
clone_repo
function also checked out any submodules that are present in the repo, as it would be helpful to add dependencies maintained in seperate repos to the pack as a submodule, while still being maintained externally.In my use case a series of ansible playbooks are maintained in a seperate repo and I would like to also make them available as a pack to st2, and as I see it the best way to do that is via git submodules.
The text was updated successfully, but these errors were encountered: