ops
ops copied to clipboard
nickthecook
The operations team for your project.
If an env var, say "SOME_API", is defined as a JSON object string in both config and secrets, currently the value from secrets will overwrite the value from config (when...
And maybe other similar errors. ### Steps to reproduce ```console $ ops version File 'ops.yml' does not exist. 1.17.0 $ cd /tmp $ ops up && echo foo File 'ops.yml'...
E.g. "command not found" shouldn't be at the end of a stack trace. Just print the error output.
There's an issue with arch images from this year and GLibC 2.33. Check the Dockerfile for details.
There are a few things that make implementing an e2e spec more work and less DRY than it should be. This is [an example](https://github.com/nickthecook/ops/blob/7955ee3c5799a3f069be4748198f2a88bdd0a975/spec/e2e/sshkey/key_with_passphrase_var/e2e_spec.rb#L5): ```ruby RSpec.describe "ssh key with passphrase...
When `ops` runs an action, it appends all command-line arguments to the command specified in the action config. Thus, it's easy to write actions that take arguments. For example: ```yaml...
It would be nice to have docs for all builtins. E.g.: - Apt and Gem have some version pinning behaviour that would be good to document (since Gem can handle...
Looks like `brew` just uses `git` to pull packages and build them, and `ops` could check out a specific commit hash or branch: https://stackoverflow.com/questions/39187812/homebrew-how-to-install-older-versions ```yaml dependencies: brew: - tflint@311029c24de3de608e78afe0ee4f2413ea7a792b #...
`ops` will append any command-line arguments to the end of the command when executing an action. For example, with this config: ## Current behaviour ```yaml actions: say_it: command: echo ```...