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
When I create a new VM, I use a packer (managed disk) image (imageid stored in consul) in order to create the OS disk. As I'm referencing a self managed image, the only way I seem to be able to nicely use this is by making a full resource id for the storage_image_reference (example below). Is there a nicer way of doing this? Ideally I would see this as a data source for azurerm images.
Terraform Version
latest
Affected Resource(s)
Please list the resources as a list, for example:
azurerm_virtual_machine
azurerm_managed_disk
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Apr 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
When I create a new VM, I use a packer (managed disk) image (imageid stored in consul) in order to create the OS disk. As I'm referencing a self managed image, the only way I seem to be able to nicely use this is by making a full resource id for the storage_image_reference (example below). Is there a nicer way of doing this? Ideally I would see this as a data source for azurerm images.
Terraform Version
latest
Affected Resource(s)
Please list the resources as a list, for example:
azurerm_virtual_machine
azurerm_managed_disk
Terraform Configuration Files
Cheers :)
The text was updated successfully, but these errors were encountered: