Small correction to list handling

[leonardbf]

Still preview - breaking changes not an issue

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[AutorestCI]

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#4622

[AutorestCI]

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#4364

[AutorestCI]

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

[azuresdkci]

Can one of the admins verify this patch?

[adxsdknet]

Automation for azure-sdk-for-net

A PR has been created for you:
Azure/azure-sdk-for-net#5536
.NET SDK Commits:
adxsdknet/azure-sdk-for-net@d18bcd7
adxsdknet/azure-sdk-for-net@f4f7e6e

[leonardbf]

This is just a small change and a quick turn around would be really appreciated. Many thanks.

[AutorestCI]

Automation for azure-sdk-for-js

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-js#1740

[dsgouda]

@leonardbf could you clean up the commit history here (git rebase -i)

[AutorestCI]

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

[leonardbf]

@leonardbf could you clean up the commit history here (git rebase -i)

Thanks for a quick response. Can you give me the full steps for this? Do you mean simply clone my master branch, perform git rebase -i then push back to master? Note this commit history is from earlier commits that have already been merged. This last change was a single commit - does that make a difference? If not then I could perform this squash on my next commit. I was hoping this one could be merged quickly so the SDKs can be generated as soon as possible.

[dsgouda]

@leonardbf pull from latest Azure master to your master, if this doesn't work you can simply clone Azure master and copy over your changes in a new branch (hacky and you can skip if it's too much work)

[leonardbf]

@leonardbf pull from latest Azure master to your master, if this doesn't work you can simply clone Azure master and copy over your changes in a new branch (hacky and you can skip if it's too much work)

Hmm, this was actually a clean branch that I pushed from a newly cloned repo. I did it that way because there were merge conflicts. I'm not really sure why this commit history is here.

@dsgouda Is this a blocker? While I understand the interest in a clean commit history, it's like you say, trying to sort it can be more effort than it's worth especially when time is short.

[leonardbf]

@dsgouda hey, I see you tried to contact me on the devex teams channel. I've noticed previously that this is only accessible to me on my SAW machine which is in the office. Teams on my development laptop does not show this channel even when clicking through from the email to my b- account you triggered in Teams (I'm assuming you are on Pacific Time but I'm on UTC in Iceland and won't be in the office for 8 hours or so).

[dsgouda]

LGTM