forked from hashicorp/terraform-provider-azurerm
-
Notifications
You must be signed in to change notification settings - Fork 0
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 #1
Merged
Merged
Update #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Tom Harvey <[email protected]>
…eve it's name This avoids calling the `ListKeyVaults` API call by querying the resource list to locate this specific resource by it's identifier and type instead.
Co-authored-by: Steve <[email protected]>
Co-authored-by: Steve <[email protected]>
Co-authored-by: Steve <[email protected]>
UPDATE delete VMs that are in failed state
New resource: `azurerm_media_streaming_policy`
…g-part-ii keyvault: optimising the lookup/adding a cache for Key Vaults
This won't take effect until binary testing is enabled but there's no harm in staying up to date here
Allow ADLS File System to have ACLs added to the root
…n-docs [Docs]`function_app` Regional VNet Integration
tc: updating the default version of tf to 0.14.4
) * fix #8577 * change the `assignable_scopes` back to required * update per review
…city to 16 for Premium SKU (#10337) Allowed the azurerm_servicebus_namespace resource to support the capacity of 16 for the number of messaging units to be set when using the Premium SKU. Microsoft documentation (docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-premium-messaging) only shows support for a capacity of up to 8, but we have been able to request 16 due to high levels of throttling at 8. Microsoft has confirmed going up to 16 is not possible in the portal, but customers can request it via a support ticket. This change is essential for us as Terraform wants to keep reverting our capacity back to 8:
#10305) This is the implementation of new resource based on demand from: #6174 Please review and let me know if you can merge to TF provider. Generally copy/paste from exisitng azurerm_data_factory_linked_service_azure_blob_storage and also fixing some items in azurerm_data_factory_linked_service_azure_blob_storage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.