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

Event hub namespace with KafkaEnabled property #2395

Merged

Conversation

fedeoliv
Copy link
Contributor

@fedeoliv fedeoliv commented Nov 27, 2018

Implemented feature request #1417 with kafkaEnabled property

(fixes #1417)

@ghost ghost added the size/M label Nov 27, 2018
@fedeoliv fedeoliv changed the title Event hub namespace with KafkaEnabled propperty Event hub namespace with KafkaEnabled property Nov 27, 2018
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.

Hi @fernandoBRS,

Thank you for adding this property! In addition to a few minor comments left inline could we add he new property to the documentation?

It also looks like you are going to need to vender in the newer API version supporting the kafka_enabled property

azurerm/data_source_eventhub_namespace_test.go Outdated Show resolved Hide resolved
azurerm/resource_arm_eventhub_namespace_test.go Outdated Show resolved Hide resolved
katbyte and others added 3 commits November 27, 2018 12:30
Co-Authored-By: fernandoBRS <fedeoliv@microsoft.com>
Co-Authored-By: fernandoBRS <fedeoliv@microsoft.com>
Co-Authored-By: fernandoBRS <fedeoliv@microsoft.com>
@fedeoliv
Copy link
Contributor Author

Hi @katbyte, yes I can add it in the documentation. Is it better to do a different PR for the documentation?

@ghost ghost removed the waiting-response label Nov 27, 2018
@katbyte
Copy link
Collaborator

katbyte commented Nov 27, 2018

Same PR is fine @fernandoBRS 🙂

@fedeoliv
Copy link
Contributor Author

@katbyte the preview version of the Event Hub that supports Kafka has a model structure a bit different compared to the current supported version on Terraform. For example, we can compare the models.go from the 2017-04-01 version with the models.go from the preview version.

I would suggest two approaches:

  • Create a azurerm_eventhub_preview_namespace
  • Refactor the azurerm_eventhub_namespace to use the new API

Do you have any guidance in these approaches?

Thanks!

@ghost ghost removed the waiting-response label Nov 28, 2018
@katbyte
Copy link
Collaborator

katbyte commented Nov 28, 2018

@fernandoBRS,

Looking at the two files the only difference seems to be the additional two fields:
screen shot 2018-11-28 at 13 32 00

I'm not sure what refactoring would be required aside from adding property?

@katbyte
Copy link
Collaborator

katbyte commented Dec 7, 2018

the 2017-04-01/eventhub package gets this property in version 22 of the sdk. It might be best to wait until we upgrade.

@katbyte katbyte modified the milestones: 1.21.0, Blocked Dec 7, 2018
@katbyte katbyte self-assigned this Dec 7, 2018
Copy link

@jackie-goldschmidt jackie-goldschmidt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should there be tests?

@@ -83,7 +84,9 @@ resource "azurerm_eventhub_namespace" "test" {
resource_group_name = "${azurerm_resource_group.test.name}"
sku = "Standard"
capacity = "2"
auto_inflate_enabled = true
auto_inflate_enabled = true

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like line 86 and 87 are duplicates.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A change like this usually means the line break when from \n <--> \n\r

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I don't understand. Are you saying lines 87 and 88 are not duplicates, but appear so due to github formatting? It looks to me like they are two green + lines with the same content.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh my apologies, you are definitely correct. Line 88 didn't appear in the conversation view.

@katbyte
Copy link
Collaborator

katbyte commented Dec 7, 2018

Yep, this should definitely be added to a test

Copy link

@jackie-goldschmidt jackie-goldschmidt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please provide tests that prove this change works as expected.

Copy link

@jackie-goldschmidt jackie-goldschmidt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please provide tests that prove this change works as expected.

@@ -83,7 +84,9 @@ resource "azurerm_eventhub_namespace" "test" {
resource_group_name = "${azurerm_resource_group.test.name}"
sku = "Standard"
capacity = "2"
auto_inflate_enabled = true
auto_inflate_enabled = true

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I don't understand. Are you saying lines 87 and 88 are not duplicates, but appear so due to github formatting? It looks to me like they are two green + lines with the same content.

@katbyte
Copy link
Collaborator

katbyte commented Dec 28, 2018

Depends on #2572

@katbyte katbyte added upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR and removed upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR labels Jan 6, 2019
@katbyte katbyte modified the milestones: Blocked, 1.21.0 Jan 8, 2019
@ghost ghost added the documentation label Jan 9, 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.

@fernandoBRS,

We have updated the SDK to v24 and unblocked this. I hope you don't mind but i made the required changes 🙂 LGTM now 🚀

@katbyte katbyte merged commit 3012599 into hashicorp:master Jan 9, 2019
katbyte added a commit that referenced this pull request Jan 9, 2019
@fedeoliv
Copy link
Contributor Author

fedeoliv commented Jan 9, 2019

Good news, thanks for the support @katbyte ! 🚀

@ghost
Copy link

ghost commented Mar 5, 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 Mar 5, 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.

Feature Request : Azure Event Hub kafka Enabled
4 participants