...
The "metadata.properties" file also allow for files to be repackaged. For use cases when a particular script has already been packaged, and developers would like to fix the script and push it into SCM again without renaming the file name, the “allowRepackaging=true” will let Deployment Packager know to ignore the earlier version of this file and begin repackage the file. Note: The new script needs to account for what was already deploy by the older script. For example, the new script would need to “drop table” if it is creating the table which was previously created by the older script.
A sample file is belowmetadata.properties file
Property | Values | Description |
labels |
| One or more labels that identify this set of changes so they can be easily identified and deployed as a group |
contexts |
| Identifier to tie a set of changes to specific environments. |
allowRepackaging | true or false | Since Datical DB v4.21, this property controls whether you can reuse a filename. The default value is false. |
archive | true or false | Since Datical DB v4.21, this property controls whether files in the data_dml directory get copied to the archive directory. The default value is true. |
schemaName |
| Since Datical DB v4.23, any scripts packaged will use this schema name when one is not specified for objects in the sql script. |
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
# This properties file controls label and context values on Deployment Packager generated change sets labels=label1,label2,label3 contexts=QA,PERF_TEST,UAT allowRepackaging=true |
...