Your first night with Capact - could be controversial 👀
Alternative scenario:
I spot that current examples don't show another important value of Capact: glue different tools and unify it usage via Capact CLI. Because of that, I thought about a different example.
Currently, in both Implementations we use echo to produce just a different string.
Instead, we could use helm and kubectl CLIs to produce the ConfigMap manifest.
Implementations:
First,helm template hello-world which produces:
# Source: hello-world/templates/config-map.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: hello-world
data:
message: |
Hello World from Helm template
and second, kubectl kustomize hello-world which produces:
apiVersion: v1
data:
message: |
Hello World from Kustomize
kind: ConfigMap
metadata:
name: hello-world
By default, Helm template is used, By using proper Policy, the kubectl kustomize is used instead.
Description
Preview URL:
Changes proposed in this pull request:
Blog related
Alternative titles:
Alternative scenario:
I spot that current examples don't show another important value of Capact: glue different tools and unify it usage via Capact CLI. Because of that, I thought about a different example.
Currently, in both Implementations we use
echo
to produce just a different string. Instead, we could usehelm
andkubectl
CLIs to produce the ConfigMap manifest.Implementations:
helm template hello-world
which produces:kubectl kustomize hello-world
which produces:By default, Helm template is used, By using proper Policy, the
kubectl kustomize
is used instead.Pros:
kubectl
step, as we will use only thecapact ti get
withyq
Cons:
You can download hello-world.zip and execute command describe above.
I discussed that with @pkosiec, but the outcome was that we should keep our example as simple as possible (KISS).
Testing
Populate Hub with manifests from https://github.com/capactio/hub-manifests/pull/53
Related issue(s)
Fix https://github.com/capactio/website/issues/63