You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug where the deployment history of external secrets is not displayed in the UI. This issue makes it difficult to track changes in secrets and see if any modifications have been made and deployed. Currently, the deployment history is only visible on the Build and Deploy page at the time of deployment. Once a new deployment occurs, there is no way to check the differences between the current and previous deployments. This lack of visibility hampers our ability to audit and manage secret changes effectively.
BUILD AND DEPLOY PAGE
DEPLOYMENT HISTORY
👟 Reproduction steps
Please try to use a external secret in application
👍 Expected behavior
NA
👎 Actual Behavior
NA
☸ Kubernetes version
NA
Cloud provider
aws
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
📜 Description
There is a bug where the deployment history of external secrets is not displayed in the UI. This issue makes it difficult to track changes in secrets and see if any modifications have been made and deployed. Currently, the deployment history is only visible on the Build and Deploy page at the time of deployment. Once a new deployment occurs, there is no way to check the differences between the current and previous deployments. This lack of visibility hampers our ability to audit and manage secret changes effectively.
BUILD AND DEPLOY PAGE
DEPLOYMENT HISTORY
👟 Reproduction steps
Please try to use a external secret in application
👍 Expected behavior
NA
👎 Actual Behavior
NA
☸ Kubernetes version
NA
Cloud provider
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
AB#9996
The text was updated successfully, but these errors were encountered: