3 ms·

I get some "managed ansible executor" vibes from this. And having a hard time differentiating it form the ansible approach. What advantage does this custum for

I get some "managed ansible executor" vibes from this. And having a hard time differentiating it form the ansible approach. What advantage does this custum format vs industry standard tools? Also not entirely sure how state/sync loop is archived from what I've read in the docs. Do I have to change my app to pull config?

candiddevmike 3y ago
There are a few advantages with the tool: - It's Jsonnet instead of YAML/HCL. That means real functions, imports, and data structures. - It has built in testing and linting functionality - While push mode functions similar to Ansible, pull mode can scale infinitely as it's just clients pulling a text file. Ansible and friends have a lot of scaling issues with larger clients. - All of the rendering happens on the client, no need to bundle secrets. The state/sync loop is achieved by running Etcha as a service or container in pull or push mode. Etcha will periodically pull down new JWTs (or receive pushed) and diff them, run the changes or remove the commands that aren't present.
- evulhotdog 3y ago
  Check out ansible-pull, which is installed by default with Ansible.
  - candiddevmike 3y ago
    Ansible pull is definitely an option, but it's not how most folks use Ansible in my experience (preferring Tower or adhoc run books), namely because it's harder to centrally manage and configure. Etcha creates release artifacts instead of pull down a git repo, and allows you to monitor your deployment using metrics services like Prometheus. Additionally, there is a complete webhook framework for triggering runs.