TODO¶

• For inno-notification

• Added the first version of staging

• Added the transfer of production out of inno-transflow

• Updated permission on the docs version

• Transfer the cloud task queue into infra and naming with queue-notification-service

~> Migrate fully the resource into inno-notification

• Deployed application based on Otter with Manifest

Goal: support to CI to Slack instead of mannual deployed with various related URL handlers

• Build update manifest of Slack when changes of component

• Set up related push for changes of Slack manifest

• Add the staging deployment with different token on application

• Add structlog for service

• Build flow of notification | handler with flow

• Idea example:

a) The message has been built

b) Nothing happend

c) In case of exist error and required maintainer -> Use dispatch for maintainer

If has maintainer call, required updated the parent message with RED color attachment

• Maintainer for each group of element

• Added convention with:

• Authentication: https://github.com/uhavin/slackers

• Following structure: https://github.com/slackapi/bolt-python

• Authentication for requests using HMAC with Slack Framework. Docs: Authentication - verifying requests from slack

• Authentication by invoke user

• Fix pipeline remove no-cpu-throtting

• Handle error

Check no pgromaging

Programming Exec

• Missing create dataset

• Handle

DATABASE | DEVELOPER | Hint

Error convention

https://stackoverflow.com/questions/6598053/python-global-exception-handling

Use webhook to send report

Report internal with 1hour each

https://www.data-sentinel.com/data-source-connectors