-
Notifications
You must be signed in to change notification settings - Fork 994
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
generic ephemeral volume with empty metadata causes panic #2198
Comments
Hi @ryanbarry, Thank you for reporting this issue! I will take care of it. |
thanks @arybolovlev – let me know if there's assistance I can provide! and while I'm here, thanks to you and the team for making it easy to build and use a random commit – i'm too impatient to wait for the release that incorporates this functionality, but i was pleasantly surprised by how simple it was to grab the latest main and integrate it 😄 |
Thank you, @ryanbarry! I hope you don't use it in production. On thing that I have noticed is that the schema has one attribute missed. Here is an example of how it looks now: volume {
name = "this"
ephemeral {
metadata {...} // REQUIRED
spec {...}
}
} Here is how it should be: volume {
name = "this"
ephemeral {
volume_claim_template {
metadata {...} // OPTIONAL
spec {...}
}
}
} Since it is not released yet, I am going to make this update. I still need to update a few files to mark PR ready for review, but all in all, I think the code changes are ready. Your feedback is more than welcome! 🙏 Thanks! |
not in production yet, and looks like a good change to me! i'll build a new version, update my usage with the new schema and report back if i have any issues 👨💻 |
Terraform Version, Provider Version and Kubernetes Version
Affected Resource(s)
specifically, the generic ephemeral volumes support added to this in #2183
Terraform Configuration Files
Debug Output
(i don't have this at hand, hopefully it's not necessary but i can come back and add it if it is)
Panic Output
Steps to Reproduce
Expected Behavior
some error before the panic, given an empty metadata block. i added an empty metadata block because when i hadn't specified one within spec.template.spec.volume, i was given an error during planning that it's required ("Insufficient metadata blocks"). once i added the empty metadata block, planning succeeded just fine, but of course applying failed as above.
Actual Behavior
without defining the metadata block, i got an error explaining i needed one, but with an empty one everything seemed to work up until the panic
Community Note
The text was updated successfully, but these errors were encountered: