The doc pulishing framework we use uses both Fastly (via ASF) and
Cloudfront (in our AWS to serve our historical documentation) so
in order to upload manually a file, you need to invalidate both
caches in case the page you updated is already in the cache.
This PR updates documentation about that, explains which Cloudfront
instances are used for live/staging appropriately and explains how
to invalidate caches manually after you modified files in the
bucket manually.
There are a couple of improvements for live/staging doc publishing.
1) we use auto/live/staging rather than buckets in the drop-downs
2) auto selection of live/staging depending on the tag used to
produce the documentation
3) we use env variables to pass inputs/outputs to scripts - which
is good security practice
4) watermark changes are applied to documentation published to
staging site
Jarek Potiuk
