proctor
proctor copied to clipboard
A Developer-Friendly Automation Orchestrator
Hi team, Im running on macbook m1 with ruby ruby 2.6.8p205 (2021-07-07 revision 67951) [universal.arm64e-darwin21], i got an error while executing brew tap gojektech/gojek, here's the complete error message: Error:...
Notable Changes: - Execution Context mechanism, all of the information on a job is stored including logs. - Ability to fetch logs even the execution process is interrupted (web socket...
github.com/spf13/cobra gojek/src/github.com/spf13/cobra/command.go:31:25: undefined: pflag.ParseErrorsWhitelist github.com/googleapis/gnostic/extensions gojek/src/github.com/googleapis/gnostic/extensions/extension.pb.go:57:29: undefined: proto.InternalMessageInfo gojek/src/github.com/googleapis/gnostic/extensions/extension.pb.go:121:45: undefined: proto.InternalMessageInfo gojek/src/github.com/googleapis/gnostic/extensions/extension.pb.go:180:46: undefined: proto.InternalMessageInfo gojek/src/github.com/googleapis/gnostic/extensions/extension.pb.go:237:29: undefined: proto.InternalMessageInfo github.com/gojektech/proctor/proctord/storage gojek/src/github.com/gojektech/proctor/proctord/storage/store.go:73:33: multiple-value uuid.NewV4() in single-value context
As an admin, Post being [notified from the CLI on a new release of Proctor CLI](), users can update proctor from the CLI itself. Example: `proctor update `
When input parameters for a proc are large, it sometimes becomes difficult to verify the input params one last time before executing a proc. Does it make sense to add...
Proctor shows the following error message when I try to run procs that I don't have permissions for. Error submitting proc for execution It should show a better error message...
As an admin, I want to notify users when new version is available whenever they run `proctor version` Example: ``` $terraform version Terraform v0.11.7 Your version of Terraform is out...
As an admin, I want to persist the procs execution status job for a worker to pick it up. Currently, it is being run asynchronously using a goroutine. In that...
Currently, CLI (client) doesn't retry on failure while streaming logs. This removes the ability to deploy `proctord` at desirable hour.
As an admin, I want to test logic written inside config setup. So that, On modifying it in future, existing functionality doesn't break.