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
Due to issues related to security audit in production environment, it is necessary to add options so that when Migration is generated, the query list to be applied can be output as a separate log.
In addition, when Migration is actually approved, the information from the approver must be brought in to record the information of the person who approved it. As the Table is managed by GitOps, it'll be able to utilize the author information of a Git Commit.
In terms of security, it is very important to leave a history of query execution in the production environment, so please actively consider and reflect this function.
The text was updated successfully, but these errors were encountered:
Due to issues related to security audit in production environment, it is necessary to add options so that when
Migration
is generated, the query list to be applied can be output as a separate log.In addition, when
Migration
is actually approved, the information from the approver must be brought in to record the information of the person who approved it. As theTable
is managed by GitOps, it'll be able to utilize the author information of a Git Commit.In terms of security, it is very important to leave a history of query execution in the production environment, so please actively consider and reflect this function.
The text was updated successfully, but these errors were encountered: