API v1.1 - Make TTL optional
TTL shouldn't be a required field in our API. Reason is that there are scenarios where messages that live forever may be needed. Also a little more convenient when the client doesn't have to always specify TTL.
From the spec:
"When posting messages or creating a claim, the ttl field may be omitted. If it is not given by the client, Marconi will default to the max TTL setting configured by the cloud operator."
See also: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Kurt Griffiths
- Priority:
- Low
- Drafter:
- Flavio Percoco
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- Kurt Griffiths
Related branches
Related bugs
Sprints
Whiteboard
I think "ttl" the field can be optional, but time-to-live the concept should be kept.
Even you want permentent messages, you can specify a specially value to "ttl" (null, maybe?)
We could allow setting ttl to 0, and assume that if it is set - in the config you would have to have a setting to disable "max ttl" which would enable "forever" messages.
Moving to Juno (kgriffs)
Duplicate - api-v1.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
