Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
mercurial-devel
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
mercurial
mercurial-devel
Commits
f71b3c561b93
Commit
f71b3c561b93
authored
5 years ago
by
Gregory Szorc
Browse files
Options
Downloads
Patches
Plain Diff
automation: improve documentation for credentials management
Differential Revision:
https://phab.mercurial-scm.org/D6982
parent
b8df6a470bbb
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
contrib/automation/README.rst
+18
-5
18 additions, 5 deletions
contrib/automation/README.rst
with
18 additions
and
5 deletions
contrib/automation/README.rst
+
18
−
5
View file @
f71b3c56
...
...
@@ -47,5 +47,13 @@
for how ``boto3`` works. Once you have configured your environment such
that ``boto3`` can find credentials, interaction with AWS should *just work*.
.. hint::
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.
e.g.::
# ~/.aws/config
[default]
region = us-west-2
...
...
@@ -51,8 +59,13 @@
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
variable.
# ~/.aws/credentials
[default]
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.
e.g. ``AWS_PROFILE=hg``.
Resource Management
-------------------
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment