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

azurerm_synapse_firewall_rule - ensure the firewall is ready #19227

Merged
merged 2 commits into from Nov 14, 2022

Conversation

ms-henglu
Copy link
Contributor

fixes #13510

image

Comment on lines +112 to +125
stateChangeConf := &pluginsdk.StateChangeConf{
Pending: []string{string(synapse.ProvisioningStateProvisioning)},
Target: []string{string(synapse.ProvisioningStateSucceeded)},
Refresh: func() (result interface{}, state string, err error) {
resp, err := client.Get(ctx, id.ResourceGroup, id.WorkspaceName, id.Name)
if err != nil {
return nil, "Error", err
}
return resp, string(resp.ProvisioningState), err
},
MinTimeout: 30 * time.Second,
ContinuousTargetOccurence: 3,
Timeout: time.Until(deadline),
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a Swagger bug tracking this API issue? if the Future is being polled on (above) this should be Succeeded at the end of the LRO?

Copy link
Contributor Author

@ms-henglu ms-henglu Nov 11, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, I've added the swagger issue to the comment.

if the Future is being polled on (above) this should be Succeeded at the end of the LRO?

Yes, but it might not take effect immediately, so I add ContinuousTargetOccurence: 3, to ensure it's working.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, I've added the swagger issue to the comment.

👍

if the Future is being polled on (above) this should be Succeeded at the end of the LRO?
Yes, but it might not take effect immediately, so I add ContinuousTargetOccurence: 3, to ensure it's working.

FWIW a Resource Manager operation should be entirely completed when the LRO is marked as ProvisioningState: Succeeded, the ContinuousTargetOccurence would be a workaround until the LRO is fixed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's a workaround.

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🌩️

@katbyte katbyte merged commit 9658dd0 into hashicorp:main Nov 14, 2022
@github-actions github-actions bot added this to the v3.32.0 milestone Nov 14, 2022
katbyte added a commit that referenced this pull request Nov 14, 2022
@github-actions
Copy link

This functionality has been released in v3.32.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Synapse resource met error ClientIpAddressNotAuthorized
3 participants