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 #1

Merged
merged 96 commits into from
Jan 28, 2021
Merged

Update #1

merged 96 commits into from
Jan 28, 2021

Conversation

MitchDrage
Copy link
Owner

No description provided.

jcanizalez and others added 30 commits January 10, 2021 17:49
tombuildsstuff and others added 29 commits January 27, 2021 08:43
…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.
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
…work_acls.ip_rules" (#10266)

fix #8701

generally two ways to fix this issue:

only cidr format is allowed
accept cidr and ipv4, when calculate hash, convert ipv4 to cidr
this PR choose the second way
…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
…ns_time_budget` (#10298)

This is a reopen of PR #9280
Previously there is a service bug, now the bug has been fixed.
@MitchDrage MitchDrage merged commit 4b1483a into MitchDrage:master Jan 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.