Parasyris Nikolaos

Hello, thanks for reporting this. It is indeed a nice feature we should support. This needs to be implemented upstream first. Related ticket => https://github.com/gophercloud/gophercloud/issues/2205

@SvenDowideit just for reference, are you using octavia or not?

Clarifying a bit the `openstack_lb_loadbalancer_v2` resource: The `vip_subnet_id` is required for LBaaS but optional for octavia. This is in the documentation. For octavia **one** of the `vip_subnet_id`, `vip_network_id` or `vip_port_id`...

Hi @fobrice. Thanks for reporting this. I expect the reason for this behavior can be found [here](https://github.com/terraform-provider-openstack/terraform-provider-openstack/blob/2665d4c052f3224481919071355d7cdd94dd92f5/openstack/resource_openstack_blockstorage_quotaset_v3.go#L170-L176). The reasoning behind conditionally writing the volume_type_quota was: - didn't want to introduce...

I'm not sure a `composed id` would work in this case. The role_assignment resource is a bit different in nature. A single blockstorage quota resource handles quotas for multiple(all) volume_types....

Hello @zhujinhe This is currently not implemented although it can be a useful new data source. Personally I won't be able to work on this any time soon. Of course...

Can you post send gist of the output `TF_LOG=DEBUG terraform plan` and `apply`? Btw I think your code can be simplified (and also probably do not trigger this behavior) with:...

I think i have an idea of why this occurs after reading some docs and code. In simple "steps": - terraform accepts both names and/or ids in `security_groups` as this...

Thanks @goldpanic. ill have a look later this week. As this behavior is mostly due to how nova api behaves (accepting both ids and names but responding only with names)...

Great! Thanks for your help!