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_iothub_shared_access_policy - prevent primary_connection_string & seconday_connection_string from regenerating #8017

Merged
merged 1 commit into from Aug 6, 2020

Conversation

neil-yechenwei
Copy link
Contributor

@neil-yechenwei neil-yechenwei commented Aug 5, 2020

fixes #7445

--- PASS: TestAccAzureRMIotHubSharedAccessPolicy_writeWithoutRead (9.74s)
--- PASS: TestAccAzureRMIotHubSharedAccessPolicy_basic (401.00s)
--- PASS: TestAccAzureRMIotHubSharedAccessPolicy_requiresImport (563.10s)
PASS
ok

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 changed the title Add existing primiary key and secondary key to http request body while updating azurerm_iothub_shared_access_policy azurerm_iothub_shared_access_policy - prevent primary_connection_string & seconday_connection_string from regenerating Aug 6, 2020
@katbyte katbyte added this to the v2.22.0 milestone Aug 6, 2020
@katbyte katbyte merged commit 53085d2 into hashicorp:master Aug 6, 2020
katbyte added a commit that referenced this pull request Aug 6, 2020
@ghost
Copy link

ghost commented Aug 7, 2020

This has been released in version 2.22.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.22.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Sep 6, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@hashicorp hashicorp locked and limited conversation to collaborators Sep 6, 2020
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.

IoT Hub Shared Access Policy should not change Key after changing permissions
2 participants