Today, when there is need to do some configuration in the destination environment of a deployment (site properties, timers, end points, etc), this configuration must be made after the deployment is done.
Would be nice to have a way of preparing those configurations during the planning and see them being applied automatically during the deployment.
Hello Eduardo,
Thank you so much for your idea. We are marking this as “on our radar” since we think this is a good idea. We've have been discussing this internally.
What are the most frequently changed configurations?
Thanks
Hi João,
I would say that the most common configurations are consumed/exposed web services End Points, Site Properties and maybe a little less Timers (schedule/activate or deactivate and timeouts).
Probably in certain situations the necessity to configure connections is also important. This is kind of convered by LifeTime during the execution of the plan. Not sure if this happen in the first or second stage in a 2 stage deployment. But for sure would be nice to be able to let other connections to be also prepared in the plan beside the connection used by the extensions. And I don't remember even if it is possible to actually create a connection or just associate one (but I think the first).
I think those are the most common changes related to deploys.
Cheers!
Thanks Eduardo!
I'd challenge the rest of the community to give feedback here! :)
Thanks!
We are developing an OS application precisely to do this. (still in a early stage)
Already have some ideas structured and can share info internally.
A nice improvement on site properties would have the capability to configure the default value for each environment before we actually deploy them. It would be nice this be configurated on Lifetime.
Changed the category to Lifetime
Hi Franco,
Thank you for posting your idea!
Is your idea some like related to this one?
https://www.outsystems.com/ideas/5032/LifeTime+-+Defining+Configuration+during+Deployment+Planning
Cheers
Check out this idea, it takes the configuration issue a bit further:
https://www.outsystems.com/ideas/1220/Configuration+management+%2f+versioning
In LifeTime:
It would be nice to see a reminder (warning message) to fill/change a newly deployed site property value, after a deployment. So this would be the first time that site property gets deployed to a new environment.
This would be especially important when the site property is getting deployed to Production for the first time.
Agree. Maybe even an email notification to some group. I had this problem so many times, when we forgot to change a site property or integration effective url.
Yes Roman. I’ve also had this problem a lot of times.
As mather of fact, just last week we deployed a fairly large application to production for a client and we forgot to set a couple of site property values which caused a lot of unnecessary problems.
I think LT having this feature would have saved us the headaches!
Maybe these settings should be part of the deployment plan; now you can create a note for changing webservices, rest endpoints, site-properties and timers.
Would be useful to add suggested values for all these settings for the next environment; that could be overwritten by the Operator that performs the publish.
I like the idea of Matthias, a warning is nice, but what really is needed is the option to configured all this in your deployment plan, and that during deployment LifeTime will configure the settings in the target environment.
This makes even more sense if your organisation uses for example Jenkins for kicking of deployments in OutSystems.
Hi guys!
Thanks for sharing, we will be launching the capability to not miss empty site-properties and fill them during the deployment plan as public early access in the next release of LifeTime.
Here is a screenshot:
Stay tuned, activate the feature and give us feedback.
Hi all,
I can understand the question but then more in general that the property needs to be changed, not because of the default value. I teach everybody that when you'll create an site property it's default value needs to be the value on production so you'll never have an issue with it.Adding it to the notes is fine, but if a timer is depending on it which is running on publish you're still to late to adjust it...Kind regards,Evert
Hi,
I agree with Evert.
Although we know that best practice, the issue still happens. Mainly, when do you don't know the PRD value in development time, or your environments are not well separated, and you ended running an app in QA with PRD impact due to wrong values.
The problem is not only present in site-properties, so we would like to keep helping you not to miss wrong configuration values or adjust it too late.
Is very important for us to get your feedback, please keep it coming and don't forget to try the feature out!
Cheers,
Joao Bento
As said in a merged idea, we are working on this. Stay tuned and give us feedback!