Closed laurodias closed 3 months ago
@laurodias See a problem with creating the cloudamqp_vpc_connect
data source. Since it will not automatically reload when changes are done to the instance. One way to force all resources and data sources to read out the data from backend is to use terraform apply -refresh-only
Instead, added the availability_zone
to the nodes data source. Each node will now display the availability zone ID. Also made sure the AZ got updated, after the instance update.
Created a new release v1.30.1 with availability_zone
available for all nodes.
Closing the issue, feel free to re-open if there are any more questions.
Currently there are no resources or data sources that export nodes availability zones, except for the
active_zones
attribute bycloudamqp_privatelink_aws
/cloudamqp_vpc_connect
. However, the attribute doesn't get updated when an instance is resized until a next plan/apply.As the console states that
If you add more servers to this cluster you will need to go back to the AWS console, edit the endpoint and add the additional subnets
, updatingcloudamqp_nodes
data source to be incremented with nodes availability zone IDs could be helpful to triggeraws_vpc_endpoint
update. My use case is:I think that could also be achieved if we had a
cloudamqp_vpc_connect
data source to be loaded after instance update.