Best practices for global wedge address configs

Question

We have some non senstive values that we would like to have shared across extensions What is the best practice for storing essentially global wedge address config values that are not sensitive and do not change by environment Should those just go in the configuration folder s settings py or should they be stored in the database In our current use case these values are used for memo post mode and would be needed across extensions MaintStartTime 23 00 00 MaintEndTime 03 00 00 InMaintenance false On a side note does q2 already have something in place to handle post mode

Trey Teter · Answer

Hello Having this in settings py is fine but I would recommend just choosing an extension to contain the shared configuration value and putting a cache over top of this that is service level that only goes to the database once every acceptable period of time Could do once an hour and then we can clear the cache if an immediate update is needed The containers themselves have a level of self testing that we run through security scans before they can be deployed Once the service is started up Antilles Monitor will be checking if it is up and running We don t have anything built in that you can tie into but if you wanted to build something in to test your specific functionality there are ways you could tie into and test it Trey

Answers