...
There is a separate use case around changes that are deemed detrimental and therefore cannot be deployed into higher environments. For example, doing so could result in a data loss. This use case is captured in another guide "How To: Negate Abandon changes" which will prevent changes from deploying further in the pipeline.
...
Process for negating changes is different for stored logic and ddl/dml code.
Changes in "data_dml", "ddl", "ddl_direct", "sql", or "sql_direct"
...
folders
We will assume that a script by the name of "international_billing.sql" was packaged from "sql_direct" directory. This script created several tables. One of those tables "international_billing_custom" is not needed. Steps below will guide you how to negate this change, i.e., drop table international_billing_custom
...
| Info | ||
|---|---|---|
| ||
Prior to deploying your changes to the target environment, especially when deploying to PROD, run a Forecast to check that negating changesets are getting picked up by your release labels and deployed in the correct order. |
Changes in "procedure", "function", "package", "packagebody", "trigger" and "view"
...
stored logic folders
Note: Scripts committed into one of these directories do not move to the "archive" directory. All stored logic scripts stay in their original directories after packaging.
...
- Since scripts in the "procedure" directory do not get archived, the original faulty script is already exists in that directory.
- The Developer will checkout the script from SCMÂ
- Rework the script.
- Commit the reworked script using the same file name and in the same directory where it was originally placed ("procedure").
- Packager will detect a new commit in the "procedure" directory. As a result, a second changeset will be created for the same procedure.
- Because the reworked script was packaged in a later commit relative to the original faulty script, Datical will deploy the reworked script in the same order as the SCM commit.
- For example, when deploy changes to PROD environment, Datical will deploy the first changeset for "
intl_cust_dep" procedure. This will create the procedure in PROD with faulty code. Datical will then proceed with deploying other changesets including the reworked changeset which will update the procedure with new code.
- For example, when deploy changes to PROD environment, Datical will deploy the first changeset for "
...
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...