2 Commits (efb7a27a3ab7dda4d3a2d35c1a725df2c6db6318)

Author	SHA1	Message	Date
Kingdon Barrett	efb7a27a3a	capitalize Jsonnet in some places ... Just the bare minimum add new text to explain the change to kubecfg This PR should be reopened as the `jsonnet-gutted` branch, with commentary removed and slimmed down to just code examples with as little non-embedded commentary as possible. This way we can consider reorganizing any pieces that would need to be redone for example in a hypothetical Jenkins+cdk8s use case document, or something else like Gitlab+Tanka, or Tekton+kubecfg, or any combination. If we are going to document outside solutions and proper integrations with them, then we should probably make their treatments as equal as possible to avoid showing favoritism.	4 years ago
Kingdon Barrett	d68991f514	decide on a home for the jsonnet ... "release-manifests.yaml" workflow which targets releasing tags that are labeled as a release, or commits that are pushed on the release branch. add more detail in jsonnet example section more text There might be some overlap with the SOPS/Azure KMS example that Leigh provided re-align with #1064 fixup text substantial rework in introduction more text that hasn't been in a commit yet more organization more commentary	4 years ago