httpexpect VS SaltStack

httpexpect for testing HTTP services. Works great with both RESTful and GraphQL.

I use this library: https://github.com/gavv/httpexpect

https://github.com/gavv/httpexpect End-to-end HTTP and REST API testing for Go.

In the new style, when the tag is longer than 20 characters, an end of tag string is appended to the tag given by the string constant TAGEND, that is, two line feeds '\n\n'. When the tag is less than 20 characters then the tag is padded with pipes "|" out to 20 characters as before. When the tag is exactly 20 characters no padded is done. source: https://github.com/saltstack/salt/blob/master/salt/utils/event.py

https://github.com/saltstack/salt https://github.com/chocolatey/choco https://github.com/nextcloud https://github.com/authelia/authelia https://github.com/grafana/grafana

SaltStack

One thing that really irks me about Salt, though, is that they are very slow to fix bugs. My Salt states are littered with workarounds for bugs that have been open for multiple years. Even in basic things, like ssh authorized_keys management. Other than bug velocity, though, I've been pretty pleased with Salt.

Here are several related GitHub issues: - https://github.com/saltstack/salt/issues/54791 - https://github.com/saltstack/salt/issues/57541 - https://github.com/saltstack/salt/issues/16089

For clarity, here's the issue: https://github.com/saltstack/salt/issues/64111

Nightly builds on supported branches & master running the full test suite, producing fully tested builds. https://github.com/saltstack/salt/actions/workflows/nightly.yml

It's definitely some sort of AI script. Not this exactly, but something working off Python or scripts of thar nature. https://github.com/saltstack/salt