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

Update to v1.32.1 of the AzureRM Terraform provider #322

Closed
wants to merge 3 commits into from

Conversation

stack72
Copy link
Contributor

@stack72 stack72 commented Aug 1, 2019

No description provided.

@stack72 stack72 self-assigned this Aug 1, 2019
@stack72 stack72 added area/providers kind/enhancement Improvements or new features labels Aug 1, 2019
@mikhailshilkov
Copy link
Member

Using this version on my laptop, I get

creating urn:pulumi:dev::azure-table::azure:storage/account:Account::storage: Error reading 
queue properties for AzureRM Storage Account "storagef0337dd4": queues.Client#SetServiceProperties: Failure responding to request: StatusCode=403 
-- Original Error: autorest/azure: error response cannot be parsed: 
"\ufeff<?xml version=\"1.0\" encoding=\"utf-8\"?><Error><Code>AuthorizationPermissionMismatch</Code>
<Message>This request is not authorized to perform this operation using this permission.\nRequestId:ffb2702c-2003-0022-7544-48ba40000000
\nTime:2019-08-01T08:38:39.1238286Z</Message></Error>" error: invalid character 'ï' looking for beginning of value

which seems to be this issue hashicorp/terraform-provider-azurerm#3939

Not sure why it happens for me and not CI, but we should be really careful with this update.

@mikhailshilkov
Copy link
Member

As discussed with @stack72, the build fails because TF changed the format of Table IDs from https://account1.table.core.windows.net/table1 to https://account1.table.core.windows.net/Tables('table1'). It seems that we need a migration, TF did it in this PR.

@stack72
Copy link
Contributor Author

stack72 commented Aug 14, 2019

I am going to close this out and reopen it - so much has changed in master that we need to do recreate this scenario

@stack72 stack72 closed this Aug 14, 2019
@stack72 stack72 deleted the stack72/v1.32.1 branch August 14, 2019 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/providers kind/enhancement Improvements or new features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants