notifications: add ability to create with ttl and custom labels #48631
Comments
rcanderson23
added
the
feature-request
|
Note that for Cloud, we'd like to create notifications with no TTL that we can add/remove using our own automation. |
Can you get by with just setting a larger TTL than you'll expect you'll ever need? (180d for example) |
We plan to manage notifications declaratively, so this could result in a mismatch between our configuration system (Kubernetes resource spec) and what the user sees after 180 days. That said, if very large values are supported (e.g., 10 years), probably not an issue. |
- Add the ability create notifications with a custom TTL (previously we relied on the server-provided default of 30 days) - Add the ability to create notifications with custom labels - Add (non-system) labels to the `tctl notifications ls` output - Add the ability to filter by label when listing notifications Closes #48631
|
#48829 should do the trick if you're okay setting a very large TTL. LMK. |
|
Thanks, looks great! A few hundred years should do it 🙂 |
- Add the ability create notifications with a custom TTL (previously we relied on the server-provided default of 30 days) - Add the ability to create notifications with custom labels - Add (non-system) labels to the `tctl notifications ls` output - Add the ability to filter by label when listing notifications Closes #48631
- Add the ability create notifications with a custom TTL (previously we relied on the server-provided default of 30 days) - Add the ability to create notifications with custom labels - Add (non-system) labels to the `tctl notifications ls` output - Add the ability to filter by label when listing notifications Closes #48631
- Add the ability create notifications with a custom TTL (previously we relied on the server-provided default of 30 days) - Add the ability to create notifications with custom labels - Add (non-system) labels to the `tctl notifications ls` output - Add the ability to filter by label when listing notifications Closes #48631
- Add the ability create notifications with a custom TTL (previously we relied on the server-provided default of 30 days) - Add the ability to create notifications with custom labels - Add (non-system) labels to the `tctl notifications ls` output - Add the ability to filter by label when listing notifications Closes #48631
- Add the ability create notifications with a custom TTL (previously we relied on the server-provided default of 30 days) - Add the ability to create notifications with custom labels - Add (non-system) labels to the `tctl notifications ls` output - Add the ability to filter by label when listing notifications Closes #48631
- Add the ability create notifications with a custom TTL (previously we relied on the server-provided default of 30 days) - Add the ability to create notifications with custom labels - Add (non-system) labels to the `tctl notifications ls` output - Add the ability to filter by label when listing notifications Closes #48631
What would you like Teleport to do?
tctl notifications create --title="Title" --content="Content" --ttl=1dtctl notifications create --title="Title" --content="Content" --label=owner=bot --label=another=labeltctl notifications ls --label=owner=botWhat problem does this solve?
If a workaround exists, please include it.
The text was updated successfully, but these errors were encountered: