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

bugfix: azurerm_stream_analytics_job resource does not set tags #3329

Merged

Conversation

maxbog
Copy link
Contributor

@maxbog maxbog commented Apr 29, 2019

fixed the bug, added a test and documentation

@maxbog maxbog force-pushed the b/apply_tags_to_stream_analytics_job branch from 2faee4b to 55b37bc Compare April 29, 2019 12:19
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 for this @maxbog, LGTM 👍

@katbyte katbyte added this to the v1.28.0 milestone Apr 29, 2019
@katbyte katbyte merged commit 992ad3b into hashicorp:master Apr 29, 2019
katbyte added a commit that referenced this pull request Apr 29, 2019
@ghost
Copy link

ghost commented May 17, 2019

This has been released in version 1.28.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.28.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented May 30, 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 May 30, 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.

2 participants