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

New Resource: azurerm_container_registry_webhook #4112

Merged

Conversation

r0bnet
Copy link
Contributor

@r0bnet r0bnet commented Aug 18, 2019

Implementation of a Container Registry Webhook.

Was requested here: #4067

(fixes #4067)

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.

Thank you for the PR @r0bnet,

Overall this is looking great, in addition to a couple minor comments i've left inline i'm seeing a test failure:

------- Stdout: -------
=== RUN   TestAccAzureRMContainerRegistryWebhook_Actions
=== PAUSE TestAccAzureRMContainerRegistryWebhook_Actions
=== CONT  TestAccAzureRMContainerRegistryWebhook_Actions
--- FAIL: TestAccAzureRMContainerRegistryWebhook_Actions (98.84s)
    testing.go:568: Step 0 error: Check failed: Check 3/3 error: azurerm_container_registry_webhook.test: Attribute 'actions.0' not found
FAIL

azurerm/resource_arm_container_registry_webhook.go Outdated Show resolved Hide resolved
azurerm/resource_arm_container_registry_webhook.go Outdated Show resolved Hide resolved
azurerm/resource_arm_container_registry_webhook.go Outdated Show resolved Hide resolved
@katbyte katbyte added this to the v1.34.0 milestone Aug 18, 2019
@r0bnet
Copy link
Contributor Author

r0bnet commented Aug 19, 2019

Hey @katbyte
thought i executed the test locally but seems like i skipped it somehow. Was wrong because actions is a set. Fixed the test accordingly. Should be fine now :)

@ghost ghost removed the waiting-response label Aug 19, 2019
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.

Thanks @r0bnet!

I hope you don't mind but i've swapped over to explicitly use constants. We avoid using the auto generated lists as sometimes the azure SDK drops support for them randomly and that could potentially break people. this way we know if a new SDK version drops it and can investigate if its valid or not.

LGTM now 👍

@katbyte katbyte modified the milestones: v1.34.0, v1.33.0 Aug 19, 2019
katbyte added a commit that referenced this pull request Aug 19, 2019
@katbyte katbyte merged commit 08f3e77 into hashicorp:master Aug 19, 2019
@ghost
Copy link

ghost commented Aug 22, 2019

This has been released in version 1.33.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 = "~> 1.33.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Sep 19, 2019

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!

@ghost ghost locked and limited conversation to collaborators Sep 19, 2019
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.

New resource azurerm_container_registry_webhook
2 participants