| Info |
|---|
| This functionality became available in the 4.5.1 release. |
...
The JDBC plugin partial deploy support allows for deploying File and Folder type objects. This page explains the two types and their attributes.
| Table of Contents |
|---|
...
DB Objects
File DB (Database) type objects model sql files that are stored in SCM. They are used to copy sql files from an SCM to a filesystem on an endpoint . File where they are executed by JDBC. DB type objects can be sourced only from an SCM. They cannot be created manually. No attributes are required.
Subfolders to the final target location of the file sql files are created by the plugin as long as the endpoint user has sufficient privileges.
Attributes
Name | Description | Default Value | ||
|---|---|---|---|---|
| Target | This is the location where the file will be placed. Property replacement will be performed on the value. If blank, the file will be copied into | ${{FDFILE_ROOT_TARGET_FOLDER}} | ||
| Use Source Path | If this is NOT checked, the file will be placed directly in target. If it is checked, the whole File Name with path will be placed inside the target. |
| ||
| Owner:Group | Set the owner or owner:group of the file to this value. This only work on Unix endpoints. On Windows endpoints, it is ignored. | Owner:Group File Default is the project property to control the default. | ||
| Permission | Set the permissions of the file to this value. This only work on Unix endpoints. On Windows endpoints, it is ignored. If it is not set, and Execute is checked, chmod +x will be run on the file if it is a Unix endpoint. | User Property | The property that will be used to set the username used to log into the database. | FDJDBC_USER - Set this value on the environment/instance, or override it on a project. Alternatively, create a new property on the workflow, and then set its value in one of those locations. |
| Password Property | The property that will be used to set the password used to log into the database. | FDJDBC_PASSWORD- Set this value on the environment/instance, or override it on a project. Alternatively, create a new property on the workflow, and then set its value in one of those locations. | ||
| JDBC URL Property | The property that will be used to set the JDBC URL used to log into the database. | FDJDBC_URL- Set this value on the environment/instance, or override it on a project. Alternatively, create a new property on the workflow, and then set its value in one of those locations. | ||
| Retry Count | How many times should the file be retried before marking it as a failure. It may be useful to set it to a larger value if deploying many files together if the selected order may not be correct. | Retry Count Default is the project property that fills in the default value at evaluate or populate time. | ||
| Ignore Failure | If checked, the file and the execution will be marked successful even if it fails to be processed in any way. The failure will be logged, but there will be no other indication. | Ignore Failure Extensions is the project property that takes a list of extensions. Any files that end with those extensions will have their ignore failures checkbox checked at populate or evaluate time. | ||
| Ignore Compilation Warnings | If checked, the file and the execution will be marked successful even if it encounters a compilation warning. The warning will be logged, but there will be no other indication. | Ignore Compile Error Extensions is the project property that takes a list of extensions. Any files that end with those extensions will have their ignore compilation warnings checkbox checked at populate or evaluate time. | ||
| Property Replacement | If checked, property replacement will be run on the file, unless it appears to be a binary file, and then it will be skipped for property replacement. | Property Replacement DefaultDefault is the project property to control the default. | Execute | If checked|
| Target Location | This is the location where the file will be | executed. This works on both Windows and Unix.Execute Default is the project property to control the default. | ||
| Ignore Failure | If checked, the file and the execution will be marked successful even if it fails to be processed in any way. The failure will still be logged, but there will be no other indication. | Ignore Failure Defaultis the project property to control the default. |
Folder Objects
Folder objects are created manually. They cannot be populated from SCM, but it is possible to add a folder that replicates one in an SCM.
...
placed. Property replacement will be performed on the value. If blank, the file will be copied into | ${{FDJDBC_SQL_ROOT_TARGET_FOLDER}} |
Other Objects
Other objects type objects model non-sql files that are stored in SCM. They are used to copy files that are stored with sql files from an SCM to a filesystem on an endpoint.Optionally they can have property replacement performed on the,. They cannot be created manually. No attributes are required.
Attributes
Name | Description | Default Value | |||||||
|---|---|---|---|---|---|---|---|---|---|
| Target Location | This is the location where the file will be placed. Property replacement will be performed on the value. If blank, the folder will be created in | ${{FDFILEFDJDBC_OTHER_ROOT_TARGET_FOLDER}} | Owner:Group | Owner:Group Folder Default is the project property to control the default. | Permission | Set the permissions of the folder to this value. This only work on Unix endpoints. On Windows endpoints, it is ignored. | Permissions Folder Default is the project property to control the default. | ||
| Property Replacement | If checked, property replacement will be run on the file, unless it appears to be a binary file, and then it will be skipped for property replacement. | Property Replacement DefaultDefault is the project property to control the default. |