StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html
This updates from pants 2.22 to 2.23. The stable version of 2.23 has not been released yet, but with so many features that we need, it's worth using an alpha to unblock other developments.
I also added a .gitattributes file to try and improve the UX of fixing lockfile merge conflicts.
I also included 2 minor commits extracted from #6202:
pants is already configured to ignore dist_utils.py, so also ignore test_dist_utils.py: 423472495f702f7c19a328dd62b35b0c42ac3a39
Add tags=["pack"] to all of the pack tests so that we can easily run just the pack tests via pants: 77ee17c03accc48cc8d0d0cc28420945772f914f
Follow-up PRs will allow us to run all of the pack and unit tests via pants + pytest.
This release adds the last 2 features we need from pants to get pants+pytest to run all of our unit and pack tests, based on work in #6202:
Added a python_test(entry_point_dependencies={...}) BUILD metadata field. This field was added to resolve issues enabling our runner tests (released in 2.23.0.dev2): https://github.com/pantsbuild/pants/pull/21062
Added a pants plugin api PytestPluginSetup(extra_sys_path=...) which we need to finish some pack_metadata based dependency inference (released in 2.23.0a0): https://github.com/pantsbuild/pants/pull/21274
v2.23.0a0 also includes the nfpm plugin I wrote to replace our st2-packaging repo. nFPM builds system packages like rpm and deb without the complicated ruby+docker+the-kitchen-sink dance we do in st2-packaging.
This updates from pants 2.22 to 2.23. The stable version of 2.23 has not been released yet, but with so many features that we need, it's worth using an alpha to unblock other developments.
I also added a
.gitattributes
file to try and improve the UX of fixing lockfile merge conflicts.I also included 2 minor commits extracted from #6202:
dist_utils.py
, so also ignoretest_dist_utils.py
: 423472495f702f7c19a328dd62b35b0c42ac3a39tags=["pack"]
to all of the pack tests so that we can easily run just the pack tests via pants: 77ee17c03accc48cc8d0d0cc28420945772f914fFollow-up PRs will allow us to run all of the pack and unit tests via pants + pytest.
Interesting new features in 2.23
The
[export].py_hermetic_scripts
option is renamed to[export].py_non_hermetic_scripts_in_resolve
in 2.23:This release adds the last 2 features we need from pants to get pants+pytest to run all of our unit and pack tests, based on work in #6202:
Added a
python_test(entry_point_dependencies={...})
BUILD metadata field. This field was added to resolve issues enabling our runner tests (released in 2.23.0.dev2): https://github.com/pantsbuild/pants/pull/21062Added a pants plugin api
PytestPluginSetup(extra_sys_path=...)
which we need to finish some pack_metadata based dependency inference (released in 2.23.0a0): https://github.com/pantsbuild/pants/pull/21274v2.23.0a0 also includes the
nfpm
plugin I wrote to replace ourst2-packaging
repo.nFPM
builds system packages like rpm and deb without the complicated ruby+docker+the-kitchen-sink dance we do inst2-packaging
.pants-plugins lockfile diffs
From 2.22 to 2.23