[HDInsight] KafkaRestProperties should not require groupName given groupId has been specified

[magodo]

The ClientGroupInfo property already accept a groupId in request body, based on which service should be able to deduce the groupName. This issue suggest to remove the groupName from the model as an input property.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aim-for-better, @idear1203, @deshriva.

[aim-for-better]

Hi @magodo , This is by design, This property not only as input but also as output. Please see here, This property will return to customer when they call Get cluster API.

[aim-for-better]

Hi @magodo , This is by design, This property not only as input but also as output. Please see here, This property will return to customer when they call Get cluster API.

Returning group name is more readable for customer.

Could you please share more about this issue? For example, what's the impact on you?

[magodo]

As the API consumer, it is more handy to provide the least amout of input in request. In this case, groupName can be deduced from groupId, which seems redundent to ask users to also specify. Otherwise, making groupName as output only (readOnly) might be a better choice here.

Specifically, I'm working on this feature in Terraform azurerm provider. Check out this comment: hashicorp/terraform-provider-azurerm#8064 (comment)

[deshriva]

@magodo : Thanks for the feedback. We have opened a work item and plan to address it in a future release.

[deshriva]

@magodo : Can we close this request, we have a work item and this change will be rolled out with a new API version.

[magodo]

@deshriva Thank you for the update, can we wait until the Swagger PR for that new API version is merged?

[aim-for-better]

Thanks for the feedback. We have opened a work item and plan to address it in a future release.

[aim-for-better]

on going

[aim-for-better]

on going

[aim-for-better]

on going

[aim-for-better]

on going