Sync up Domain Objects about terraform-provider-fusionauth

[MCBrandenburg]

@robotdan I will try to get these added over the course of this weekend.

I think building that way should be a goal main things needed would be to known:

• computed, optional, required
• defaults if applicable
• description(I've been copying and pasting from the api docs)

[robotdan]

Ok, let me think about this, and see if the team has any good ideas. It would be cool if we could produce enough meta data from our build that would all you to convert it directly into a resource schema or something like that.

[mooreds]

If we end up building an OpenAPI spec ( FusionAuth/fusionauth-issues#614 ), I think that this project would be useful to address this issue: https://github.com/dikhan/terraform-provider-openapi

[drpebcak]

The openapi provider seems cool conceptually, but it sounds like a nightmare to use. Having the spec be dynamic will likely cause issues with the state and resources needing to be modified unnecessarily (especially when it comes to attributes that are computed). I can see this causing some big problems during breaking api changes as well - having your resource names and everything mapped to endpoint names means that changing endpoint names will require migration or deletion/recreation of resources. That is one of the things terraform is great about.. abstraction.

It also means that no validation can be done during the plan phase to ensure that args are valid before attempting to apply, no special helper methods can be added to do things like work around formatting differences between the source and api response, configuring dependencies between objects in the api, lifecycle management of resources, etc.

[MCBrandenburg]

@robotdan these updates should be out in v0.1.25