Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question/Req - Using a Packer image as a storage reference - Data Source? #371

Closed
tomasquith opened this issue Sep 29, 2017 · 1 comment · Fixed by #382
Closed

Question/Req - Using a Packer image as a storage reference - Data Source? #371

tomasquith opened this issue Sep 29, 2017 · 1 comment · Fixed by #382

Comments

@tomasquith
Copy link

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

  storage_image_reference {
    id = "/subscriptions/${var.subscription_id}/resourceGroups/${var.image_resource_group}/providers/Microsoft.Compute/images/${var.image_id}"
  }

Cheers :)

@ghost
Copy link

ghost commented Apr 1, 2020

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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants