Currently the Integration Studio (IDE) is used to `Activate` (push) and `Deactivate` (rollback) the ETL code to an environment where Integration Studio is linked with. This doesn't comply with the standard SDLC procedure. The major issue here is that the artifact generation process is not transparent and that there is no way to guarantee the artifact is the outcome of the change that was sought (requirement documents), developed (code changes), tested (QA verified) and approved (peer reviewed and approved) by designated authorities. We need such artifacts to go through various scanning processes against major threats before it can be deployed. We also need to guarantee the immutability of an artifact (which was developed, tested, approved and scanned) that is promoted from Dev -> UAT -> PROD environments.