13
 Followers
48
 Likes

LifeTime - Defining Configuration during Deployment Planning

Lifetime
Working on it
expected delivery in Q1 2020

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.

Created on 2 Jul 2018
Comments (26)
Changed the status to
On our radar


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.

Merged this idea with 'Site Properties - Configuration behavior' (created on 28 Jun 2018 13:18:49 by Franco)

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.



This comment was:
- originally posted on idea 'Site Properties - Configuration behavior' (created on 28 Jun 2018 by Franco)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:06:42 by João Bento

Changed the category to Lifetime




This comment was:
- originally posted on idea 'Site Properties - Configuration behavior' (created on 28 Jun 2018 by Franco)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:06:42 by João Bento

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



This comment was:
- originally posted on idea 'Site Properties - Configuration behavior' (created on 28 Jun 2018 by Franco)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:06:42 by João Bento

Check out this idea, it takes the configuration issue a bit further:

https://www.outsystems.com/ideas/1220/Configuration+management+%2f+versioning



This comment was:
- originally posted on idea 'Site Properties - Configuration behavior' (created on 28 Jun 2018 by Franco)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:06:42 by João Bento
Merged this idea with 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 21:46:49 by Nordin Ahdi)

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.



This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento

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. 



This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento

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!



This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento

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.



This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento

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.



This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento

Changed the category to Lifetime




This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento
Changed the status to
Working on it
expected delivery in Q2 2019


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.

Cheers!



This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento

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



This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento

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



This comment was:
- originally posted on idea 'LifeTime - Reminder to fill/change new site properties after deployment' (created on 09 Feb 2019 by Nordin Ahdi)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 22 May 2019 18:08:00 by João Bento
Changed the status to
Working on it
expected delivery in Q2 2019


As said in a merged idea, we are working on this. Stay tuned and give us feedback!

It would be an improvement in general so glad to see you're working on it.

Able to change some configurations in the deployment plan since LifeTime May.2019 version for site properties and July CP1 for set the names of the physical tables of each external database entity.

Feedback is welcome here: https://www.outsystems.com/forums/discussion/48360/configure-application-settings-during-deployment/


We expect to keep improving this. 


Cheers!

Merged this idea with 'Allow to change the effective value of new site properties, endpoints and timers during staging proces' (created on 04 Feb 2019 12:55:39 by Stefan Dirkx)

Allow to change the effective value of new site properties, endpoints and timers during staging proces.

Often these values are different per environment. It would be helpful to have the same kind of warning for configuration as with a new database connection. So it has the correct value when the application is online and it is not forgotten during the staging process.



This comment was:
- originally posted on idea 'Allow to change the effective value of new site properties, endpoints and timers during staging proces' (created on 04 Feb 2019 by Stefan Dirkx)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 07 Nov 2019 11:51:21 by João Bento

Changed the category to Backend




This comment was:
- originally posted on idea 'Allow to change the effective value of new site properties, endpoints and timers during staging proces' (created on 04 Feb 2019 by Stefan Dirkx)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 07 Nov 2019 11:51:21 by João Bento

Isn't this already available as an early access feature in one of the latest platform)/lifetime versions?



This comment was:
- originally posted on idea 'Allow to change the effective value of new site properties, endpoints and timers during staging proces' (created on 04 Feb 2019 by Stefan Dirkx)
- merged to idea 'LifeTime - Defining Configuration during Deployment Planning' on 07 Nov 2019 11:51:21 by João Bento
views
1564
Followers
13