You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Hey @MartinBaas-Tivian 👋 Thank you for taking the time to raise this! I took a look around, more specifically at the aws_storagegateway_local_disk data source, since that's where the documentation shows grabbing the disk_id from. That data source uses the ListLocalDisks function from the AWS Go SDK to read information about the disks. Looking at the API reference for the underlying API call, it still shows disk IDs as being in the current format.
With that said, are you seeing differing behavior that led you to initially filing this?
Hi @justinretzolk :)
First: Thank you for looking into this. To be honest, I totally forgot about this issue and I first had to look at what I was doing, when it was raised ^^'
Yes, I vaguely remember seeing a different behavior than the one in the documentation.
Documentation Link
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/storagegateway_upload_buffer
Description
The import example is not correct anymore. Disk IDs changed from path-by-id to unique hexadecimal IDs
e.g.: pci-0000:03:00.0-scsi-0:0:0:0 -> a36d4361-3578-76ea-78ae-12a4f41eace6
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: