Support for managing configurations

[rajdip-b]

Description

Currently, keyshade only supports storing secrets. While this is nice, users might also want to store non-sensitive data such as application configurations. For example, SERVER_PORT.

Solution

This brings us to our second entity besides secret: Configuration. A configuration will necessarily be having similar features as that of secret, except these changes:

• No Encrytion/decryption logic
• No rotation feature

Scope of changes

For now, these changes are only local to the API. They include:

• Create configuration POST /api/configuration/{projectId}
• Update configuration PUT /api/configuration/{configurationId}
• Delete configuration DELETE /api/configuration/{configurationId}
• Get config by id GET /api/configuration/{configurationId}
• Get all configs of project (paginated) GET /api/configuration/{projectId}
• Get all configs (paginated) (admin only) GET /api/configuration/

Necessary tests for the same would be a huge plus!

[lakshay-saini-au8]

/attempt

[github-actions]

Assigned the issue to you!

[rajdip-b]

@lakshay-saini-au8 hey! you can get started with this now.

[rajdip-b]

🎉 This issue has been resolved in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