While no UI exists to create a deployment file to specify host items to remove it is possible to use the APIs to create such a deployment file - see the last example in the top section of the class documentation for Ens.Deployment.Utils. This is the same removal mechanism used when creating the rollback mechanism.
link at https://irisdocs.intersystems.com/irislatest/csp/documatic/%25CSP.Documa...
I defer to those with experience in the field to offer comparative advice but concerning the Production Export functionality:
For existing environments it is possible to use the Export for deployment from the Production configuration page for one or more items and not the whole production. This allows changing existing items or adding items to a production when deploying the export file. When changing an item the deployment code will disable the item first if it is enabled and then re-enable the item as necessary after the deployment has finished.
It is possible to remove items using the deployment functionality but for this one needs to use Ens.Deployment.Util APIs and not the GUI to create the removal deployment package.
Concerning settings - if you haven't seen perhaps System Default Settings might be appropriate (https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY...).
An alternative use of System Default Settings by some sites is to use for the same values without having to enter per item - hence the option in the Export for deployment dialog to export deployable System Default Settings.
The Export from the Production configuration page attempts to identify what are linked items/code but might not be complete. This is the reason for being able to add Studio project contents to the export. In version 2017.2.0 we added detection of RecordMap classes to be included in the export.
I am doing work with Caché LDAP support and am benefiting from using the Apache DS and Apache Directory Studio plug-in (http://directory.apache.org/studio/update) with Atelier.
Log in or create a new account to continue