Lack of "download" Command

(Note: I believe that what I’m looking for here is not at all the same thing as #19, in particular because I’m looking for functionality that is not the same as the ‘clone’ command.)

Let me start by saying that I agree that, generally, the git repo should be the authoritative source of the code for a GAS project.

However, I’d like to be able to check that, when I have checked out what is supposed to be the released version of the source, the actual released version matches that. The first idea that comes to mind is to be able to run “gapps download”, which would use the information from the gapps.config.json file to download the currently released copies of the project, and then a “git diff” would tell me my version is inconsistent and, if so, what those inconsistencies are.

I’m open to other ideas for how to do this, though.

A further extension of this would be the ability to download specific versions of the project as saved in “File / Manage Versions…” dialogue. However, I don’t see any API that would let us do this, nor am I sure that the usefulness of this would justify more than very minimal expense.

[brainysmurf]

I am using this tool to maintain a potentially large code base as well, and I have to agree with c-j-s.

The stack we are using is quite unique. In other environments, our local stack can be assumed to work exactly like the remote one (with important caveats). But with Google, if something isn’t working right with different calls to Google’s API, it just makes a whole lot of sense to modify the code in the script and test in the remote stack. (Using the Test as Add on…) You can mock them locally, too, to avoid having to do this all the time, but if you got that mock wrong you need to go to the source.

Granted the programmer could potentially screw this up. How about a --force option and without it, it prompts the user with “are you sure…”?

[danthareja]

Hey @cjs-cynic-net, I really appreciate your input here. To be totally transparent, this tool was initially developed for my own personal use at work, and has reached a wider audience with the help of @hess-g. My initial pushback arose because I don’t use this tool in a large team setting, and I don’t think I’ll ever be the authority on the issues you’re experiencing.

I do agree with many of your points, but I don’t have the time right now to commit to the work it would require to make these changes. I’m happy to see you fork the project to suit your needs and look forward to your PRs should you choose to submit them