Add 2 missing endpoints to newest versions Microsoft.Logic

[refortie]

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

• The title of the PR 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 information on cleaning up the commits in your pull request, see this page.
• Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
• If applicable, the PR references the bug/issue that it fixes.
• Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[AutorestCI]

Automation for azure-sdk-for-java

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

[AutorestCI]

Automation for azure-sdk-for-js

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

[AutorestCI]

Automation for azure-sdk-for-ruby

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

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-node

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

[AutorestCI]

Automation for azure-sdk-for-python

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

[AutorestCI]

Automation for azure-sdk-for-go

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

[refortie]

@lmazuel Could I get some eyes on this? Also, What's is your guys' SLA? The link for it on the contributions page is dead.

[lmazuel]

Hi @refortie
Sorry for the late review, I thought I could keep up with review last week, but I should have reassigned it and assume time will be missing :(
Looking at it right now.
Thanks you

[lmazuel]

@AutorestCI rebuild azure-sdk-for-java

[lmazuel]

Hi @refortie
There is important model validation issue. I know most of them are not introduced in your PR, but would be nice if you can try to understand and tell your team. "unresolved reference" will likely create invalid SDK.

[refortie]

Hi @lmazuel,

So I must not understand this correctly, the model we provide in the workflow examples and such does exist. If you got to the page, it resolves with a 200 with the actual schema. Is that not correct?

[lmazuel]

@sergey-shandar help on the "unresolved reference". Is this because the final # ?

[ravbhatnagar]

Looks good, just one minor note.

[ravbhatnagar]

Signing off from ARM side, just one minor note which needs to be fixed.