The repository or configuration that created this release differ from a previous release. View details.
applicationmapper
This is is a Kubernetes controller implemented using Metacontroller that can generates ArgoCD applications conveniently via Helm templates from input sources that are not sourced from GitOps, but instead from Rest APIs.
It is comparable to an ArgoCD ApplicationSet resource, but more powerful and decoupled from GitOps. The primary use
case of this controller is to manage automatic deployments of mostly homogeneous applications based on external data
sources, such as spinning up (and down) customer environments.
Usage
The ApplicationMapper resource is a Cluster-scoped resource because it allows it to generate resources in any
namespace. This is relevant for being able to generate an Application object in the argocd namespace while being
able to populate Secret and ConfigMap resources in another namespace (e.g. where the application deploys its
resources to).
The template in an ApplicationMapper may produce any of the following resources:
argoproj.io/v1alpha1/Applicationv1/ConfigMapv1/Secret
Examples
- Guestbook – Creates an instance of the ArgoCD Guestbook application, one per item in a static list of subscription IDs.
Metadata
Release files for applicationmapper 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| applicationmapper-0.3.1.tar.gz | 31.8 kB | With provenance | Details for applicationmapper-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| applicationmapper-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for applicationmapper-0.3.1-py3-none-any.whl |
Total release size: 38.9 kB
Release files / applicationmapper-0.3.1.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | applicationmapper-0.3.1.tar.gz |
|---|---|
| Size | 31.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2023affac40f1cd3cd3e695d690225be9b483389a24317e487b82d5736bac4c
|
|
BLAKE2b-256 checksum How to use checksums |
65f6cca2cf220efff608c93cfc922869571b7801795c2ff090260ba6ee80a2ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 30, 2025.
Transparency logRelease files / applicationmapper-0.3.1-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | applicationmapper-0.3.1-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8563da4ba9a55bb3d553712f21e2e5582b338916efac1cc584fefc83f2b281ea
|
|
BLAKE2b-256 checksum How to use checksums |
a99a02f84c00ca119be76403f94c90c6f614139c54c0ba30dab821b1a95b005e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 30, 2025.
Transparency logSecurity for applicationmapper 0.3.1
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.
Change of provenance
The repository and configuration that created this release differ from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Repository
Attestation for applicationmapper-0.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 30, 2025.
Transparency logA 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.