This message was deleted.
# azures
sparse-intern-71089
02/11/2021, 2:23 AMThis message was deleted.
t
tall-needle-56640
02/11/2021, 2:30 AMCan you run
pulumi up --logtostderr -v=3b
bright-eve-47520
02/11/2021, 2:31 AMI was using -v=9, is 9 deeper than 3?
bright-eve-47520
02/11/2021, 2:44 AMLevel 3 doesn’t give much
t
tall-librarian-49374
02/11/2021, 7:46 AMThe highest logging is with
-v=9 --logtostderr --debug --logflow🙂 1
b
bright-eve-47520
02/12/2021, 1:39 AMThat’s much better thanks!
bright-eve-47520
02/12/2021, 1:41 AMLooks like the responses from MS are 404s
bright-eve-47520
02/12/2021, 1:52 AMLooks like I’m using the wrong outputs to pass as inputs to another resource. Such as product.Id and api.Id for inputs ProductId and ApiId. Would probably be more intuitive if these inputs were called ProductName and ApiName so it’s more intuitive to pass product.Name and api.Name. This is already the case for ResourceGroupName that’s an input to most resources
bright-eve-47520
02/12/2021, 1:53 AMThe 2 resources that caught me out were ApiPolicy and ProductApi in ApiManagement
t
tall-needle-56640
02/12/2021, 2:02 AMAzureNG pulls directly from the Azure API specs. Whatever it allows, Pulumi.AzureNextGen allows. If you need something else, you can use the Azure SDK or create something yourself that does a lookup.
b
bright-eve-47520
02/12/2021, 2:10 AMIt’s not a matter of not being able to do something, I fixed my code and now it works. It just wasn’t intuitive to pass a “Name” output from 1 resource to an “Id” input of another when there’s also an “Id” output on that resource. Now I know that all the Id outputs contain an entire path to the resource and the inputs generally just want the name.
However the side effect of this simple user error was the above message that the error couldn’t be parsed. Not very helpful. The response from Azure was a 404 which lead me to look at the URL and see the encoded path where the product name looked like it should be.
I guess a simple improvement would be for the Pulumi error parser to recognise a 404 response with no body and output that information as a build error, instead of noting the EOF. Including the ARM resource URL with the 404 message could help people identify their error.
t
tall-needle-56640
02/12/2021, 2:40 AMYou should file an issue for that. I would love to see that.
👍 2
5 Views