Chanwit Kaewkasi

Security review for every feature and release going forwards

1

* [ ] Prepare a security checklist to review for every release * [ ] Prepare a process for discussing the security aspect for all features, including the new ones...

Setup a scenario repo to demonstrate how to chain resources and what's the best way to organize resources when using TF objects to destroy Terraform resources.

https://google.github.io/oss-fuzz/getting-started/new-project-guide/go-lang/

Per @phoban01 suggestion, ```yaml writeOutputs: - kind: Secret name: helloworld-output outputs: - key: age_key targetPath: age.agekey ``` This should be re-implemented as part of the `v1alpha2 spec.

After #72

Support generic health check

3

From @phoban01 on #44 Might want to consider adding a successThreshold and failureThreshold to avoid transient network errors triggering health-check failures? Generally, the application of tcp/http healthchecks could be limited,...

import initial tfstate with a secret

2

We currently could do the following to import a TFSTATE for a specify Terraform object. ```shell gzip terraform.tfstate NAME=tf-controller-ng-cc5a1ac4 kubectl create secret \ generic tfstate-default-${NAME} \ --from-file=tfstate=terraform.tfstate.gz \ --dry-run=client -o=yaml...