Add --noconfirm option to deployment docs

[alentodorov]

I imagine that someone who is pretty new in using an OSS project would not come to check the source code and I think the option of force deployment is easier than writing a .growrc.yaml file.

[jeremydw]

Hi @alentodorov! It's documented in the help for the command (see below). Are you suggesting it being added to the website as well? Currently we have a bit of a mismatch between what's documented on the website, and the full breadth of command line commands / args.

$ grow deploy --help
Usage: grow deploy [OPTIONS] [DEPLOYMENT_NAME] [POD_PATH]

  Deploys a pod to a destination.

Options:
  -c, --confirm / -f, --noconfirm
                                  Whether to confirm prior to deployment.
  --test / --notest               Whether to run deployment tests.
  --test_only                     Only run the deployment tests.
  --auth TEXT                     (deprecated) --auth must now be specified
                                  before deploy. Usage: grow
                                  --auth=user@example.com deploy
  --force-untranslated            Whether to force untranslated strings to be
                                  uploaded.
  -p, --preprocess / -np, --no-preprocess
                                  Whether to run preprocessors.
  --re-route / --no-re-route      Use experimental routing/rendering pipeline.
  -t, --threaded / -nt, --no-threaded
                                  Use threading during rendering pipeline.
  --help                          Show this message and exit.

[alentodorov]

Hi @jeremydw. Thank you very much for your quick reply and also for the effort in building Grow. I haven’t thought to use manual, but I think most of the developers would use it first.

My suggestion was to add the option to the online docs because I was trying to use the growrc conf file and couldn’t get it working.