D6982: automation: improve documentation for credentials management
indygreg (Gregory Szorc)
phabricator at mercurial-scm.org
Sat Oct 5 14:29:46 EDT 2019
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-devel.
Closed by commit rHGf71b3c561b93: automation: improve documentation for credentials management (authored by indygreg).
This revision was automatically updated to reflect the committed changes.
This revision was not accepted when it landed; it landed in state "Needs Review".
CHANGES SINCE LAST UPDATE
CHANGES SINCE LAST ACTION
diff --git a/contrib/automation/README.rst b/contrib/automation/README.rst
@@ -47,12 +47,25 @@
for how ``boto3`` works. Once you have configured your environment such
that ``boto3`` can find credentials, interaction with AWS should *just work*.
+To configure ``boto3``, you can use the ``aws configure`` command to
+write out configuration files. (The ``aws`` command is typically provided
+by an ``awscli`` package available in your package manager, including
+``pip``.) Alternatively, you can write out files in ``~/.aws/`` directly.
+ # ~/.aws/config
+ region = us-west-2
- Typically you have a ``~/.aws/credentials`` file containing AWS
- credentials. If you manage multiple credentials, you can override which
- *profile* to use at run-time by setting the ``AWS_PROFILE`` environment
+ # ~/.aws/credentials
+ aws_access_key_id = XXXX
+ aws_secret_access_key = YYYY
+If you have multiple AWS accounts, you can name the profile something
+different from ``default``. e.g. ``hg``. You can influence which profile
+is used by ``boto3`` by setting the ``AWS_PROFILE`` environment variable.
To: indygreg, #hg-reviewers
More information about the Mercurial-devel