-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(specs): add notification settings to tasks [skip-bc] (generated)
algolia/api-clients-automation#4297 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Pierre Millot <[email protected]>
- Loading branch information
1 parent
4d9b926
commit 68b98ea
Showing
8 changed files
with
98 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
29 changes: 29 additions & 0 deletions
29
src/main/scala/algoliasearch/ingestion/EmailNotifications.scala
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
/** Ingestion API The Ingestion API lets you connect third-party services and platforms with Algolia and schedule tasks | ||
* to ingest your data. The Ingestion API powers the no-code [data | ||
* connectors](https://dashboard.algolia.com/connectors). ## Base URLs The base URLs for requests to the Ingestion API | ||
* are: - `https://data.us.algolia.com` - `https://data.eu.algolia.com` Use the URL that matches your [analytics | ||
* region](https://dashboard.algolia.com/account/infrastructure/analytics). **All requests must use HTTPS.** ## | ||
* Authentication To authenticate your API requests, add these headers: - `x-algolia-application-id`. Your Algolia | ||
* application ID. - `x-algolia-api-key`. An API key with the necessary permissions to make the request. The required | ||
* access control list (ACL) to make a request is listed in each endpoint's reference. You can find your application ID | ||
* and API key in the [Algolia dashboard](https://dashboard.algolia.com/account). ## Request format Request bodies must | ||
* be JSON objects. ## Response status and errors Response bodies are JSON objects. Successful responses return a `2xx` | ||
* status. Client errors return a `4xx` status. Server errors are indicated by a `5xx` status. Error responses have a | ||
* `message` property with more information. ## Version The current version of the Ingestion API is version 1, as | ||
* indicated by the `/1/` in each endpoint's URL. | ||
* | ||
* The version of the OpenAPI document: 1.0.0 | ||
* | ||
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). | ||
* https://openapi-generator.tech Do not edit the class manually. | ||
*/ | ||
package algoliasearch.ingestion | ||
|
||
/** EmailNotifications | ||
* | ||
* @param enabled | ||
* Whether to send email notifications, note that this doesn't prevent the task from being blocked. | ||
*/ | ||
case class EmailNotifications( | ||
enabled: Option[Boolean] = scala.None | ||
) |
26 changes: 26 additions & 0 deletions
26
src/main/scala/algoliasearch/ingestion/Notifications.scala
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
/** Ingestion API The Ingestion API lets you connect third-party services and platforms with Algolia and schedule tasks | ||
* to ingest your data. The Ingestion API powers the no-code [data | ||
* connectors](https://dashboard.algolia.com/connectors). ## Base URLs The base URLs for requests to the Ingestion API | ||
* are: - `https://data.us.algolia.com` - `https://data.eu.algolia.com` Use the URL that matches your [analytics | ||
* region](https://dashboard.algolia.com/account/infrastructure/analytics). **All requests must use HTTPS.** ## | ||
* Authentication To authenticate your API requests, add these headers: - `x-algolia-application-id`. Your Algolia | ||
* application ID. - `x-algolia-api-key`. An API key with the necessary permissions to make the request. The required | ||
* access control list (ACL) to make a request is listed in each endpoint's reference. You can find your application ID | ||
* and API key in the [Algolia dashboard](https://dashboard.algolia.com/account). ## Request format Request bodies must | ||
* be JSON objects. ## Response status and errors Response bodies are JSON objects. Successful responses return a `2xx` | ||
* status. Client errors return a `4xx` status. Server errors are indicated by a `5xx` status. Error responses have a | ||
* `message` property with more information. ## Version The current version of the Ingestion API is version 1, as | ||
* indicated by the `/1/` in each endpoint's URL. | ||
* | ||
* The version of the OpenAPI document: 1.0.0 | ||
* | ||
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). | ||
* https://openapi-generator.tech Do not edit the class manually. | ||
*/ | ||
package algoliasearch.ingestion | ||
|
||
/** Notifications settings for a task. | ||
*/ | ||
case class Notifications( | ||
email: EmailNotifications | ||
) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
/** Ingestion API The Ingestion API lets you connect third-party services and platforms with Algolia and schedule tasks | ||
* to ingest your data. The Ingestion API powers the no-code [data | ||
* connectors](https://dashboard.algolia.com/connectors). ## Base URLs The base URLs for requests to the Ingestion API | ||
* are: - `https://data.us.algolia.com` - `https://data.eu.algolia.com` Use the URL that matches your [analytics | ||
* region](https://dashboard.algolia.com/account/infrastructure/analytics). **All requests must use HTTPS.** ## | ||
* Authentication To authenticate your API requests, add these headers: - `x-algolia-application-id`. Your Algolia | ||
* application ID. - `x-algolia-api-key`. An API key with the necessary permissions to make the request. The required | ||
* access control list (ACL) to make a request is listed in each endpoint's reference. You can find your application ID | ||
* and API key in the [Algolia dashboard](https://dashboard.algolia.com/account). ## Request format Request bodies must | ||
* be JSON objects. ## Response status and errors Response bodies are JSON objects. Successful responses return a `2xx` | ||
* status. Client errors return a `4xx` status. Server errors are indicated by a `5xx` status. Error responses have a | ||
* `message` property with more information. ## Version The current version of the Ingestion API is version 1, as | ||
* indicated by the `/1/` in each endpoint's URL. | ||
* | ||
* The version of the OpenAPI document: 1.0.0 | ||
* | ||
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). | ||
* https://openapi-generator.tech Do not edit the class manually. | ||
*/ | ||
package algoliasearch.ingestion | ||
|
||
/** Set of rules for a task. | ||
* | ||
* @param criticalThreshold | ||
* The number of critical failures in a row before blocking the task and sending a notification. | ||
*/ | ||
case class Policies( | ||
criticalThreshold: Option[Int] = scala.None | ||
) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters