Skip to content

fix/GONRG-2103: Pass wrong date-time format

Yan Sushchynski (EPAM) requested to merge fix/GONRG-2103_Entity_passes_validation_with_wrong_date_format into master

Type of change

  • Bug Fix
  • Feature

Does this introduce a change in the core logic?

  • [Yes]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Updates description?

Fix the issue:

  • Any entity was able to pass the validation against date-time format (e.g. "mar 11" was valid, though it didn't follow date-time format).

!!!NOTE: To turn on date-time validation, the package strict-rfc3339 must be installed (https://python-jsonschema.readthedocs.io/en/latest/validate/#jsonschema.FormatError).

Date-time fields must follow RFC3339 standards :

  • 2020-12-16T11:46:20.163Z - ok
  • 2019-10-12T14:20:50.52+07:00 - ok
  • 2020-12-16T11:46:20Z - ok
  • 2019-10-12T14:20:50.52 - not ok

see: https://pypi.org/project/strict-rfc3339/

Edited by Yan Sushchynski (EPAM)

Merge request reports