As of FlexDeploy 9.0.0.3, all special characters are handled when sourcing from OAC and deploying to OAC using Linux endpoints and with FlexDeploy running on Linux.
Starting with FlexDeploy 9.0.0.3, following escape sequence is used. This means that if you use any files that contain these characters, you should rediscover with the inactivate checkbox checked. A new file will appear. The name will be similar but will be percent encoded. Files with \ in them didn’t work previously. Files with a colon will be in different places in the file catalog as of 9.0.0.3, so any files with : in there will lose their history and packages containing them will need to be modified to have the file in the new location and builds will need to be redone.Character or String | Escaped as |
|---|---|
: | %3a |
\/ (back slash forward slash together) | %2f |
\ | %5c |
Known Limitations
On Windows, folders and files cannot start or end with spaces. If it is done, Windows endpoints cannot be used, and FlexDeploy on Windows will have similar issues.
If you are exporting to SCM, most special characters should still work on Linux, but more failures on Windows are likely. Windows has protected names for files and folders like COM2 and CON. If you use a protected name as a folder name, this will also fail on Windows. Git SCM is tested the most with special characters. It is likely that other SCMs will have issues handling special characters.
You can open a support ticket if you find an issue with special characters or have any other issues.