Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix!: always return iso-8601 formatted date time #453

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

jooola
Copy link
Collaborator

@jooola jooola commented Feb 2, 2024

SUMMARY

Fixes #91

Always return datetime as iso-8601 formatted strings.

ISSUE TYPE
  • Bugfix Pull Request

@jooola jooola force-pushed the consistent-datetime-format branch from 062a4d4 to eb5beb6 Compare February 2, 2024 16:04
@jooola jooola merged commit 55d2616 into ansible-collections:main Feb 5, 2024
30 checks passed
@jooola jooola deleted the consistent-datetime-format branch February 5, 2024 11:18
jooola pushed a commit that referenced this pull request Feb 5, 2024
🤖 I have created a release *beep* *boop*
---


##
[3.0.0](2.5.0...3.0.0)
(2024-02-05)


### ⚠ BREAKING CHANGES

* drop support for ansible-core 2.13
([#450](#450))
* always return iso-8601 formatted date time
([#453](#453))
* remove inventory `api_token_env` option
([#454](#454))

### Features

* drop support for ansible-core 2.13
([#450](#450))
([96f8009](96f8009)),
closes
[#400](#400)
* **inventory:** allow templating instances hostname
([#455](#455))
([be404ef](be404ef))
* remove inventory `api_token_env` option
([#454](#454))
([d0c82ae](d0c82ae))


### Bug Fixes

* allow renaming networks
([#449](#449))
([742cfe6](742cfe6))
* always return iso-8601 formatted date time
([#453](#453))
([55d2616](55d2616))
* load balancer invalid cookie lifetime value returned
([#452](#452))
([86b7662](86b7662))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Would it make sense to document the precise format of not_valid_after in hcloud_certificate_info?
2 participants