Package deployment include environment specific configurations
Have anyone encounter challenges doing package deployment across environment where certain environment specific configurations were included and hence resulted in cross environment references?
A typical example is data feed deployment (though strictly speaking, they are not packages). Exporting them would include the user name, password, URL (A2A feed), DB connection string, file path etc. that are environment specific. Hence some manual post deployment task are needed to correct them thereby introducing operational risk in the deployment process.
Another example would be calculated field where formula would hardcode certain environment specific value. Can I not hardcode the value? Probably not, as the calculated string are URL links to an external system that is environment specific.
The list goes on with notifications (subscription, on-demand etc.) for "from" email addresses, which I'd want to use them as indicator if emails are from production or test environment, data publication connection string, LDAP etc. etc. It seems to be a perfect use case to have some sort of global environment parameters where the settings are not change due to packaging and Archer can reference.
I was wondering how other Archer users are working around this limitation.
- archer deployment
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
Well, you just note all these hardcoded things in the notepad, and them modify them upon migration.
That is why each change you do in DEV env, you need to list down for the possible migration to PROD.
Surely, you may build some advanced tool, which would do all this for you automatically by touching DB directly or by API, but that still would be environments specific, not universal.
Thanks Ilya Khen. I was wondering wouldn't it be great if RSA can provide some kind of global environment parameters setup that can be referenced in formula, data feeds, notification etc.? That way, we don't have to do any direct DB update or calling some API (in any case, there is no API for configuration related setup), which you rightly pointed out that is still not universal.
My challenge is on managing 200-300 data feeds and migrating all of them becomes a nightmare. Each data feed require manual update post migration, which is really time consuming and error prone.