SaltStack VS Ansible

Have a look at https://github.com/saltstack/salt/tree/master/tests/pytests/unit and https://docs.saltproject.io/en/latest/topics/development/tests/unit.html

I've opened a ticket: https://github.com/saltstack/salt/issues/60710 but a salt employee has marked it as expected behaviour which means they expect that all commands are sent to every minion even if they don't match and that's expected.

Release phase - Saltstack, HashiCorp Vault.

The most likely cause is this long standing bug: https://github.com/saltstack/salt/issues/54045

However, I can't seem to find any resources about how to initialize the tests directory so it actually runs. There's https://github.com/saltstack/salt/tree/master/tests, but it appears to have way more than what you need to get started...

Hi, I need to manage a .yaml file which has a list of users and associated ip's / ports. I attempted to use file.serialized, however the way I structured my .yaml file file.serialize throws an exception because it contains a list as the first item (github.com/saltstack/salt/issues/41209). My original structure was:

filters and tests are a WIP https://github.com/ansible/ansible/pull/74963

As the parent poster well knows (as they invented it) the trick here is that you write your jobs to install from a checkout the CI system does for you.

https://opendev.org/opendev/system-config/src/commit/0a27974...

is really nice practical example. What it does isn't even really that important; but it runs a simulation of deploying production code in OpenDev. This is a "devel" job, we deliberately test any changes against all the latest HEADS of the master/main/development branches of projects we use. This is a non-voting job -- a heads up that what you're introducing might be fine now, but there is trouble brewing when our dependencies release their next version. Sometimes that's fine and a known issue, or upstream is broken, and other times it's something totally unique and needs to be fixed (this is why, despite AI being able to write code for you, so far the implications of using that code still need a human in the loop :)

The "required-projects" tells Zuul what repositories this test needs.

You can clearly see how it handles various projects having "devel", "main" or "master" branches to pull from to get their latest versions.

In the "vars" you can see we're setting variables that get passed to the job roles flagging "this is the devel job, don't install the latest release but use the source Zuul will checkout for you from here".

The amazing thing? If I make a change and this job fails, I may debug it and find that it wasn't actually my fault, but something in upstream Ansible committed recently. I can propose the fix upstream. They do all their CI, and that's fine. But I now put in my change comment

Depends-On: https://github.com/ansible/ansible/pull/1234

and magically Zuul will recognise that I want to apply that pull request to the Ansible tree in testing and set it up for me (as noted, Zuul can do this for all sorts of systems, not just github). Additionally, Zuul will not merge the change until the dependency is satisfied -- I can NOT commit broken code!

Thanks for this! I've added it to a general accessibility audit issue we have - https://github.com/ansible/ansible/issues/73510

That being said, my recommendation is to look into Ansible -- https://www.ansible.com/. It's syntax is trivial and the greatest advantage is that you only need ssh and Python on the remote system and you're good to go. Even if you don't have root access, if you have ssh you should be able to deploy your configuration files. As a templating engine, Ansible uses Jinja2, which is also quite easy to start with.

They are kind of described here - https://github.com/ansible/ansible/blob/devel/lib/ansible/plugins/terminal/__init__.py

Once machines are installed, you deploy your software with Ansible or similar config management.

Ansible This is a very easy and popular solution but it scales horribly.

I think the only issue is your usage of dashes in variable names: https://github.com/ansible/ansible/issues/8849

- [[ansible]] does not actually support this `-d` flag. So I'll have to drop down into the raw `apt-get install` command [[ apt-get ]] [[ install ]] - https://github.com/ansible/ansible/issues/23220