Eyal Mor

To raise customer confidence in our libraries, and to give us confidence in our ability to refactor them, it would be valuable if we could have available to us metrics...

Original Author: @slonokot Running `shore exec` with bad JSON payload will produce misleading error message: ```shell $ shore exec -p '{"application": "a", "pipeline": "b",,,}' required args key 'pipeline' missing required...

**Late night idea warning** We need data to drive our decisions, and understanding of how people use pipelines. To allow us to make data-driven decisions, let's add some basic telemetry...

The current examples directory is very messy, with old and new examples. We need to create a few examples that are easy to run and understand with clear intentions. Additionally...

Original Author: @slonokot Follow up issue on the initial integration tests Our exec and test-remote cmds aren't checking properly the outcomes with the existing mocks. * Evaluate gomock framework *...

When executing commands, the CLI may require some files to be available, top examples: 1. `main.pipeline.jsonnet`. 2. `cleanup.pipeline.jsonnet`. These files should be validated pre-execution and have a clear error message...

Background: The short of it is that it would be a nice to have a helper command to download a pipeline json based on Application and Pipeline names, this saves...

For the spinnaker backend, some operations require Application/Pipeline/Type properties. Create the struct for the most basic operations like checking if these fields exist.

Original Author: @dkirillov Goals for refactoring `init.go` are: - decouple or provide flexibility in the init to support different render/backend combos. - maintain or improve code coverage for `init.go` (84%...

Original Author: @dkirillov This is follow up for issue #108 . When doing `shore project init` and giving the project name, the output that contains the project's name might be...