Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DataFactory] Add new features in version 4.14.0 #18309

Merged
merged 9 commits into from
Feb 3, 2021
Merged

[DataFactory] Add new features in version 4.14.0 #18309

merged 9 commits into from
Feb 3, 2021

Conversation

Jingshu923
Copy link
Contributor

@Jingshu923 Jingshu923 commented Feb 1, 2021

Azure/azure-rest-api-specs#12383

@check-enforcer
Copy link

check-enforcer bot commented Feb 1, 2021

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run net - [service] - ci

@Jingshu923
Copy link
Contributor Author

/check-enforcer override

@Jingshu923
Copy link
Contributor Author

/check-enforcer override

@Jingshu923
Copy link
Contributor Author

/check-enforcer override

/// <param name="tenant">The name or ID of the tenant to which the
/// service principal belongs. Type: string (or Expression with
/// resultType string).</param>
public AzureDataExplorerLinkedService(object endpoint, object database, IDictionary<string, object> additionalProperties = default(IDictionary<string, object>), IntegrationRuntimeReference connectVia = default(IntegrationRuntimeReference), string description = default(string), IDictionary<string, ParameterSpecification> parameters = default(IDictionary<string, ParameterSpecification>), IList<object> annotations = default(IList<object>), object servicePrincipalId = default(object), SecretBase servicePrincipalKey = default(SecretBase), object tenant = default(object))
Copy link
Member

Choose a reason for hiding this comment

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

this will result in a breaking change, please have the breaking change approval board add the "Approved-BreakingChange" label to Azure/azure-rest-api-specs#12755

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@m-nash This change has been reverted in this PR Azure/azure-rest-api-specs#12769, Could you review this again?

@Jingshu923
Copy link
Contributor Author

/check-enforcer override

@m-nash m-nash merged commit 0dc804a into Azure:ADFDev Feb 3, 2021
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.

3 participants