Prisma1: [Metrics] No Prisma Cloud secret is set. Metrics collection is disabled.

[nampdn]

Describe the bug
Messy log display every 30s seconds.
[Metrics] No Prisma Cloud secret is set. Metrics collection is disabled.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
Show up a way to setup prisma secret cloud.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: [e.g. Windows 10, OS X High Sierra, Ubuntu 16.04]
• prisma CLI: [e.g. prisma/1.9.0 (darwin-x64) node-v10.4.0]
• Prisma Server: [e.g. 1.9.0]
• graphql-cli, prisma-binding, graphql-yoga, etc. if applicable

Additional context
Prisma is an awesome product. But this messy log make developing experience very bad.

[morajabi]

What can we do for now? Any way to set a cloud secret or perhaps bypass it?

[jonsharratt]

Would be good to show this message once on startup rather than it happening every 30 seconds or not show it at all. Starts to fill up logs 🙈

[divyenduz]

Hey! we are aware of this and we will work on a resolution soon. I will get back with more accurate estimates soon.

[rimiti]

This log should be removed, it's not really useful... 😕

[morajabi]

@divyenduz Please remove it in the next patch if it's not going to be ready soon :)

[do4gr]

Our suggested solution is to only log state changes. This means that we will write a log message only once, if the Cloud Secret is not set.

Does this alleviate your concerns?

[morajabi]

It does, please do it 🙏 thanks!

[hardy613]

@do4gr Thanks for the update!

[mavilein]

Thanks for reporting this! 🙏 This is fixed in 1.15.3 which will be availabel in a few minutes.

[nugoo1]

Im getting this same error when trying to run prisma deploy!

is there a solution to this?