[Azure Maps] - Onboarding for Timezone SDK

[dubiety]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-maps-timezone

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - cu

[azure-pipelines]

No pipelines are associated with this pull request.

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dubiety]

/azp run python - maps - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hi @dubiety. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[ghost]

Hi @dubiety. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing "/reopen" if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the "no-recent-activity" label; otherwise, this is likely to be closed again with the next cleanup pass.