SSIS File System Support

[HaoQian-MS]

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]

SDK Automation [Logs] (Generated from 29f3be5)

Python: Azure/azure-sdk-for-python [Logs]

• No packages generated.

Java: Azure/azure-sdk-for-java [Logs]

• Package generation in progress.

Go: Azure/azure-sdk-for-go [Logs]

• Package generation in progress.

JavaScript: Azure/azure-sdk-for-js [Logs]

• Package generation in progress.

[AutorestCI]

Automation for azure-sdk-for-python

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

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-go

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-go#5269

[AutorestCI]

Automation for azure-sdk-for-java

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

[sanjaiganesh]

"ExecuteSSISPackageActivity": {

This is heavily modifying the schema of this resource and will cause issues with clients that would be mix of new and old SDKs.
pls introduce them under new api version.

---

Refers to: specification/datafactory/resource-manager/Microsoft.DataFactory/preview/2017-09-01-preview/entityTypes/Pipeline.json:1999 in 29f3be5. [](commit_id = 29f3be5, deletion_comment = False)

[sanjaiganesh]

Ensure to add/update examples

[sanjaiganesh]

"ExecuteSSISPackageActivity": {

also I just couldn't find CRUD api for this resource in the repo..

---

In reply to: 508885125 [](ancestors = 508885125)

---

Refers to: specification/datafactory/resource-manager/Microsoft.DataFactory/preview/2017-09-01-preview/entityTypes/Pipeline.json:1999 in 29f3be5. [](commit_id = 29f3be5, deletion_comment = False)

[sanjaiganesh]

SSISAccessCredential [](start = 5, length = 20)

This must be excluded in GET calls.. to avoid revealing secrets.

[sanjaiganesh]

so the actual resource requires different schema for GET

---

In reply to: 300815583 [](ancestors = 300815583)

[HaoQian-MS]

We don't have GET calls on the resource.

[HaoQian-MS]

@sanjaiganesh, we don't have CRUD apis (and examples) on individual activities, they are always included in a pipeline. Moreover, shall I remove my change in 2017-09-01-preview version and only keep it in 2018-06-01?

[sanjaiganesh]

@haoqian@microsoft.com Didn't follow. Could you please explain how are these resources created ?.. both are existing api versions . so SDK issues concern apply equally to both.

---

In reply to: 509058430 [](ancestors = 509058430)

[HaoQian-MS]

@sanjaiganesh , activity is not a standalone resource. It's a sub resource of pipeline. When creating the pipeline resource, the activity resources in the pipeline are created. Activity resources can't be created directly. Moreover, we don't introduce any breaking change here. We only add more properties which are optional. The existing payloads always work. We don't need to create a new api-version.