Just wanted to drop a big +1 to everything communicated in this thread. I found myself in the exact same situation @alexray described, wanting to pair up cloud-init with an antlet provisioning process, as well as create a vnic via TF like @soneill but the API shortcomings do certainly throw a wrench into those awesome plans. As much as I'd like to take matters into my own hands and cobble something together on the openapi provider side of things, polishing the API is probably the ideal fix. I doubt I could justify a contribution designed as a crutch for this one particular API; I imagine the response would be "No, openapi provider is fine, make the API compliant and it'll work like it's supposed to".
I'd also like to toss into the wishing well, concerning API updates to get the swagger file happy, that I'd love to see a boolean property in the POST /api/antlets call that enables powering on the created antlet immediately after creation.
@daniel-luck Waiting for that update got me like
Just wanted to drop a big +1 to everything communicated in this thread. I found myself in the exact same situation @alexray described, wanting to pair up cloud-init with an antlet provisioning process, as well as create a vnic via TF like @soneill but the API shortcomings do certainly throw a wrench into those awesome plans. As much as I'd like to take matters into my own hands and cobble something together on the openapi provider side of things, polishing the API is probably the ideal fix. I doubt I could justify a contribution designed as a crutch for this one particular API; I imagine the response would be "No, openapi provider is fine, make the API compliant and it'll work like it's supposed to".
I'd also like to toss into the wishing well, concerning API updates to get the swagger file happy, that I'd love to see a boolean property in the POST /api/antlets call that enables powering on the created antlet immediately after creation.
@daniel-luck Waiting for that update got me like
daniel.luck has reacted to this post.