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

Add 'tags' to Notification hub and Namespace #3872

Closed
ghost opened this issue Jul 18, 2019 · 3 comments
Closed

Add 'tags' to Notification hub and Namespace #3872

ghost opened this issue Jul 18, 2019 · 3 comments
Labels
enhancement service/notifications upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR
Milestone

Comments

@ghost
Copy link

ghost commented Jul 18, 2019

This issue was originally opened by @ashwinippatil26 as hashicorp/terraform#22122. It was migrated here as a result of the provider split. The original body of the issue is below.


The Messaging Resources - azurerm_notification_hub and azurerm_notification_hub_namespace don't support tags arguments. See the error below -

Error: Unsupported argument

  on main.tf line 55, in resource "azurerm_notification_hub" "notification":
  55:                 tags = local.tags

An argument named "tags" is not expected here.

Please update the resources to add this argumen.

@tombuildsstuff tombuildsstuff added the upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR label Jul 18, 2019
@tombuildsstuff
Copy link
Member

hi @ashwinippatil26

Thanks for opening this issue.

Just to let you know that unfortunately this is blocked on an upstream bug in the Azure API's which is being tracked here - once that's resolved it'll be possible for someone to take a look into this. Until that's resolved there's not a lot we can do with this unfortunately, as such for the moment I'm going to tag this as upstream-microsoft (which we use to indicate this issue is blocked upstream).

Thanks!

@tombuildsstuff tombuildsstuff added this to the Blocked milestone Aug 14, 2019
@katbyte katbyte modified the milestones: Blocked, v2.7.0 Apr 23, 2020
katbyte pushed a commit that referenced this issue Apr 23, 2020
@katbyte katbyte modified the milestones: v2.7.0, v2.8.0 Apr 23, 2020
@katbyte katbyte modified the milestones: v2.8.0, v2.9.0 Apr 30, 2020
@tombuildsstuff tombuildsstuff modified the milestones: v2.9.0, v2.7.0 May 7, 2020
@tombuildsstuff
Copy link
Member

Fixed via #6578

@ghost
Copy link
Author

ghost commented Jun 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 Jun 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement service/notifications upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR
Projects
None yet
Development

No branches or pull requests

2 participants