awx
sops
Our great sponsors
awx | sops | |
---|---|---|
147 | 149 | |
13,386 | 15,019 | |
1.5% | 2.1% | |
9.8 | 9.2 | |
3 days ago | 10 days ago | |
Python | Go | |
GNU General Public License v3.0 or later | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awx
-
The Bullhorn #124 (Ansible Newsletter)
AWX Project ↗
-
Webhook notifications -> unable to save custom messages
However, when I try to add it is not allowing me to save nor it throws any error. I see one old pull request which seem to address this very issue but I find the issue still persists. https://github.com/ansible/awx/issues/8898
-
AWX / cicso.nxos Module Help
I ran into that (or something very similar) a few days ago. For me, I made a new Execution environment and used this image rather than the 'latest' one: quay.io/ansible/awx-ee:23.5.0 and now mine works. ref: https://github.com/ansible/awx/issues/14689
-
The Bullhorn #119 (Ansible Newsletter)
@elibogomolnyi The EKS reconnect support AWX jobs can't tolerate the EKS scale out & possible fix.
-
The Bullhorn #114 (Ansible Newsletter)
We're happy to announce that AWX Version 23.0.0 is now available! We're happy to announce that AWX Operator version 2.5.2 is now available!
- [homelab] I am confused with how 3rd-party GUIs interact with my Ansible server
-
The Bullhorn #107 (Ansible Newsletter)
AWX Project ↗ AWX
-
The Bullhorn #106 (Ansible Newsletter)
2023-07-11: AWX Office hours, 15:00 UTC
-
External Semaphore/AWX installation?
You can install AWX in a docker-compose environment as well: https://github.com/ansible/awx/blob/devel/tools/docker-compose/README.md
-
Server management software (patching,...)
There is a web UI for Ansible called AWX
sops
-
Encrypting your secrets with Mozilla SOPS using two AWS KMS Keys
Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Tracking SQLite Database Changes in Git
We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets
Definitely not best practice security-wise, but it works well
-
The Twelve-Factor App
For anyone new to SOPS like I was - https://github.com/getsops/sops
- Storing and managing private keys
-
Show HN: Shello – Wrangle Environment Variables
I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.
You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.
We do this for the live configuration as well in line with Gitops and find it to work well.
If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely
-
Check your secrets into Git [video]
Basically, the simpler the better --just encrypt your secrets and check them in to version control.
We use SOPS[0] for this, and have found it to be pretty nice.
-
How to secure secrets of docker-compose stacks with git?
The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.
-
Is it safe to commit a Terraform file to GitHub?
Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.
-
using keyring - no keyring set and giving errors about backend
It looks like the software you're intending to use is oriented towards interacting with desktop Linux's keyring. While you can probably get this to work, I would recommend using something like sops as it's a more standardized way of storing secrets in configuration.
What are some alternatives?
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
ansible-keepass - Ansible lookup plugin to fetch data from KeePass file
Vault - A tool for secrets management, encryption as a service, and privileged access management
semaphore - Modern UI for Ansible
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
argo-cd - Declarative Continuous Deployment for Kubernetes
git-crypt - Transparent file encryption in git
awx-ee - An Ansible execution environment for AWX project
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
ara - ARA Records Ansible and makes it easier to understand and troubleshoot.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.