Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.
The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.
💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.
🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.
Start by sharing what could be better - the community and our teams will help take it from there.
We also have similar but very rudimentary internal ObjectScript library that converts JSON configuration into several IRIS ObjectScript API calls. Currently it supports the subset of external service registry, oauth, iop production and task settings we need. It also implements general purpose application configuration pattern all our applications can use (arbitrary JSON configuration is stored into ens lookup table were it can be queried).
The closest existing solution is most likely the Installation Manifest.
This can be used for installation and upgrades.
I am not certain if it is recommended for container deployments and whether or not improvements could be made for container deployments.
Hi Kari,
have you looked at the Configuration Merge File? This mechanism offers a lot of flexibility for adapting the configuration of a running instance, and is used heavily in our own cloud deployment pipelines.