Deployment-Producer and Consumer
Application Type
Traditional Web, Mobile, Reactive, Service

Consider a producer application undergoes a change, so I have to re-deploy the latest version of it in the target environment. In this scenario, should I also re-deploy the consumer application to the target environment? How does Lifetime handle it?

mvp_badge
MVP
Solution

Hi,

From OutSystems document action:

Update Dependencies in Target Environment

When deploying an application to a target environment, LifeTime detects the applications consuming functionality from the application being deployed and that would have outdated dependencies with the current deployment. In the deployment plan, LifeTime suggests to republish these consumer applications in the target environment to ensure all its dependencies are up to date.

No changes are made to these consumer applications: they will only be republished in the target environment to start using the new version of the application being deployed. You will only be able to republish the applications to which you have permissions.

Choosing not to republish the consumer applications in the target environment may lead to runtime errors.

--

LifeTime gives you an option per consumer application to not republish. We use it without any problems to avoid a large amount of republishing if we know it is not needed. A QA 9r pre production environment is the place to try and test that there are no runtime errors.

Solution

Hi  Krishnnambal ,

1) If you made some changes in the Producer Module ,
During deployment process you will get the option to tick publish consumer modules .
If you are not selecting consumer modules then producer module changes will not affect consumer modules .
(This is the case when you are doing changes in the Producer which will not cause Broken Dependencies ).


2)If you are doing some changes like Input Parameter(Mandatory), or Deleting web blocks etc.

In this case , Dev. environment itself you have to do changes and  deploy to another environment.

You will not get a tick box of consumers in this scenario while deployment .

As per my experience , better try to do deployment with different scenarios .
Your all doubts will get clear.

Regards ,
Vivek P

Hello Krishnnambal,

As per my knowledge you can only re-deploy the latest version of the producer module, It will work but  It depends if you add any other component or references that are not present in the group then you need to add that too in the Solution. 

 Because LifeTime detects all application dependencies that are not up-to-date in the destination environment and adds those dependencies to the deployment plan, highlighting them in red. 

Please go through this Deploy an Application with dependencies   and  Single Module Deployment it will also help you to understand it better.

Regards,

Pavan R

mvp_badge
MVP
Solution

Hi,

From OutSystems document action:

Update Dependencies in Target Environment

When deploying an application to a target environment, LifeTime detects the applications consuming functionality from the application being deployed and that would have outdated dependencies with the current deployment. In the deployment plan, LifeTime suggests to republish these consumer applications in the target environment to ensure all its dependencies are up to date.

No changes are made to these consumer applications: they will only be republished in the target environment to start using the new version of the application being deployed. You will only be able to republish the applications to which you have permissions.

Choosing not to republish the consumer applications in the target environment may lead to runtime errors.

--

LifeTime gives you an option per consumer application to not republish. We use it without any problems to avoid a large amount of republishing if we know it is not needed. A QA 9r pre production environment is the place to try and test that there are no runtime errors.

Solution

Hi  Krishnnambal ,

1) If you made some changes in the Producer Module ,
During deployment process you will get the option to tick publish consumer modules .
If you are not selecting consumer modules then producer module changes will not affect consumer modules .
(This is the case when you are doing changes in the Producer which will not cause Broken Dependencies ).


2)If you are doing some changes like Input Parameter(Mandatory), or Deleting web blocks etc.

In this case , Dev. environment itself you have to do changes and  deploy to another environment.

You will not get a tick box of consumers in this scenario while deployment .

As per my experience , better try to do deployment with different scenarios .
Your all doubts will get clear.

Regards ,
Vivek P

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.