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
I do understand from what I've read that when using use_azure_cli_auth the local user's current subscription is being used.
for instance, if my current 'default' subscription is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx then packer tries to use the image URL of SourceImageName: '/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxproviders/Microsoft.Compute/locations/eastus2/publishers/MicrosoftWindowsDesktop/ArtifactTypes/vmimage/offers/Windows-10/skus/win10-22h2-ent-g2/versions/latest'
OR looks for the Vnet I've set in the wrong subscription.
but I've explicitly set the subscription_id and I would expect that setting the subscription_id would tell packer, that no I don't want the default/current subscription but rather I really want you to use the one I've provided.
These are for local test packer builds when I'm testing
Overview of the Issue
I do understand from what I've read that when using
use_azure_cli_auth
the local user's current subscription is being used.for instance, if my current 'default' subscription is
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
then packer tries to use the image URL ofSourceImageName: '/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxproviders/Microsoft.Compute/locations/eastus2/publishers/MicrosoftWindowsDesktop/ArtifactTypes/vmimage/offers/Windows-10/skus/win10-22h2-ent-g2/versions/latest'
OR looks for the Vnet I've set in the wrong subscription.
but I've explicitly set the
subscription_id
and I would expect that setting the subscription_id would tell packer, that no I don't want the default/current subscription but rather I really want you to use the one I've provided.These are for local test packer builds when I'm testing
Reproduction Steps
Plugin and Packer version
Simplified Packer Buildfile
Operating system and Environment details
MacOS Sonoma 14.7.2
Log Fragments and crash.log files
https://gist.github.com/DevopsMercenary/422c8eff546ec79f286ddb569ffc1d65
The text was updated successfully, but these errors were encountered: