Skip to content

Comments

.NET client update#5197

Merged
dsgouda merged 14 commits intoAzure:masterfrom
stefanb995:AddProxyOverrideAndPublicEndpoint
Feb 12, 2019
Merged

.NET client update#5197
dsgouda merged 14 commits intoAzure:masterfrom
stefanb995:AddProxyOverrideAndPublicEndpoint

Conversation

@stefanb995
Copy link
Contributor

@stefanb995 stefanb995 commented Jan 31, 2019

Adding two new parameters to Managed Instance (ProxyOverride and PublicDataEndpointEnabled)
Link to the PR with swagger change on which this code is generated: link

Description


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

General Guidelines

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

SDK Generation Guidelines

  • If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
  • The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

*Adding two new parameters to Managed Instance (ProxyOverride and PublicDataEndpointEnabled)
@msftclas
Copy link

msftclas commented Jan 31, 2019

CLA assistant check
All CLA requirements met.

@stefanb995 stefanb995 closed this Jan 31, 2019
@stefanb995 stefanb995 reopened this Jan 31, 2019
@stefanb995 stefanb995 closed this Jan 31, 2019
@stefanb995 stefanb995 reopened this Feb 1, 2019
@dsgouda
Copy link
Contributor

dsgouda commented Feb 1, 2019

@jaredmoo please approve before I post my review.

Copy link
Contributor

@jaredmoo jaredmoo left a comment

Choose a reason for hiding this comment

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

Discussed offline - needs enum for proxy property.

@stefanb995 stefanb995 closed this Feb 1, 2019
@stefanb995 stefanb995 reopened this Feb 1, 2019
@stefanb995
Copy link
Contributor Author

Here is a link for the PR with the swagger change and examples update.

Copy link
Contributor

@jaredmoo jaredmoo left a comment

Choose a reason for hiding this comment

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

Looks good so far, please update at least 1 scenario test to use the new properties

Updated test to include parameters ProxyOverride and PublicDataEndpointEnabled
@stefanb995
Copy link
Contributor Author

Updated existing scenario test adding these two new parameters.

@stefanb995 stefanb995 closed this Feb 7, 2019
@stefanb995 stefanb995 reopened this Feb 7, 2019
/// <exception cref="System.ArgumentNullException">
/// Thrown when a required parameter is null
/// </exception>
public SqlManagementClient(ServiceClientCredentials credentials, HttpClient httpClient, bool disposeHttpClient) : this(httpClient, disposeHttpClient)
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a breaking change, please bump version to 1.28.0-preview

Copy link
Contributor

Choose a reason for hiding this comment

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

Deepak, is this changed expected from latest autorest? Just want to check.

Copy link
Contributor

Choose a reason for hiding this comment

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

Stefan, when you update csproj with new version, please also wipe out old release notes from 1.27.0 and add your new release notes.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not a 100% sure, but this is coming from AutoRest. @stefanb995 could you install latest autorest version and regen the code (autorest --reset)

SDK ganerated with option -AutoRestVersion "latest" on master azure-rest- api-specs

autorest version: 2.0.4283
@stefanb995
Copy link
Contributor Author

stefanb995 commented Feb 8, 2019

Hey guys, I have regenerated code from master branch.
autorest version is 2.0.4283.
There are some new files generated. Can you please take a look and tell me is this ok.

And deleted methods in SqlManagementClient from previous PR are back.

@jaredmoo
Copy link
Contributor

jaredmoo commented Feb 8, 2019

Please update csproj with new version (1.28.0-preview) and please also wipe out old release notes from 1.27.0 and add your new release notes.

@jaredmoo
Copy link
Contributor

jaredmoo commented Feb 8, 2019

Looks like you picked up sensitivity labels from @bashahee 's Swagger change ( Azure/azure-rest-api-specs#5148 ) , but we can't add that to SDK without tests. @dsgouda , what is your guidance when features get tied up like this?

@stefanb995
Copy link
Contributor Author

Updated csproj.

Please let me know what could I do on my side. Should I just delete these new files and everything added for sensitivity labels?

