apiKey environment variable instead of .coda.json file

[Eric_Koleda]

Hi @orth - Thanks for the feedback, that is something we’ve heard before as well. You can work around the limitation by generating your .coda.json in the action, as shown here:

Feedback on passing Coda API key as a command line argument when running `coda upload` command

Hi @Mohammad_Mohammad2 - Thanks for kicking off this discussion. I’ve had people mention to me that they wanted to set up a GitHub action before, but I hadn’t had time to look into it to date. I agree that it would be nice to have a parameter for the token for cases like this, and I can see if the engineers would be open to accepting that PR. I did some testing and found that I could create a .coda.json file without too much trouble. Here’s what my workflow file looks like: name: Pack Actions …

In the long run though it would be nice to just make it a command line argument.