Skip to main content
Announcements
Applications are open for the 2024 Qlik Luminary Program. Apply by December 15 here.
cancel
Showing results for 
Search instead for 
Did you mean: 
akshaay_akkii
Contributor
Contributor

Database connections are not updating post deployment

We are deploying the project to higher environment with changes in landing zone setting but the changes are not reflecting post deployment.

Example in LANDING zone "ORG_LANDING_ZONE" I have database "Organization". I have modified it as "Org". after deploying the changes in existing project  on higher environment. It's still showing database as Organization only.

1 Solution

Accepted Solutions
sureshkumar
Support
Support

Hello @akshaay_akkii 

As i checked internally, this is expected behaviour.

"Note that as database settings are usually environment specific, the database settings in the target project will not be overwritten by those of the source project.
When deploying, Compose does not override existing connection parameters. This enables you to easily migrate projects from test to production"

https://help.qlik.com/en-US/compose/May2022/Content/ComposeDWDL/Main/DW/General/Project_Deployment.h...

 

Regards,
Suresh

View solution in original post

4 Replies
sureshkumar
Support
Support

Hello @akshaay_akkii 

What is the Qlik Compose version in lower environment and higher environment?

And kindly let us know exact steps followed.

 

Regards,

Suresh

akshaay_akkii
Contributor
Contributor
Author

Hi Suresh,

Compose version in both the environment is same 2022.5.0.743.

Steps:

In lower environment I have modified the database name in existing source connection and when I'm deploying it to higher environment it's still showing old database name only.

sureshkumar
Support
Support

Hello @akshaay_akkii 

As i checked internally, this is expected behaviour.

"Note that as database settings are usually environment specific, the database settings in the target project will not be overwritten by those of the source project.
When deploying, Compose does not override existing connection parameters. This enables you to easily migrate projects from test to production"

https://help.qlik.com/en-US/compose/May2022/Content/ComposeDWDL/Main/DW/General/Project_Deployment.h...

 

Regards,
Suresh

TimGarrod
Employee
Employee

As Suresh said, this is by design, so that everytime you deploy you do not have to be concerned about adjusting db names and schemas.   You set it once and that is it. 

 

Having said that, if you do have a need to adjust these configurations as part of deployment, you can use environment variables, and apply a json file that has the overrides you wish to deploy.  This is done via the ComposeCLI only today, as this is meant for automated deployment scenarios. 

 

For more information please see the help docs - https://help.qlik.com/en-US/compose/May2022/Content/ComposeDWDL/Main/DW/Projects/Variables_templates...