Resource dependency doesn't work

[dak1n1]

Terraform Version and Provider Version

Terraform v0.12.26
kubernetes-provider-alpha 0.1.0

Affected Resource(s)

kubernetes_manifest

Terraform Configuration Files

Here is the config with an explicit dependency (depends_on).
https://gist.github.com/dak1n1/3dcb14290880d272918bee00a0066c2f

Here is the config with an implicit dependency (referencing the namespace name).
https://gist.github.com/dak1n1/5bf8e59302f44bb11f34c85ec2ff1d4f

Debug Output

Debug trace for explicit dependency:
https://gist.github.com/dak1n1/70a8c5e28d0696f94e6fa063b96ee17c

Debug trace for implicit dependency:
https://gist.github.com/dak1n1/1f993d15185aa348ad96f24f9a793a8f

Expected Behavior

It should create the namespace before it attempts to create the other resources.

Actual Behavior

It errors saying the namespace does not exist.

Error: rpc error: code = Unknown desc = update dry-run for 'test/redis-master' failed: namespaces "test" not found

Steps to Reproduce

1. Download one of the terraform configs attached to this issue and run terraform apply.

Important Factoids

The resources work fine if I create them in a namespace that already exists (like default).

References

• This might be fixed by wait_for A generic way of waiting for a resource to reach a particular state #12

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[alexsomesan]

This is similar to #57

The issue is a known limitation when using server-side planning (detailed in above issue). Will be resolved with the local planner (PR #41)

[dak1n1]

Closing this issue since we're tracking this in #57.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!