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
This is blocking running our tests on a virtualenv exported by pants.
Options:
wait for the next pants release that includes this feature.
Pants does dev releases almost every week, but we normally wait for at least an alpha or release candidate before using it with StackStorm. This means that waiting could delay the release further.
In general, we agreed that the release is already delayed, so waiting for this is ok.
Extract the changes in pants into a pants-plugin we can include in the st2 repo.
This is a fairly large plugin at around 1k lines because it has to copy a lot of the modified pants rules.
@cognifloyd will watch the release cycle of pants - if it looks like the release is going to be delayed, then he'll create a PR to pull the plugin into st2.
@nzlosh asked about the feasibility of cutting a release based on pants soonish
We don't want to do an official release until we can test it with our current tests as-is. This is blocked by the editable installs feature.
However, we do have the bits to install the virtualenv in /opt/stackstorm/st2. So, @cognifloyd will work on the packaging parts of the release workflow while we wait for the testing parts.
This includes packaging a virtualenv (generated from the pants-generated wheels) into deb/rpm similar to our current release process.
Some of the end-to-end testing will probably not be doable until we can run our unit tests (blocked, see above).
But that does not block working on the rest of packaging.
@cognifloyd has been focused on the pants+CI+release workflow changes and hasn't had a chance to review
We want the changes, just need review time bandwidth and some of the CI needs to be fixed.
Painful upgrades are coming:
python 3.9, 3.10
mongo 4.4 is reac hing EOL
updating ubuntu and EL involves bumping the python version
we want to get the pants stuff in to facilitate all of this work.
python 3.10 is blocked on our use of nosetest
RBAC K/V issues
We need someone from ochestral to take a look at adding list all secrets or similar permissions for rbac policies that apply to non-admin users. Keystore RBAC Configuration Issues st2#5908
The text was updated successfully, but these errors were encountered:
April 2023 @StackStorm/tsc
1 hour
meeting plan:Tuesday, 14 February 2023, 09:30 AM US Pacific
.Meeting
AgendaNotesWe did not have a meeting agenda ahead of time. So, this is what we talked about:
Attendees
@armab, @amanda11, @cognifloyd, eduardtamsa, @mickmcgrath13, @nzlosh, @winem
Topics discussed
New StackStorm Deploy Action for GHA:
Pants migration / the next release:
/opt/stackstorm/st2
. So, @cognifloyd will work on the packaging parts of the release workflow while we wait for the testing parts.SSO/SAML:
Painful upgrades are coming:
nosetest
RBAC K/V issues
The text was updated successfully, but these errors were encountered: