Adding support to the LogicApps Workflow Run Delete operation (New).

[aalevato]

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.

[openapi-sdkautomation]

In Testing, Please Ignore

[Logs] (Generated from 32cd45f, Iteration 1)

.NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]

• Microsoft.Azure.Management.Logic [Logs] [Instructions] [Generation PR]

Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]

• azure-mgmt-logic [Logs] [Instructions] [Generation PR]
  • azure-mgmt-logic-4.0.0rc2.zip
  • azure_mgmt_logic-4.0.0rc2-py2.py3-none-any.whl

Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]

• logic/resource-manager/v2016_06_01 [Logs] [Instructions] [Generation PR] [Integration PR]
  • pom.xml
  • azure-mgmt-logic-1.0.0-beta-javadoc.jar
  • azure-mgmt-logic-1.0.0-beta-sources.jar
  • azure-mgmt-logic-1.0.0-beta.jar
• logic/resource-manager/v2018_07_01_preview [Logs] [Instructions] [Generation PR] [Integration PR]
  • pom.xml
  • azure-mgmt-logic-1.0.0-beta-javadoc.jar
  • azure-mgmt-logic-1.0.0-beta-sources.jar
  • azure-mgmt-logic-1.0.0-beta.jar

Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]

• logic/mgmt/2016-06-01 [Logs] [Instructions] [Generation PR] [Integration PR]
  • logic.mgmt.2016-06-01.zip
• preview/logic/mgmt/2015-02-01-preview [Logs]
• preview/logic/mgmt/2015-08-01-preview [Logs]
• preview/logic/mgmt/2018-07-01-preview [Logs] [Instructions] [Generation PR] [Integration PR]
  • preview.logic.mgmt.2018-07-01-preview.zip

JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]

• @azure/arm-logic [Logs] [Instructions] [Generation PR] [Integration PR]
  • azure-arm-logic-6.0.1.tgz

Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]

• No packages generated.

[AutorestCI]

Automation for azure-sdk-for-python

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

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-go

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

[aalevato]

Related to #5755 - as suggested, I will abandon the other PR once this once gets merged. Thanks.

[aalevato]

None of the "check errors" pointed above are on parts of the code that I touched. The code in master already has the "model validation issues" being raised.

[ArcturusZhang]

Hi @aalevato , has the ARM team viewed this api change?

[aalevato]

Hi @ArcturusZhang , they haven't. This API was implemented (and has been in production) since the beginning of the year. The first PR I sent for it was back on May. We're changing our processes as for future API changes to go through the ARM team review, but this one was made before it. Like I said, however, we're referring to an API which is already in production for almost 6 months now.

[ArcturusZhang]

Hi @ArcturusZhang , they haven't. This API was implemented (and has been in production) since the beginning of the year. The first PR I sent for it was back on May. We're changing our processes as for future API changes to go through the ARM team review, but this one was made before it. Like I said, however, we're referring to an API which is already in production for almost 6 months now.

If the ARM team hasn't reviewed these changes, we should wait for them to respond. I will write an email to them if they do not show up till tomorrow

[yungezz]

hi @aalevato could you pls fix model validation error? the error message is self explains. Pls ping us if you have difficult on meanings of error. Those errors will be every of your future PRs if not fixed.

[aalevato]

@yungezz I said before - the errors appearing on the check are for different files. They were already there before my changes (can you run a check on the current master to see it?). It's not the intention of this PR to fix the other files. Can we please move on already? I don't want us dropping in the same infinite bucket as before and wait for months.

[yungezz]

@aalevato yes the modelvalidation is from existing codes in the swagger file. While it will be there in every future PR on this swagger file? Do your team have any plan to fix it? Besides this, this PR is pending on ARM review. After ARM signed off, feel free to ping us for PR merging.

[aalevato]

@ArcturusZhang we still didn't hear back from ARM. Can we please move forward with it? This process had been going already for several months, and the users are eager to use the API (which is already in production) but can't do so because they want to see it on the swagger first.

[aalevato]

Thanks @anthony-c-martin - @yungezz @ArcturusZhang can we merge it now? Thanks!

[aalevato]

@yungezz @ArcturusZhang It says I'm not authorized to merge. Can someone please merge the PR? Thanks!