Support state and individual resources

[jasonckeating]

Is your feature request related to a problem?

Yes, registry state is ignored by the Terraform provider.
If a registry was configured in the UI, Terraform will overwrite it.

importing existing registries is not supported.

Describe the solution you'd like

Registries should be individual resources.
So they can be managed individually and imported. Also, we are wanting to use a foreach so that we can programmatically add many registries.

example: We have many accounts that are members of an org.
Would like Terraform to loop through each account and configure each registry, so many resources don't need to be manually configured.

Describe alternatives you've considered

for_each is not supported for specification blocks {}

Additional context

This has prevented us from hooking up all registries, since there are many.
It has caused our work through the UI to be wiped out many times.

[ericofusco]

@jasonckeating You can use dynamic blocks as an alternative.

https://www.terraform.io/language/expressions/dynamic-blocks

[jasonckeating]

In addition, if one registry is misconfigured or throws an error, the entire run fails with a generic Non-OK status: 400

I'm adding many registries, and there is no indication of what failed.

[jasonckeating]

Checking back in, has this been reviewed?

[maxboynton]

In the version 0.8.0 release (#71) an initial implementation of the individual registry resource has been added under the name prismacloudcompute_resource_registry. Because of some complexities caused by the design of the API endpoints behind this, it is currently only possible to create registries using this resource -- they cannot be removed or updated via terraform. We will look to add those functionalities later on.