## Installation
`pip install --user hush-push`
## Usage
```
usage: hush [-h] [--version] [--execute] [--overwrite] [--verbose]
[--remote-endpoint REMOTE_ENDPOINT]
Hello world
optional arguments:
-h, --help show this help message and exit
--version show the current version
--execute, -e create the specified configuration parameters
--overwrite, -o force put the configuration parameters even if they
already exist
--verbose, -v enable verbose logging
--remote-endpoint REMOTE_ENDPOINT, -r REMOTE_ENDPOINT
specify remote endpoint
```
## Pre-requisites
You need to specify which configuration file to use by setting the environment variable `AWS_CONFIG_FILE` to the absolute path of your configuration file.
## Directory structure
The directory structure need to be organized in folders at the root of your project. The first folder name should be equal to the profile name specified in the configuration file to use for the call. If your config looks like this:
```ini
[profile accProfile]
role_arn = arn:aws:iam::000000000000:role/ROLE
region = eu-west-1
source_profile = default
```
You must put your configuration parameters in the following structure under the directory `secrets/`:
```
<project-root>:
secrets/
accProfile/
parameterName
```
If the `parameterName` is a folder structure, the configuration parameter name will be a concatenated version of those. If the folder structure looks like this:
```
<project-root>:
secrets/
accProfile/
eu-west-1/
staging/
remoteEndpoint
```
the parameter name will look like this: `/eu-west-1/staging/remoteEndpoint` with the value of the parameter set to the content of the file `remoteEndpoint`
## Development
To build the dist: `python3 setup.py sdist bdist_wheel` and answer "no" to the question if it's a production release. To upload the created dist run `python3 -m twine upload --repository-url https://test.pypi.org/legacy/ dist/*` and sign in with your username and password.
Metadata
Release files for hush-push 0.3.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 |
|---|---|---|---|---|
| hush-push-0.3.0.tar.gz | 4.4 kB | Without provenance | Details for hush-push-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hush_push-0.3.0-py2-none-any.whl | Python 2 | none | any | Details for hush_push-0.3.0-py2-none-any.whl |
Total release size: 11.9 kB
Release files / hush-push-0.3.0.tar.gz
| Download URL | hush-push-0.3.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
400c20f50ccf299a72d7cee60e19f0a81b6df0baa3a478d77f04e1f04fb2b842
|
|
BLAKE2b-256 checksum How to use checksums |
8e3968edd3d1a66a1210064238e7186112ca78ca1cbf8963e365f271685ea697
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.13
|
Release files / hush_push-0.3.0-py2-none-any.whl
| Download URL | hush_push-0.3.0-py2-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
357b9dc3a8db56c91b6c4974f9984f25113702c1d1f4ac0f8dcfc3d53ec3889f
|
|
BLAKE2b-256 checksum How to use checksums |
21077ae7bf7bf72d0381d6a9b95f8f765af9dee111733a26cfa5d17bb4ee0333
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.13
|
Security for hush-push 0.3.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.