Hello,
We have a client who want to have airgap deployment to production only and not use lifetime there for security purpose since its a banking client.We are supposed to give them pros and cons of both i.e. deployment with lifetime and without lifetime.I am finding it very difficult to find any pros for deployment without lifetime.Kindly help to share pros and cons of this kind of deployment as per your experiences. TIA
Regards,Anagha
Hi Anagha,
Deploying without Lifetime becomes more complex and error prone because it manages dependencies between the applications. At some point it may potentially lead to deployment issue or any broken dependencies.
Lifetime simplifies the management of dependencies between applications and modules, ensuring smooth deployments without risking dependency errors. Without Lifetime, manual dependency management can be complicated and prone to mistakes, potentially causing deployment issues.
Regards,
Mohamed Zubair Ahmed
Hi,
LifeTime also has an API that you can integrate in any CI/CD tool like Jenkins, AzureDevOps or any other tool that can call REST API to complete their CI/CD pipelines.
Using LifeTime or the LifeTimeAPI will ensure deployment is completely done correct, and validations are automatically performant to deploy all the right versions of dependent modules.
OutSystems LifeTime simplifies and accelerates application lifecycle management (ALM). Runtime configurations, such as batch job scheduling, web-service endpoints, business properties, and versions are all done in one place.
Daniel
To be honest, I don't think there is a single pro for a deployment without LifeTime.
Before LifeTime, you had to upload and publish OML/OSP files directly into the target environment to execute a deployment. Everything could go wrong since no reference validations were made.
Using LifeTime has several advantages as mentioned in previous replies.
What exactly are those "security" issues raised?
Kind regards,
Rui Barradas