-
Notifications
You must be signed in to change notification settings - Fork 63
Conversation
I need this feature. Is there anything I can do to speed this up? |
8fe2749
to
296d25f
Compare
checkpoint: create resource works
…e the realm of cty
296d25f
to
f35039a
Compare
@alexsomesan is this waiting for an upstream Terraform feature to progress? |
@WilliamABradley we are working on a significant upgrade of the provider to use the new provider development modules. This PR is blocked on that change. We're working to get it out the door asap. |
superseded by #151 |
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! |
Description
Introduces a new method of generating the plan by extracting the type information for the resource being planned from the OpenAPI definition available on the API server.
This approach should generate a more complete resource structure, which enable more robust resource lifecycle as all attributes ar being accounted for throughout all operations.
It does not make dry run-calls to the API server during planning, which removes the limitation of not being able to plan resources that depend on one another.
Milestones:
[x] Synthesize Terraform native types from OpenAPI spec
[x] Type-morph the user-supplied resource attributes onto the OpenAPI scaffolding
[x] JSON to Terraform types serialization / deserialization following OpenAPI scaffolding
[ ] Resolve issues in type converter regarding
IntOrString
types and CRD OpenAPI embedded specAcceptance tests