Open psavidis opened 1 year ago
Hi @psavidis, Thanks for raising this problem.
Since this behavior did not change with your code changes, i.e., a TTL with a not-allowed value led to the same error behavior in the past, I would keep everything as it is and wait for user feedback. We could potentially address this after collecting more evidence that this is really a problem.
Acceptance Criteria (Required on creation)
As a User of the Java & REST API, i want the parsing of the different deployable resources to be consistent in the case of missing HistoryTimeToLive.
Hints
Links
Breakdown
Dev2QA handover