Closed javiertury closed 1 year ago
Thanks for reporting this. The version is indeed outdated and I should bump it in the docs.
The keys of the map need to match the name of your workspace. terraform workspace list
As for your second example, the default needs to replace apps and ops. Not wrap it. See below:
module "example_custom_manifests" {
providers = {
kustomization = kustomization.gke_gc0_europe-west1
}
source = "kbst.xyz/catalog/custom-manifests/kustomization"
version = "0.4.0"
configuration_base_key = "default"
configuration = {
default = {
resources = [
"${path.root}/manifests/example/upstream.yaml"
]
}
}
}
The example located in the following documentation page does not work for me, and I suspect it may be wrong or outdated.
https://www.kubestack.com/framework/documentation/extending-kubestack/#kubernetes-manifests
I'm referring to the usage of
apps
andops
properties incustom-manifests
. Note that I changed version0.3.0
to0.4.0
because otherwise I get an error in terraform. When runningterraform apply
, the following module finishes "successfully" but terraform completely ignoresupstream.yaml
.Using the
default
configuration base key doesn't help.However other examples from other documentation sources work fine. Note that I changed version
0.3.0
to0.4.0
because otherwise I get an error in terraform