Summary of improvements - PENDING for Rafael

[justin808]

Now

• [x] always echo org and app for all commands (Added in #94)
• [x] logs from cpl run commands go where? See discussion on Slack - issue #98
• [x] verbose mode, don't echo any token (applies to promote-app-from-upstream) - issue #97
• [x] rename controlplane.yml key setup to setup_app_workloads for clarity - issue #112
• [ ] validations of yaml file upon startup - issue: #99
  • [ ] workload names must match template file names and the workload name inside the templates
  • [ ] templates can contain multiple documents (working), but ONLY one workload with name matching file name
  • [x] default location - Issue #100
  • [x] Allow specifying --location for commands like ps, run, run:detached, apply-template
• [x] spec/dummy app that docs reference - issue #101
  • [ ] Rails 7.1 base image that includes node, ruby, rails 7.1, and the common gems and packages so that the build can be very fast.
  • [x] rails new rails-webpack --javascript=webpack
  • [x] Can be based on https://github.com/shakacode/react-webpack-rails-tutorial/tree/master/.controlplane
  • [x] Use the simple docker examples from https://github.com/rails/rails/blob/main/railties/lib/rails/generators/rails/app/templates/dockerignore.tt#L1 and https://github.com/rails/rails/blob/main/railties/lib/rails/generators/rails/app/templates/Dockerfile.tt#L65
  • [x] Use org https://console.cpln.io/console/org/shakacode-heroku-to-control-plane-ci/-info

---

Later

• [ ] Could have some flag to output json later for cleaner output if anybody ever asks (not yet!), like

• [ ] LATER - Should we update docs to refer to this example. We might not keep https://github.com/shakacode/react-webpack-rails-tutorial always updated...Let's get the CI example working first.

JSON arg example from Heroku

USAGE
  $ heroku apps [-A] [--json] [-s <value>] [-p] [-t <value>]

FLAGS
  --json               output in json format

[justin808]

See #92.

[ahangarha]

@justin808 May I break down this issue into multiple focused issues so that it becomes easier to track the progress?

[ahangarha]

I have moved all the priority tasks into dedicated issues so that:

• We can separately track their progress
• We can separately discuss their implementation

If it is okay, we can remove the now section and keep this for LATER tasks. We may add milestone for 1.2.0 and 1.3.0, with deadline.

[justin808]

@ahangarha you can link my checklist above to issues.