Open gvdmaaden opened 1 year ago
Thank you for your feedback. This has been routed to the support team for assistance.
@gvdmaaden We are looking into it and get back to you for any additional information.
@gvdmaaden I am able to reproduce this and checking internally with the team. I will update you as soon as I have any updates. Thanks.
@SaurabhSharma-MSFT - Any update on this?
Hello @soma-ms, Im currently using the PrePostDeploymentScript.Ver2.ps1 and I
m having the same issue regarding stoping all the triggers (even if they are not changed). I downloaded the script last month and Im not sure if I have to do some adjustments. I
m asking because I saw a few posts from last year (2023) about this issue and with some adjustments to do. Is this script already adjusted?
Hi @mariobgallardo, I noticed that the dev team has included my workaround in their PrePostDeploymentScript.Ver2.ps1. See line 285 in the script here. So this issue should be solved at least with this workaround. Are you sure that your problem is related to this datetime issue?
Aside from the datetime issue you also might encounter an issue regarding overriding the parameters in your CI CD pipeline, please see this issue. I suggested a fix for that in this PR so that PrePostDeploymentScript.Ver2.ps1 would support overriding parameters, but it has not been merged since my change was considered too big. If your scenario is related to this override issue then you might need to implement the changes from the PR in our own version of the powershell script. If needed I can advice.
Description
Hi, it seems Get-AzDataFactoryV2Trigger method is not returning the correct datetime notation. I have a schedule trigger in ADF with a local time:
This is correctly reflected in my ARM template:
But when I retrieve the trigger details with Get-AzDataFactoryV2Trigger it incorrectly shows an "Z" at the and of the datetime, suggesting that it is a UTC time:
I noticed this issue when I was testing the PrePostDeploymentScript v2 (=script that should only stop and start the triggers in case they are changed). There already seems to be an issue raised for that but I believe this Get-AzDataFactoryV2Trigger issue is the underlying problem here.
I also included some part of the debug output. There you can see the HTTP response of the GET action that retrieves the data factory details. In that HTTP response it shows the correct local datetime notation.
Issue script & Debug output
Environment data
Module versions
Error output