-
Notifications
You must be signed in to change notification settings - Fork 988
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Introduce raw manifest resource #109
Comments
I've been working on a project that does exactly this. https://github.com/ericchiang/terraform-provider-k8s Would love feedback. |
Cool! Will take a look at it soon. I believe it still would be great to have that in the official Kubernetes provider. Have you thought about contributing that back to this provider @ericchiang? |
I didn't plan to. Would be happy to review PRs from anyone who wanted to add the feature to this one. |
Hi folks 👋 Supporting YAML/JSON was considered before and during the initial implementation of this provider and we decided not to do it. For that reason I'm going to close this issue as we have no intentions of implementing it nor accepting PRs which accept raw configs in JSON/YAML. Feel free to use @ericchiang's provider if you wish. Full discussion: hashicorp/terraform#3132 TL;DR version (summary): hashicorp/terraform#3453 (comment) |
It would be cool if this provider would support creating any resource valid for the current api server just directly in YAML. So that resources that are not natively supported by the provider can still be created using YAML (the fact of having <<HEREDOC for HCL properties is super useful for this) using the behavior similar to
kubectl apply -f
.The text was updated successfully, but these errors were encountered: