k8s-build-maps
Build a directory of Kubernetes ConfigMap/Secret manifests, inserting data from files.
Example
Given this directory:
example-manifests/
configmaps/
mymap.yaml
mymap.yaml.files/
file1
file2
Where mymap.yaml looks like:
apiVersion: v1
kind: ConfigMap
metadata:
namespace: mynamespace
name: something
labels:
mylabel: value
Running k8s-build-maps example-manifests example-manifests-built creates this directory:
example-manifests-built/
configmaps/
mymap.yaml
Where mymap.yaml has the following content:
apiVersion: v1
kind: ConfigMap
metadata:
namespace: mynamespace
name: something
labels:
mylabel: value
data:
file2: dGVzdDI=
file1: dGVzdDE=
Installation
pip install k8s-build-maps
Usage
k8s-build-maps SOURCE [DEST] [--clean] [--no-clean] [-q/--quiet] [--debug]
Where:
SOURCE: Required. The source manifest directory.
DEST: Optional if present in build config (see below). The destination manifest directory.
--clean/--no-clean: Pass --clean to remove existing files in DEST before building the manifests. Defaults to --no-clean.
-q/--quiet: Hide output.
--debug: Enable debug logging.
Config file
The SOURCE directory can have an optional .build-maps.yaml config file. This may contain the following values:
dest: DEST path, relative to SOURCE. Can be overridden on the command line.
clean: true or false. Can be overridden on the command line by --clean/--no-clean
Metadata
Release files for k8s-build-maps 0.0.9
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 |
|---|---|---|---|---|
| k8s-build-maps-0.0.9.tar.gz | 4.4 kB | Without provenance | Details for k8s-build-maps-0.0.9.tar.gz |
Release files / k8s-build-maps-0.0.9.tar.gz
| Download URL | k8s-build-maps-0.0.9.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b9ba014b98299306b588a598a9348c79b1b045c297f79f59f33c17a84e3c106
|
|
BLAKE2b-256 checksum How to use checksums |
ae2f81d2a67ac34a93ede1acf3a611adadd18241ad76d84fea82b0ef83b81462
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for k8s-build-maps 0.0.9
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.