Credential Rotation and Environment Security Enhancements

The user has outlined two critical use cases related to credential and environment security management that warrant review:

1. Credential Rotation

Context: The user requires periodic credential (API key) rotation in accordance with security best practices.

Current Limitation: At present, rotating credentials results in service downtime until all systems are updated with the new credentials.

Impact: This downtime is operationally unacceptable, as it may disrupt business-critical services.

Requested Enhancement: Introduction of a mechanism that allows for a smooth transition between old and new credentials—enabling both to remain valid temporarily during the rotation process to prevent downtime.

2. Environmental Security:

Context: The user maintains multiple environments, including development, staging, and production.

Current Limitation: A single shared credential is being used across all environments.

Impact: This presents a potential security vulnerability, as exposure of credentials in a lower environment could compromise production systems.

Requested Enhancement: Implementation of environment-specific credentials to ensure proper isolation and adherence to standard security protocols.

Kindly confirm whether these improvements are already part of our development roadmap or if a new feature request should be initiated for further evaluation.