@dsgouda
Copy link
Contributor

dsgouda commented Feb 8, 2019

Looks like you picked up sensitivity labels from @bashahee 's Swagger change ( Azure/azure-rest-api-specs#5148 ) , but we can't add that to SDK without tests. @dsgouda , what is your guidance when features get tied up like this?

@shahabhijeet could you please take a look

@dsgouda
Copy link
Contributor

dsgouda commented Feb 8, 2019

@jaredmoo If I understand correctly, you are not ready to release the SesitivityLabels feature yet but you would like to release the changes in this PR.
The recommended way to do this is to remove the sensitivityLabel features from the default tag in readme.md so that generated code does not include that spec. Let us know if you have any doubts here

@bashahee
Copy link
Contributor

@jaredmoo @dsgouda Can we please merge these clients? I updated readme.md and swagger files in order to generate clients (our GA is at end of the month), but I see that @stefanb995 already did that, so can our clients be merged along with current PR?

@jaredmoo
Copy link
Contributor

@bashahee we need e2e scenario tests for all APIs, Can you please implement those?

@bashahee
Copy link
Contributor

@bashahee we need e2e scenario tests for all APIs, Can you please implement those?

Yes, I will implement E2E scenario tests once this PR is merged. Is that what you meant?

@jaredmoo
Copy link
Contributor

I mean can you make your own PR that has your own scenario tests? We can merge them both together. (I can help resolve merge during Redmond hours if needed)

@stefanb995
Copy link
Contributor Author

Guys, I need this merged as soon as possible. I need this change to be published to nuget before I send PR for powershell update.

@dsgouda
Copy link
Contributor

dsgouda commented Feb 11, 2019

@stefanb995 @jaredmoo please ensure that the code was regenerated after @bashahee 's changes so that this PR has exactly what you plan to publish in the SDK?
Also please fix the failing tests, please check if the tests are running locally in the Playback mode

@dsgouda
Copy link
Contributor

dsgouda commented Feb 11, 2019

@stefanb995 also link the Rest spec PR for which this SDK is being generated

@stefanb995
Copy link
Contributor Author

@dsgouda I generated this SDK on master branch of Rest spec. I have also attached PR for my Rest spec change.

I forgot to commit session record for the test I updated. I have updated it now. When I run tests in playback mode all tests are passing and 5 tests are being skipped.

@dsgouda
Copy link
Contributor

dsgouda commented Feb 12, 2019

@azuresdkci Test azure-sdk-for-net.client please

@dsgouda
Copy link
Contributor

dsgouda commented Feb 12, 2019

@azuresdkci retest this please

@dsgouda dsgouda merged commit b6b1a9f into Azure:master Feb 12, 2019
@jaredmoo
Copy link
Contributor

We need to make sure that @bashahee has scenario tests for sensitivity labels before publishing

@stefanb995
Copy link
Contributor Author

stefanb995 commented Feb 13, 2019

Can @bashahee update AssemblyInfo.cs file with AssemblyFileVersion (1.28.0.0)?
And please let me know when we are ready to publish.

@bashahee
Copy link
Contributor

@stefanb995 @jaredmoo
I opened a PR containing scenario tests for sensitivity labels clients.
#5240

Moreover, I updated AssemblyInfo.cs.

mentat9 pushed a commit to mentat9/azure-sdk-for-net that referenced this pull request Jun 10, 2019
* .NET client update

*Adding two new parameters to Managed Instance (ProxyOverride and PublicDataEndpointEnabled)

* Delete build.err

* Delete build.wrn

* .NET client update

* Update ManagedInstanceCrudScenarioTests.cs

Updated test to include parameters ProxyOverride and PublicDataEndpointEnabled

* Delete sql_resource-manager.txt

* .NET sdk

SDK ganerated with option -AutoRestVersion "latest" on master azure-rest- api-specs

autorest version: 2.0.4283

* Update sql_resource-manager.txt

* Update Microsoft.Azure.Management.Sql.csproj

* Update of session record for updated test

* Update TestCreateUpdateGetDropManagedInstance.json
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.

6 participants