Sometimes when schema registration fails, its hard to trace why.
You need to either check schema-registry logs, or you need to debug endpoint response output on client side
This adds Logs UI which shows all logs that schema-registry does via regular logger.error() functions, just uses redis as a temporary storage
Changes
add logs tab (reads from redis)
add info component
add winston-redis-stream for temporary storage for logs
⚠ Bad use of docker image
**Message:** Only pipedrive base images must be used
**File:** [Dockerfile.CI](https://github.com/pipedrive/graphql-schema-registry/tree/3ff20bb707756c26d607b3b2693c742af54c1ed7/Dockerfile.CI)
**Actual image:**
```dockerfile
node:16-alpine
```
🔍 [How to fix it](https://neodora.pipedrive.tools/rules/pipedriveBaseImage)
Problem
Sometimes when schema registration fails, its hard to trace why. You need to either check schema-registry logs, or you need to debug endpoint response output on client side This adds Logs UI which shows all logs that schema-registry does via regular
logger.error()
functions, just uses redis as a temporary storageChanges