StackStorm / StackStorm/st2

st2 pack * commands should work on "system" packs too.

Open
#3,470 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale status:under discussion
Dominant language
Python
Stars
6.5k
Forks
787
PR merge metrics
No merged PRs in 30d

Description

@nmaludy on slack:

i tried writing a small script to update all of the installed packs :

     st2 pack install $pack; \
   done

However, most of the installed packs can't be downloaded so it errors out... think i need to filter out the "built-in" packs

Also, I don't know where they came from!

@Kami

yep, one think you could do is like git ls contrib/

[11:00]
and exclude those

[11:00]
one solution would be for us to add some metadata for system packs

[11:00]
like st2 pack list --system=false or smth

[11:00]
https://github.com/StackStorm/st2/tree/master/contrib

@lakshmi-kannan

Or move the system packs to index/exchange as well.

@shusugmt

+1 for this (packs in exchange/index). When running st2 in HA mode all nodes running st2actionrunner must share /opt/stackstorm/packs directory. And to do that I can mount NFS shared directory to there, but after you mount of course there's nothing there, it's empty. So every time I setup the HA cluster I first need to copy all system packs extracting from st2 core repository, all manually.

If those system packs are on exchange then I can simply use st2 pack install core or whatever to get them. to achieve this, there's one more thing to be done. st2 pack command cannot rely on packs pack being installed. So the code required to run st2 pack needs to be ported into core library.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the st2 pack command and the system packs under contrib/, then trace the pack-related code that currently depends on the packs pack. Clarify whether the intended outcome is exchange/index availability, system-pack filtering, or moving command support into the core library; done means the selected approach supports pack commands for system packs without requiring packs to be installed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.