Skip to content

Conversation

@aim-for-better
Copy link
Member

@aim-for-better aim-for-better commented Dec 10, 2019

This PR is related with swagger PR [HDInsight] Support kafka rest proxy feature

  1. Support new feature: create kafka cluster with kafka rest proxy
  2. update azure-mgmt-hdinsight version from 1.1.0 to 1.3.0

This checklist is used to make sure that common guidelines for a pull request are followed.

  • The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

  • I adhere to the Command Guidelines.

@aim-for-better aim-for-better added this to the S162 milestone Dec 11, 2019
@aim-for-better
Copy link
Member Author

@Juliehzl Could you please help us review this PR? Can we join S162? I added S162 milestone by myself.

@aim-for-better
Copy link
Member Author

@haroldrandom @Juliehzl Is there someone can help review our PR? It's already 3 work days since we submitted the PR.

@haroldrandom
Copy link
Contributor

haroldrandom commented Dec 13, 2019

Bump SDK version needs to update tests I think?

@Juliehzl Juliehzl self-assigned this Dec 13, 2019
@Juliehzl Juliehzl modified the milestones: S162, S163 Dec 13, 2019
@idear1203
Copy link
Contributor

@haroldrandom The SDK is backward compatible. The newer SDK only adds a few properties to support this new feature. So in general it is not necessary to update tests due to SDK version change.

arg_group='Customer Managed Key', help='Algorithm identifier for encryption.')

# Kafka Rest Proxy
c.argument('kafka_client_group_id', arg_group='Kafka Rest Proxy',
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it possible to provide short name for your argument here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Is it possible to provide short name for your argument here?

Hi @Juliehzl , Thanks. This is the shortest name that can explain the meaning. And there are already some properties' name are longer than this one. For example : workernode_data_disk_storage_account_type=None, workernode_data_disk_size=None,
We should consider the meaning firstly, right?

Copy link
Contributor

Choose a reason for hiding this comment

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

You can provide options_list=['--kafka-client-group-id', '-k'] to give both descriptive name and short name. (Feel free to find a vaild short name here)
The same for the following one.

# Kafka Rest Proxy
c.argument('kafka_client_group_id', arg_group='Kafka Rest Proxy',
help='The client AAD security group id for Kafka Rest Proxy')
c.argument('kafka_client_group_name', arg_group='Kafka Rest Proxy',
Copy link
Contributor

Choose a reason for hiding this comment

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

The same

Copy link
Member Author

Choose a reason for hiding this comment

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

The same

The same with above

@Juliehzl
Copy link
Contributor

@haroldrandom The SDK is backward compatible. The newer SDK only adds a few properties to support this new feature. So in general it is not necessary to update tests due to SDK version change.

We know the newer SDK should be backward compatible, but I think the new SDK may have api version number change, right? Re-recording your tests in hdinsight module based on the new SDK can help double-check the functionality of new SDK and update the request url to make it consistent with the new SDK used. We really recommend you re-record your tests here.

@Juliehzl
Copy link
Contributor

LGTM in general. Please resolve all my comments and if CI agrees I will approve.

@aim-for-better
Copy link
Member Author

@haroldrandom The SDK is backward compatible. The newer SDK only adds a few properties to support this new feature. So in general it is not necessary to update tests due to SDK version change.

We know the newer SDK should be backward compatible, but I think the new SDK may have api version number change, right? Re-recording your tests in hdinsight module based on the new SDK can help double-check the functionality of new SDK and update the request url to make it consistent with the new SDK used. We really recommend you re-record your tests here.

Hi Zunli, I have added a test for the new properties. Thanks

@Juliehzl
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@aim-for-better
Copy link
Member Author

Hi @Juliehzl , how do you like our PR?

@Juliehzl Juliehzl merged commit 5b8878e into Azure:dev Dec 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants