Closed hashibot closed 6 years ago
hashibot
commented
7 years ago This comment was originally opened by @nrcxcia as https://github.com/hashicorp/terraform/issues/2587#issuecomment-117690286. It was migrated here as part of the provider split. The original comment is below.
This problem does NOT present itself when supplying:
storage_service_name (Optional according to docs)Not sure how that would affect the image.
hashibot
commented
7 years ago This comment was originally opened by @spuder as https://github.com/hashicorp/terraform/issues/2587#issuecomment-140529614. It was migrated here as part of the provider split. The original comment is below.
+1 This also bit me, costing me almost a whole day of work.
No matter what name you use, terraform will fail on azure claiming the name is invalid.
As soon as I added storage_service_name the problem went away.
At the very least, this should be in the documentation.
hashibot
commented
7 years ago This comment was originally opened by @xied75 as https://github.com/hashicorp/terraform/issues/2587#issuecomment-159955592. It was migrated here as part of the provider split. The original comment is below.
Guys, something related, I was trying to deploy CoreOS with specific version, I find it by azure-cli something like this: 2b171e93f07c4903bcad35bda10acf22__CoreOS-Alpha-870.3.0
If I put this in tf I got above error msg. But put in "CoreOS Alpha" does work, so how do we specify the version then? Apparently in above msg we got tons of CoreOS Alpha there which all look the same. :)
vancluever
commented
6 years ago Hello!
Thank you for opening this issue and participating in the discussion. Today (December 19, 2017) we’ve announced the deprecation and archival of the Azure Classic Provider. Matching Microsoft’s commitment to gradually remove access to Azure Classic (or Service Management) which is outlined in this blog post, we are closing all open PR's and Issues here. This repository will remain available here on GitHub, but in an archived state, and no longer receiving support or new releases.
The Azure (Resource Manager) Provider remains fully supported and is our recommended approach for managing Azure with Terraform. More information about this process is available in the blog post linked above.
Thanks! The Terraform Team
This issue was originally opened by @nrcxcia as hashicorp/terraform#2587. It was migrated here as part of the provider split. The original body of the issue is below.
When using the azure provider to setup an instance, no matter what image label I provide it can not find it. Even when I supply an image label that it says is available in the error output it then proceeds to return a different set of images that it says are "available". Here is my code:
Here is the error that is returned: