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

Support managing Trigger Delivery Policies #23

Closed
davidebriani opened this issue Mar 2, 2023 · 0 comments · Fixed by #27
Closed

Support managing Trigger Delivery Policies #23

davidebriani opened this issue Mar 2, 2023 · 0 comments · Fixed by #27

Comments

@davidebriani
Copy link
Contributor

The upcoming release of Astarte v1.1 will include the new resource type of Trigger Delivery Policies.
A set of CRUD APIs are available and existing policies can also be referenced by Triggers.
Supporting these operations on the astarte-client-elixir is desirable.

Further references on Trigger Delivery Policies:

  1. The JSON Schema, as per Astarte v1.1.0-alpha.0, for how Trigger Policies can be defined: Delivery policy and TriggerEngine revision proposal astarte#554 (comment)
  2. The Swagger file that defines the REST APIs available to manage Trigger Policies: https://github.com/astarte-platform/astarte/blob/master/apps/astarte_realm_management_api/priv/static/astarte_realm_management_api.yaml
  3. Documentation about the concepts of Triggers / Trigger Policies: https://docs.astarte-platform.org/snapshot/060-triggers.html#trigger-delivery-policies
  4. Documentation about using Triggers / Trigger Policies: https://docs.astarte-platform.org/snapshot/060-using_triggers.html#trigger-delivery-policies
@szakhlypa szakhlypa linked a pull request May 10, 2024 that will close this issue
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 a pull request may close this issue.

1 participant