akshat
akshat
As an admin, I don't want users to type `execute` everytime they want to execute a proc. Current scenario: ``` proctor execute create-some-infra-one ARG_ONE=a ARG_TWO=b proctor execute create-some-infra-two ARG_THREE=c ARG_FOUR=d...
As an admin, I want to notify CLI users when a newer version of proctor is released. So that, Users can stay updated with the latest features. When a newer...
We can have auto-completion for describe/execute/list commands. * Out of scope: auto-completion for procs and their args.
Currently, for providing any args to a proc, I need to pass them as K-V pairs. Example: ``` proctor execute grep-knife-node-list NODE_NAME=proctor-postgres ``` Would it make sense to pass free-flowing...
As a user, I want procs help to be more intuitive. Currently, If I fetch all procs using `proctor list`, and I need help for `run-sample` proc, I need to...
As an admin, I want to clean-up inter-changeable usage of the keywords `jobs`, `procs`, `scripts` and `automation` inside Proctor. Across Proctor, only 1 keyword should be used for the automation...
As an admin, I want users to be able run procs in the environment they specify. So that, Connectivity issues won't arise while running procs. Currently procs are run in...
As an admin, I want to encrypt secrets while storing them using proctord. So that, If secrets get leaked accidentally, they aren't of any use without the encryption key.
As a user, I would like to see how to stitch all components of Proctor together. Currently, dev setup for proctor CLI and proctord exists. What already exists: - Setup...