-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Conversation
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: 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: |
/check-enforcer override |
/check-enforcer override |
/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)) |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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?
/check-enforcer override |
Added encryption property for Customer Managed Key: [DataFactory]: Add CMK Properties azure-rest-api-specs#10867
Added custom events trigger definition: custom events trigger definition azure-rest-api-specs#12503
Added Policy property into Databricks linkedService, Added admin property in Custom Activity typeProperties
Azure/azure-rest-api-specs#12383
Added managed identity support for authentication in Databricks linkedService: Add Custom Activity User Elevation and scope and Databricks policyId azure-rest-api-specs#12628
Added dualStandbyPairName property: Update swagger for SSIS IR to support SSISDB failover azure-rest-api-specs#12357
Added managedVirtualNetwork reference to IR:[Hub Generated] Review request for Microsoft.DataFactory to add version stable/2018-06-01 azure-rest-api-specs#12339