Go Gin HTTP endpoint for u-service

[kneerunjun]

• [x] Setup basic go gin ping endpoint
  • [x] Setup logging
  • [x] Error handling
  • [x] Handler for trigger POST endpoint
  • [x] Basic test with Postman
  • [x] Unit testing endpoint for url params, cron like repeated calls
  • [x] Makes HTTP fwd call to telegram.org/api to get the updates

[kneerunjun]

Telegram request needs to handle timeout scenarios - Telegram server is typically found to be fast, but incase it takes longer to respond the api call here on the u-service should timeout

[kneerunjun]

Typical endpoint looks like this /bots/:botid/scrape/:offset. botid is for getting the appropriate bot token (loaded into the environment from secrets.) while the offset is the update offset

• Validation of url params
• Gets the token from bot id - bot id is nothing but the private chatid of the bot
• Offset of the update from url params
  • Makes POST request to api.telegram.org
  • Reads the response onto UpdareResponse object
  • Sends back
  • total messages in the update
  • next update offset
  • Text messages as []string
  • Caller (typically a cron job) will use the offset and bot id again to get more updates after interval