Stack update audit events are currently missing an important piece of context for audits in that they only include the state of the stack after the update. With the current info we can see that a user updated a stack, but not the specific change to the stack that the user made. My team would like to see the specific change made to the stack in the audit log event, for instance on setting a new branch for the code source, the before and after branch name. More broadly this seems applicable to any resource that can be changed in an update action.
Please authenticate to join the conversation.
π In Review
π‘ Feature Requests
Access Control
About 13 hours ago
Get notified by email when there are changes.
π In Review
π‘ Feature Requests
Access Control
About 13 hours ago
Get notified by email when there are changes.