Improve/websock and cr

[abdheshnayak]

• updated token generation logic for the grpc of container registry for internal use
• added record version to websocket logs.

[sourcery-ai]

Hey @abdheshnayak - I've reviewed your changes and found some issues that need to be addressed.

General suggestions:

• Ensure that all new methods and changes adhere to existing security protocols, especially regarding the handling of secrets and tokens.
• Review the logging level changes to ensure they align with the intended severity and information disclosure policies.
• Consider the impact of the new admin credential creation method on existing workflows and ensure it integrates smoothly with the current system architecture.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🔴 Security: 1 blocking issue
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Docstrings: all looks good

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

• X
• Mastodon
• LinkedIn
• Facebook

---

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

[sourcery-ai]

🚨 issue (security): Hard-coded secret detected in the concatenation of d.envs.RegistrySecretKey with credential.AccountName. This approach can potentially expose sensitive information. Consider securely managing secrets, for example, through a secrets manager.