Closed rivernews closed 3 years ago
Terraform apply error, something in the ASL YAML:
Error: Provider produced inconsistent final plan
│
│ When expanding the plan for module.step_function.aws_sfn_state_machine.this[0] to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws"
│ produced an invalid new value for .definition: was cty.StringVal("\nStartAt: FirstState\nStates:\n FirstState:\n Type: Pass\n Result: \"FirstStateResult\"\n End: true\n"),
│ but now cty.StringVal("\nComment: |\n # AWS State Machine Definition Supports YAML\n #
│ https://aws.amazon.com/about-aws/whats-new/2021/03/aws-step-functions-adds-tooling-support-for-yaml/\n # Based on\n #
│ https://docs.aws.amazon.com/step-functions/latest/dg/development-options.html#development-options-format\n\nStartAt: FirstState\nStates:\n FirstState:\n Type: Pass\n Result:
│ \"FirstStateResult\"\n End: true\n").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Resolve the infra issues first
StatefulSet
instead ofDeployment
when having PVC? -- put this in comment TODO.DO enforce using newer K8s.. now cert-manager is not working. Let's create a branch, and use it to update stuff to latest, then try again.
Then, when the node dev environment is ready again
ClusterIssuer
. Terraform outputsINFO: creating issuer... error: unable to recognize "STDIN": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refused
. Local testing bykubectl apply
further revealserror: error validating "test.yaml": error validating data: [ValidationError(ClusterIssuer.spec.acme): unknown field "dns01" in io.cert-manager.v1.ClusterIssuer.spec.acme, ValidationError(ClusterIssuer.spec.acme.solvers[0].dns01): unknown field "selector" in io.cert-manager.v1.ClusterIssuer.spec.acme.solvers.dns01]; if you choose to ignore these errors, turn validation off with --validate=false
. We need a working example ofClusterIssuer
, using DNS challenge with Route53.error: unable to recognize "STDIN": Get http://localhost:8080/api?timeout=32s: dial tcp 127.0.0.1:8080: connect: connection refused
In the future, to be able to fully use VScode remote-container-k8s...