support Express Custom Setup

[liubing-microsoft]

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 fc0bdde, Iteration 8)

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

• Microsoft.Azure.Management.DataFactory [Logs] [Instructions]
  • Microsoft.Azure.Management.DataFactory.4.1.2.nupkg
  • Microsoft.Azure.Management.DataFactory.4.1.2.snupkg

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

• No packages generated.

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

• datafactory/resource-manager/v2017_09_01_preview [Logs]
• datafactory/resource-manager/v2018_06_01 [Logs]

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

• datafactory/mgmt/2018-06-01 [Logs]
• preview/datafactory/mgmt/2017-09-01-preview [Logs]

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

• Package generation in progress.

[AutorestCI]

Automation for azure-sdk-for-python

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-python#7023

[AutorestCI]

Automation for azure-sdk-for-go

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

[azuresdkci]

Can one of the admins verify this patch?

[ArcturusZhang]

Semantic and LintDiff checks fail, please fix this.

[liubing-microsoft]

Hi @ArcturusZhang , I have updated my changes but the semantic check is still failed which is not introduced by my changes. How to handle it?

error :
code: OAV131
error: DISCRIMINATOR_NOT_REQUIRED
name: discriminator
params:

• type
  message: discriminator must be a required property.
  path:
• 'definitions,IntegrationRuntimeStatus'

error :
code: OAV131
error: DISCRIMINATOR_NOT_REQUIRED
name: discriminator
params:

• type
  message: discriminator must be a required property.
  path:
• 'definitions,SsisObjectMetadata'

[ArcturusZhang]

Hi @ArcturusZhang , I have updated my changes but the semantic check is still failed which is not introduced by my changes. How to handle it?

error :
code: OAV131
error: DISCRIMINATOR_NOT_REQUIRED
name: discriminator
params:

• type
  message: discriminator must be a required property.
  path:
• 'definitions,IntegrationRuntimeStatus'

error :
code: OAV131
error: DISCRIMINATOR_NOT_REQUIRED
name: discriminator
params:

• type
  message: discriminator must be a required property.
  path:
• 'definitions,SsisObjectMetadata'

This is caused by something changed in the semantic tool. I asked owner of CI @NullMDR how to resolve this, but do not get reply right now. After they resolve this issue, we can re-run the tests.

[liubing-microsoft]

@ArcturusZhang , Could you tell me when the semantic tool issue can be resolved? It will block our feature release. Thank you.

[raych1]

@liubing-microsoft , the semantic errors was fixed by PR, please merge the change and re-run semantic check, it should pass.

[liubing-microsoft]

Semantic and LintDiff checks fail, please fix this.

Hi @ArcturusZhang , all checks have passed.

[ArcturusZhang]

Semantic and LintDiff checks fail, please fix this.

Hi @ArcturusZhang , all checks have passed.

I approved this. But please wait for ARM team response before you merge this

[ravbhatnagar]

this is typically a breaking change, but for ADF the scenario is a bit more nuanced. We have discussed this in person in the past and given them exception with the understanding that we will bring up this usecase in front of folks like MarkRuss and seek guidance. Signing off from ARM side.