Brian Murray has proposed merging autopkgtest-cloud:novarc-secrets into autopkgtest-cloud:master.
Requested reviews: Canonical's Ubuntu QA (canonical-ubuntu-qa) For more details, see: https://code.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/444203 Yesterday when adding the lcy02.rc file I was reading the documentation at https://autopkgtest-cloud.readthedocs.io/en/latest/deploying.html#supply-secrets and realized that it could use a little bit of clarification. Additionally, an example was hiding due to an incorrectly formatted code-block. -- Your team Canonical's Ubuntu QA is requested to review the proposed merge of autopkgtest-cloud:novarc-secrets into autopkgtest-cloud:master.
diff --git a/docs/deploying.rst b/docs/deploying.rst index bf1ee95..110c849 100644 --- a/docs/deploying.rst +++ b/docs/deploying.rst @@ -60,15 +60,17 @@ First create the location for Mojo to find the secrets: cd !$ Now put them in. ``swift_password`` should just contain your swift password. -``novarcs.tar`` should contain the cloud ``.rc`` files. These must be named: -for amd64 (which will also run i386 tests): ``region.rc``, and for everything -else: ``region-arch.rc``. For example: +``novarcs.tar`` should contain the cloud ``.rc`` files which must be named: +``$REGION.rc`` for amd64 (which will also run i386 tests) and +``$REGION-$ARCH.rc`` for everything else. For example: -.. code-block: +.. code-block:: $ tar tf novarcs.tar + lcy02.rc bos01-arm64.rc bos01-ppc64el.rc + ... These are all that are required for a devel deployment. For production there are more secrets required, see the ``service-bundle`` and charm
-- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
