---

User Story

As a news wire reader service, I need instructions on how to retrieve updates.

---

Description

In our MVP delivery of Exemó::Gobbler, we're going to limit the scope of the call to execution endpoint (think CLI parameters/arguments) to a taxonomic category.

For everything else, we'll establish a Gobbler config file that will provide default values for:

• a target URI for a news feed
• the frequency of polling (in milliseconds up to 5 minutes)
• a taxonomic category
• the number of retries/attempts (integer up to 5)
• the interval between retries (in milliseconds up to 5 minutes)

While we will eventually add these values to the call to execution endpoint, we first want defaults that will instruct the service how to act when individual arguments are missing.

---

UATs

1. GIVEN a valid Gobbler config file
   • and GIVEN it contains a valid default URI
   • and GIVEN it contains a valid default taxonomic category
   • and GIVEN we have a valid session token from the new wire service
   • and GIVEN we manually create a valid query in Postman
   • WHEN we issue a request to the new service via our valid query
   • THEN the news wire service successfully fulfills our request
2. GIVEN a valid Gobbler config file
   • WHEN we check range of the the frequency setting
   • THEN it should contain a value of 1 to 300000 milliseconds
3. GIVEN a valid Gobbler config file
   • WHEN we check range of the the retries interval setting
   • THEN it should contain a value of 1 to 300000 milliseconds
4. GIVEN a valid Gobbler config file
   • WHEN we check range of the the retries interval setting
   • THEN it should contain a value of 1 to 5

---

User Story

As an ingestion service, I periodically want to be updated with new content.

---

Description

As part of the Gobbler service, the scope of this ticket is to periodically go out to a targeted news wire service and poll it for data.

If the response is valid, then the service will provide a flag or other mechanism to indicate a successful read event.

If the response is invalid, then the service will provide a flag or other mechanism to indicate the polling service failed.

We'll incrementally add more functionality to this feature in subsequent stories. This includes retries, hand-off to queues, and logging enumerated in other tickets within the parent epic.

This story has an additional prerequisite the completion the Gobbler configuration file task to include:

• a target URI for a news feed
• the frequency of polling
• a fixed, default taxonomic category

Assumptions include:

• the taxonomic category of the news feed is fixed at this time
• the news wire is a RESTful service
• the news wire is returning results in a JSON format
• the news wire service is up and available
• the news wire service is delivering valid data
• the news wire adheres to the HTTP/HTTPS protocol in its treatment of header data

---

UATs

1. GIVEN a valid URI for a news wire
   • and GIVEN a valid taxonomic category
   • and GIVEN the news wire service is up and running
   • WHEN the news wire service is polled
   • THEN a response is received from the news wire service
2. GIVEN the successful execution of UAT 1 above
   • and GIVEN the news wire response includes a valid HTTP Header
   • and GIVEN the news wire response includes valid JSON data in the Body
   • WHEN when the response is received
   • THEN the ingestion service identifies the response as valid
3. GIVEN a valid URI for a news wire
   • and GIVEN a valid taxonomic category
   • and GIVEN the news wire service is up and running
   • WHEN the news wire service is polled
   • THEN a response is received from the news wire service