Idem-Aws-Auto
aws_auto Cloud Provider for Idem
DEVELOPMENT
Clone the idem-aws-auto repository and install with pip.
git clone git@gitlab.com:my-user/idem-aws-auto.git
pip install -e idem-aws-auto
ACCT
After installation aws_auto Idem Provider execution and state modules will be accessible to the pop hub. In order to use them we need to set up our credentials.
Create a new file called credentials.yaml and populate it with profiles. The default profile will be used automatically by idem unless you specify one with –acct-profile=profile_name on the cli.
acct backends provide alternate methods for storing profiles.
The aws_auto provider uses the aws_auto acct plugin for authentication. A profile needs to specify the authentication parameters for aws_auto.
credentials.yaml
aws_auto:
default:
username: my_user
password: my_good_password
endpoint_url: https://console.aws_auto.com/api
Now encrypt the credentials file and add the encryption key and encrypted file path to the ENVIRONMENT.
The acct command should be available as it is a requisite of idem and idem_aws_auto. Encrypt the the credential file.
acct encrypt credentials.yaml
output:
-A9ZkiCSOjWYG_lbGmmkVh4jKLFDyOFH4e4S1HNtNwI=
Add these to your environment:
export ACCT_KEY="-A9ZkiCSOjWYG_lbGmmkVh4jKLFDyOFH4e4S1HNtNwI="
export ACCT_FILE=$PWD/credentials.yaml.fernet
USAGE
A profile can be specified for use with a specific state. If no profile is specified, the profile called “default”, if one exists, will be used:
ensure_user_exists:
aws_auto.user.present:
- acct_profile: my-staging-env
- name: a_user_name
- kwarg1: val1
It can also be specified from the command line when executing states.
idem state --acct-profile my-staging-env my_state.sls
It can also be specified from the command line when calling an exec module directly.
idem exec --acct-profile my-staging-env aws_auto.user.list
Metadata
Release files for idem-aws-auto 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| idem-aws-auto-0.1.0.tar.gz | 2.7 MB | Without provenance | Details for idem-aws-auto-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| idem_aws_auto-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for idem_aws_auto-0.1.0-py3-none-any.whl |
Total release size: 8.9 MB
Release files / idem-aws-auto-0.1.0.tar.gz
| Download URL | idem-aws-auto-0.1.0.tar.gz |
|---|---|
| Size | 2.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb655663ad03598e11c408289e0b0f0cf922c07989c6dc395f2332106b84f0a6
|
|
BLAKE2b-256 checksum How to use checksums |
69aafe7ec8a6885d36be7e027fcf714400b270ec8025e0c74444f2e316bf8c0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.6
|
Release files / idem_aws_auto-0.1.0-py3-none-any.whl
| Download URL | idem_aws_auto-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
655693ae555621d789db6d127b92ddbad98ad82d874dd6c314808736f6974d1f
|
|
BLAKE2b-256 checksum How to use checksums |
452c38bb5f575793fc4adb51517dd641be052813d3babd008877ddee93d56d54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.6
|
Security for idem-aws-auto 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.