HOW can promotion be handled, with HARD CODED SNAPS?

Please read the entire message before answering.

In many companies, production promotion is handled by people that either aren’t, don’t want to be, and sometimes are forbidden to be, knowledgeable about things in that domain. Their job is simply to follow protocols, read promotion instructions, and faithfully execute them. If there is any problem, they report in to the submitter, etc… Frankly, I wouldn’t want to do this manually anyway. Too many things need to be changed and it would justify another test, which can’t be done in production.

To that end, I used newer snaps that handled expressions, to make a product that will AUTOMATICALLY promote to anywhere in the entire enterprise. It is nice because one parameter sets that, and a blank setting sets it to a default, so dev will run with default dev settings, and production will run with production settings by default. This code REQUIRES, NO…, DEMANDS, that we have features that are 99% only in the snaps. Without them, there is simply NO way to automatically promote using snaplogic, because the snaps require values that CHANGE from environment to environment, and the OLD snaps require that the changing values be HARD CODED! In snaplogic’s Defense, snaplogic didn’t write the snaps I seem destined to have to use.

It seems the only option I have at this point for one case is to change a hardcoded snap automatically upon promotion. The change would be a standard one for the environment.

So my question is has anyone done this before? If not, are there any APIs to facilitate the import and export, programmatically? I have a limited time to get an answer, implement and test.

BTW I am trying to only give enough details to answer WHY I have the problem, and the limited timeframe, and why I have to do it, and what I need to do. Ideally, we want to hand stuff to the production team with SIMPLE instructions that they can quickly follow, and keep reusing.