TF provider import not fully hydrate NS sub-blocks
Community Note
- Please vote on this issue by adding a
馃憤 reaction to the original
issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra
noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
So, when trying to import existing terraform namespaces, and it seems a lot of the resource blocks don't allow importing or setting the state variables.
resource "pulsar_namespace" "test" {
....
namespace = "test"
dispatch_rate {
dispatch_msg_throttling_rate = 50
rate_period_seconds = 50
dispatch_byte_throttling_rate = 2048
}
}
terraform import for pulsar_namespace produces spurious dispatch_rate plan drift because the provider's Read function only populates optional blocks when they already exist in state - seem to be a known provider limitation with no current fix; workaround is to verify values with pulsar-admin before applying, pls look into unconditional import reads.
New or Affected Resource(s)
Potential Terraform Configuration
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.
References
TF provider import not fully hydrate NS sub-blocks
Community Note
馃憤 reaction to the original
issue to help the community and maintainers prioritize this request
noise for issue followers and do not help prioritize the request
Description
So, when trying to import existing terraform namespaces, and it seems a lot of the resource blocks don't allow importing or setting the state variables.
terraform import for pulsar_namespace produces spurious dispatch_rate plan drift because the provider's Read function only populates optional blocks when they already exist in state - seem to be a known provider limitation with no current fix; workaround is to verify values with pulsar-admin before applying, pls look into unconditional import reads.
New or Affected Resource(s)
Potential Terraform Configuration
References