GIT Instruction How To
GIT Instruction How To
In order to migrate Sisense assets between environments, please follow the below steps:
Step to add your assets to the GIT repository:
1. Create a project by adding a ...
Published 09-17-2024
Knowledge Base Article
Hi gwolfe
When using Git Integration, database connections are environment-specific and are not automatically promoted between environments. This design is intentional and driven by security best practices—to ensure that sensitive connection details (e.g., hostnames, credentials) are not inadvertently shared or overwritten across development, staging, or production environments.
When you push a commit from your development environment to Git and then pull it into your production environment, the prod environment can have database connection (with the same name) already exists in production and is configured with the appropriate production credentials.
At this time, Sisense does not support dynamic transformation or promotion of connection settings during Git-based migrations. Any required changes to connection details must be made manually in the destination environment, or automated using the Sisense REST API as part of your deployment pipeline.
This approach ensures that connections are managed securely and deliberately, and reduces the risk of accidentally exposing or reusing development credentials in sensitive production environments.
CC DRay
About Sisense Administration
