Bump module version to 1.17.1 and update changelog for timezone handling improvements #402#496
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request addresses an important issue with scheduled trigger recurrence times in Azure Data Factory deployments, ensuring that explicit timezone offsets are preserved during configuration updates. It also includes a version bump and new tests to verify the fix.
Bug fix for timezone offsets in trigger recurrence:
Update-ObjectPropertyinObjectProperty.ps1to preserve explicit timezone suffixes (e.g.,+10:00,Z) when settingDateTimeproperties, preventing unintended timezone shifts during deployment.Testing improvements:
Update-PropertiesFromFile.Tests.ps1to verify that timezone offsets in trigger recurrence start and end times remain unchanged after updates (Issue Deployed scheduled trigger has wrong time due to timezone #402).Documentation and versioning:
changelog.mdto document the fix for scheduled trigger timezone handling and incremented the version to1.17.1.azure.datafactory.tools.psd1from1.17.0to1.17.1.Deployed scheduled trigger has wrong time due to timezone #402