Deployment Notifications
This package collects the mechanics for sending notifications “version x of project y was just deployed to environment z”, for example to set markers in observability systems like Grafana, post a message to a slack channel, transition issues in jira to the corresponding status, etc.
Usage
The package provides a “multi subcommand” CLI interface:
python -m zeit.deploynotify
--environment=staging --project=example --version=1.2.3 \
slack --channel=example --emoji=palm_tree
Typically this will be integrated as a Keptn Deployment Task, like this:
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: deployment-notify
spec:
refreshInterval: 1h
secretStoreRef:
name: baseproject-vault
kind: SecretStore
data:
- secretKey: SLACK_HOOK_TOKEN
remoteRef:
key: zon/v1/slack/hackbot
property: HOOK_TOKEN
---
apiVersion: lifecycle.keptn.sh/v1alpha3
kind: KeptnTaskDefinition
metadata:
name: notify
spec:
container:
name: task
image: europe-west3-docker.pkg.dev/zeitonline-engineering/docker-zon/deploynotify:1.0.0
envFrom:
- secretRef:
name: deployment-notify
args:
- "--environment=staging"
- "slack"
- "--channel=example"
- "--emoji=palm_tree"
Changelog
zeit.deploynotify 1.13.0 (2026-01-08)
Changes
Implement gha-workflow command to send repository_dispatch event to GHA (gha)
zeit.deploynotify 1.12.0 (2025-09-10)
Changes
jira: Ignore issues that cannot be transitioned (jira)
1.11.0 (2025-05-06)
Changes
MAINT: Consider ES project when updating Jira tickets (jira-project)
1.10.2 (2025-04-25)
Changes
Correctly return empty changelog diff (empty)
1.10.1 (2025-04-23)
Changes
Return empty changelog diff if previous version equals current version (previous)
1.10.0 (2025-02-27)
Changes
Specify separate title for postdeploy message (postdeploy)
1.9.1 (2025-02-25)
Changes
Ignore status Backlog by default (jira)
1.9.0 (2025-02-20)
Changes
Move printing of changelog diff to CLI for reusability (printdiff)
1.8.1 (2024-12-11)
Changes
Retrieve workloadVersion, not appVersion from keptn context (keptn)
1.7.0 (2024-12-10)
Changes
Make retrieving the changelog from tag configurable (jira)
1.6.0 (2024-10-18)
Changes
WCM-457: new custom command slack-reminder (reminder)
Changes
WCM-457: new custom command slack-reminder (reminder)
1.5.0 (2024-08-07)
Changes
issues: Support multiple issue prefixes (issues)
jira: Select jira status by name insead of id (jira)
1.4.1 (2024-07-30)
Changes
ZO-5636: Set all hny dataset as default (ZO-5636)
1.4.0 (2024-07-30)
Changes
ZO-5636: Support honeycomb environments marker (ZO-5636)
1.3.0 (2024-02-22)
Changes
Update to keptn-0.10 context API (keptn)
1.2.3 (2024-01-17)
Changes
Fix jira status change (jira)
1.2.2 (2024-01-16)
Changes
Don’t set jira status if status is already ‘more done’ (jira)
1.2.1 (2024-01-11)
Changes
Detect empty postdeploy properly (postdeploy)
1.1.1 (2024-01-08)
Changes
Quote changelog text correctly for slack (changelog)
1.1.0 (2024-01-08)
Changes
ZO-4171: Implement posting the changelog diff to slack (changelog)
1.0.4 (2024-01-08)
Changes
postdeploy: Retrieve changelog of the deployed version (postdeploy)
1.0.3 (2023-12-18)
Changes
Fix jira changelog parsing (jira)
1.0.2 (2023-12-18)
Changes
Fix bugsnag cli parsing (bugsnag)
1.0.1 (2023-12-18)
Changes
Allow calling multiple tasks in a single invocation (chain)
1.0.0 (2023-12-13)
Changes
Initial release (initial)
1 maintainer
Metadata
1 maintainer
Release files for zeit.deploynotify 1.13.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 |
|---|---|---|---|---|
| zeit_deploynotify-1.13.0.tar.gz | 18.7 kB | Without provenance | Details for zeit_deploynotify-1.13.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zeit_deploynotify-1.13.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for zeit_deploynotify-1.13.0-py2.py3-none-any.whl |
Total release size: 30.1 kB
Release files / zeit_deploynotify-1.13.0.tar.gz
| Download URL | zeit_deploynotify-1.13.0.tar.gz |
|---|---|
| Size | 18.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
74de699e6a14c0bbd45f2e9d97012c367b9e3ebf806ed03adb83648899e71504
|
|
BLAKE2b-256 checksum How to use checksums |
e6ca08cdd363cee1ce2795399886d28ef24e0df5fbb7cdbdca8a8151990a5d67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / zeit_deploynotify-1.13.0-py2.py3-none-any.whl
| Download URL | zeit_deploynotify-1.13.0-py2.py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7ba8aac3c6610f1954158261e36d3e765a8308a666011d78a3f01398c6f98049
|
|
BLAKE2b-256 checksum How to use checksums |
2f23afd21843cd3cb51da79e4d79239ffe404da65f5da37e77fbecb7f0eabf74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for zeit.deploynotify 1.13.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.
