tsaaii opened a new issue #21949:
URL: https://github.com/apache/airflow/issues/21949


   ### Apache Airflow version
   
   2.2.4 (latest released)
   
   ### What happened
   
   I am trying to implement the functionality specified in this [PR 
](https://github.com/apache/airflow/pull/17885) here 
   
   From the code, to run a pipeline on ADF, you do this
   
   ```
       run_pipeline1 = AzureDataFactoryRunPipelineOperator(
           task_id="run_pipeline1",
           pipeline_name="pipeline1",
           parameters={"myParam": "value"},
       )
   ```
   
   This doesn't work if your pipeline is in a folder, something like
   ```
       run_pipeline1 = AzureDataFactoryRunPipelineOperator(
           task_id="run_pipeline1",
           pipeline_name="folder_name/pipeline1",
           parameters={"myParam": "value"},
       )
   ```
   
   DAG fails with following error
   
   ```
   msrest.exceptions.ValidationError: Parameter 'pipeline_name' must conform to 
the following pattern: '^[A-Za-z0-9_][^<>*#.%&:\\\\+?/]*$'.
   ```
   
   
   ### What you expected to happen
   
   There should be a way to specify directory and sub directory names when 
using AzureDataFactoryRunPipelineOperator.
   
   ### How to reproduce
   
   _No response_
   
   ### Operating System
   
   windows
   
   ### Versions of Apache Airflow Providers
   
   3.6.0
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   Docker+Helm chart with custom values.yaml
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to