The PeopleSoft plugin package-based project allows for deploying customization File type objects. Customization file type objects model files that are stored in SCM. They are used to copy files from an SCM to a filesystem on an endpoint. Customization file objects can be sourced only from an SCM. They cannot be created manually. No attributes are required.
Sub-folders to the final target location of the file are created by the plugin as long as the endpoint user has sufficient privileges.
Attributes
Name | Code | Description | Default Value |
---|---|---|---|
Source |
| Object Source Location Type | SCM (**populating from SCM) |
Target Location |
| 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 |
|
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. |
|
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. |
|
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. |
|
Execute |
| If checked the file will be executed. This works on both Windows and Unix. |
|
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. |
|