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

Feature Request: Azure Event Hub - Add 'Do not emit empty files' option #3057

Closed
sinn1 opened this issue Mar 15, 2019 · 3 comments · Fixed by #3074
Closed

Feature Request: Azure Event Hub - Add 'Do not emit empty files' option #3057

sinn1 opened this issue Mar 15, 2019 · 3 comments · Fixed by #3074

Comments

@sinn1
Copy link

sinn1 commented Mar 15, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Azure Event Hub capture_description doesn't include the option 'Do not emit empty files when no events occur during the Capture time window' which is available in the Azure UI portal.

event-hub-capture

New or Affected Resource(s)

  • azurerm_eventhub

Potential Terraform Configuration

capture_description {
    emitEmptyFiles = false|true
  }
@Lucretius
Copy link
Contributor

I have picked this up and got it working - I just need to add some unit tests.

@ghost
Copy link

ghost commented Apr 3, 2019

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

@ghost
Copy link

ghost commented Apr 20, 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 Apr 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants