awsslack
Basic view of how it would look in Slack (reality is much better with live progress-bar)
my-slack-bot APP 12:02 AM
████████████████████ 100.0%
00:02:12 - [Build: <project-name> BuildStatus=IN_PROGRESS!]
00:02:17 - [Build's Phase: SUBMITTED PhaseStatus=SUCCEEDED]
00:02:18 - [Build's Phase: QUEUED PhaseStatus=SUCCEEDED]
00:02:48 - [Build's Phase: PROVISIONING PhaseStatus=SUCCEEDED]
00:02:53 - [Build's Phase: DOWNLOAD_SOURCE PhaseStatus=SUCCEEDED]
00:03:14 - [Build's Phase: INSTALL PhaseStatus=SUCCEEDED]
00:03:19 - [Build's Phase: PRE_BUILD PhaseStatus=SUCCEEDED]
00:05:00 - [Build's Phase: BUILD PhaseStatus=SUCCEEDED]
00:05:31 - [Build's Phase: POST_BUILD PhaseStatus=SUCCEEDED]
00:05:36 - [Build: <project-name> BuildStatus=SUCCEEDED!] (edited)
Installation
$ pip install awsslack
Usage
Config
Config file path is: ~/.aws/.awsslack-config.yaml
$ awsslack config --auto-generate
See help: awsslack config --help
CodeBuild
Trigger Codebuild project for dev environment:
$ awsslack codebuild -P <project-name> -E dev
Similarly, for prod environment:
$ awsslack codebuild -P <project-name> -E prod
See help: awsslack codebuild --help
CodeDeploy
Trigger CodeDeploy project for dev environment:
$ awsslack codedeploy -P <project-name> -E dev
Similarly, for prod environment:
$ awsslack codedeploy -P <project-name> -E prod
Note: If --commit is not provided, will fetch latest Commit ID from --branch.
See help: awsslack codedeploy --help
Slack App
To create a new Slack app:
- Go to https://api.slack.com/apps?new_app=1
- click 'From scratch'
- enter 'App Name': 'awsslack'
- select workspace
- click 'Create App'
- click 'OAuth and Permissions'
- under scopes, 'Bot Token Scopes', click 'Add an OAuth Scope'
- add 'chat:write' scope
- under scopes, 'User Token Scopes', click 'Add an OAuth Scope'
- under 'OAuth Tokens for Your Workspace', click 'Install to Workspace'
- click 'Allow'
- copy 'Bot User OAuth Token'
- update the token in config file at path
~/.aws/.awsslack-config.yaml - Add apps to your Slack workspace
- Good to go. now 'awsslack' can push updates to slack
Metadata
Release files for awsslack 0.1.4
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 | |
|---|---|---|---|---|
| awsslack-0.1.4.tar.gz | 10.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awsslack-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.2 kB
Release files / awsslack-0.1.4.tar.gz
| Download URL | awsslack-0.1.4.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e180e7adc2ad8395ab59229d8b1c9dff34d1954cd81fd78afcc59d91ac46edd
|
|
BLAKE2b-256 checksum How to use checksums |
063a95a8acadee350353557decef6af22e7d3740c0ee7cf8ddf75ea0e4c6d97e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.1 CPython/3.8.10 Linux/5.15.0-1028-aws
|
Release files / awsslack-0.1.4-py3-none-any.whl
| Download URL | awsslack-0.1.4-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26f18ca8198abbb710e73287a545f32bfcad15bb46016c309b32fb2a1fd61525
|
|
BLAKE2b-256 checksum How to use checksums |
d833fa976f8c56c0dabe897e8f813d6895202db01b12275884f0f50ce4c6556e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.1 CPython/3.8.10 Linux/5.15.0-1028-aws
|
Security for awsslack 0.1.4
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.