Open chalabaj opened 8 months ago
Encountering the same issue on version 1.18.2, this issue is not present on 1.18.1
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @zhangyd2015, @Frey-Wang, @Jingshu923.
Even we are facing the same issue, when can we expect a resolution ?
HI Team
we are facing the same issue with 1.18.2 for our web activity in the pipelines , is there a time line on the resolution for this ?
We are facing this challnge too and it has resulted in failures of the PrePostDeploymentScript used in our CI.CD pipelines. This is a breaking change for us so any priority effort that could be placed on either rectifying the issue or rolling back the update would be appreciated.
Is there any update on this issue?
Thanks for feedback. I am from ADF team, we have acknowledged and identified these issues and working on a hotfix release. We aim to release the new version with hotfix by the end of this week 3.15. I will share the status with you when the new version powershell module released. Before the new release, you could use 1.18.1 version to work around.
Applied a hotfix and released a new version of Az.DataFactory PowerShell Gallery | Az.DataFactory 1.18.3. Please try 1.18.3 version.
I know its unrelated but the GitHub action repo data-factory-deploy is archived and cannot implement this fix. Is there anyone we can reach out to fix our workflows?
Hi , i am also facing the issue with github action repo for data-factory-deploy method , this method is first running the command
which seems to be still installing the data factory 18.2 version and causing the failures in pre port deployment script . ps 1 where the triggers get turned on and off ,
Install-Module -Name Az -Scope CurrentUser -Repository PSGallery -Force
this is still bringing in the 1.18.2 version of data factory , can we get this fixed ?
Hi , i am also facing the issue with github action repo for data-factory-deploy method , this method is first running the command
- name: Install Az PowerShell module run: if('${{ inputs.skipAzModuleInstallation }}' -ne 'true') { Install-Module -Name Az -Scope CurrentUser -Repository PSGallery -Force } shell: pwsh
which seems to be still installing the data factory 18.2 version and causing the failures in pre port deployment script . ps 1 where the triggers get turned on and off ,
Install-Module -Name Az -Scope CurrentUser -Repository PSGallery -Force
this is still bringing in the 1.18.2 version of data factory , can we get this fixed ?
A workaround I found was to add a step in your own workflow to do a manual install of specifically Az.DataFactory before you run the depoy action. See below example:
deployment:
needs: build
environment: ${{ inputs.environment }}
runs-on: ubuntu-latest
steps:
# we 1st download the previously uploaded artifact so we can leverage it later in the release job
- name: Download a Build Artifact
uses: actions/download-artifact@v3.0.2
with:
name: ExportedArmTemplate # (5) Artifact name
- name: Login via Az module
uses: azure/login@v1
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ vars.ENTRA_TENANT_ID }}
subscription-id: ${{ vars.AZURE_SUBSCRIPTION_ID }}
enable-AzPSSession: true
- name: Install Az PowerShell module
run: Install-Module -Name Az.DataFactory -Scope CurrentUser -Repository PSGallery -Force
shell: pwsh
- name: data-factory-deploy
uses: Azure/data-factory-deploy-action@v1.2.0
Description
Since version 1.18.2 of Az.DataFactory module, we got error with deserialization of pipeline jsons when running
**Get-AzDataFactoryV2Pipeline** -ResourceGroupName "XXXX" -DataFactoryName "YYYY" -name "ZZZZ
I get error for 14 out of 700 pipeline deployed. Problematic pipelines jsons: When downgrading to version 1.18.0 everything works fine:Issue script & Debug output
Environment data
Module versions
Error output