Set Begin AppID with CLI argument for CI

Question

Set Begin AppID with CLI argument for CI

ryanbethel opened this issue 2 years ago · 3 comments

It would be nice to be able to set the begin appID with a command line argument that does not get added to the .arc file. This would be useful for CI and integration testing where the appID could be specified in Github secrets etc.

Answer 1 · 2022-10-07T15:37:44.000Z

Hmm, Which workflows? More info pls!

Answer 2 · 2022-10-07T20:29:13.000Z

For instance I wanted to add a staging test to a repo for a feature that cannot be tested in sandbox (i.e. accessing fingerprinted files). To do that I might run begin deploy in Github actions to deploy to a staging app and run tests against that. It would make the most sense to store the app id for that in github secrets and pass it as a command line argument than to have it in the repo in the .arc file. I could also write it to the .arc file in GA before running begin deploy. This is more of a feature suggestion.

Answer 3 · 2022-11-01T02:51:28.000Z

This can be done for stateless workflows, such as: builds, create, destroy, env, logs, and we should definitely do that. deploy is a stateful workload, however, and must be run contextually within a project directory containing an app ID.