Mastered salt-ssh technology for client repositories. It was added to the code and client accounts as a separate type of config management. This greatly simplifies the launch of small clients, since they no longer need to have salt masters. Of the shortcomings – incompatible with Windows minions. It works on the principle of packing a client repository into a docker image with salt-ssh and running a job on a dedicated gitlab runner with docker executor. In terms of pipeline job execution, it is compatible with the usual salt repository.
Related Post
System Optimizations and Bug Fixes Across Backup, Automation, and Client Management
With a small fix, we’ve augmented the rsnapshot_backup with the ability to pipe a dump using mysqldump_args,...
Deployment, Monitoring Improvements, and Site Hacks via the Vote Module: A Roundup of Key Updates
Successfully used salt-ssh-deploy with GitHub Actions, added minimalist example pipeline. Started using ACL in Redis to...
From GMail Cleanup to GitLab Optimizations: Managing Errors, Monitoring, and Enhancements
After the introduction of interception of errors from servers in Sentry instead of mail, the time has come to clean up...
