initial commit, need to fix system test #9518
Annotations
2 errors
Integration Tests (Daemon):
packages/cli/__tests__/zosfiles/__integration__/upload/dtu/cli.files.upload.dtu.integration.test.ts#L40
expect(received).toMatchSnapshot()
Snapshot name: `Upload local dir to uss dir should display the help 1`
- Snapshot - 2
+ Received + 7
@@ -109,10 +109,15 @@
--include-hidden | --ih (boolean)
Include hidden files and folders that have names beginning with a dot
+ --encoding | --ec (string)
+
+ Data content in encoding mode, which means that data conversion is performed
+ according to the encoding specified.
+
--response-timeout | --rto (number)
The maximum amount of time in seconds the z/OSMF Files TSO servlet should run
before returning a response. Any request exceeding this amount of time will be
terminated and return an error. Allowed values: 5 - 600
@@ -241,9 +246,9 @@
================ Z/OS FILES UPLOAD LOCAL DIRECTORY TO USS DIRECTORY HELP WITH RFJ===============
{
"success": true,
"exitCode": 0,
"message": "The help was constructed for command: dir-to-uss.",
- "stdout": "\n COMMAND NAME\n ------------\n\n dir-to-uss | dtu\n\n DESCRIPTION\n -----------\n\n Upload a local directory to a USS directory.\n\n An optional .zosattributes file in the source directory can be used to control\n file conversion and tagging.\n\n An example .zosattributes file:\n # pattern local-encoding remote-encoding\n # Don't upload the node_modules directory\n node_modules -\n # Don't upload files that start with periods\n .* -\n # Upload jpg images in binary\n *.jpg binary binary\n # Convert CICS Node.js profiles to EBCDIC\n *.profile ISO8859-1 EBCDIC\n\n Lines starting with the ‘#’ character are comments. Each line can specify up to\n three positional attributes:\n A pattern to match a set of files. Pattern-matching syntax follows\n the same rules as those that apply in .gitignore files (note that negated\n patterns that begin with ‘!’ are not supported). See\n https://git-scm.com/docs/gitignore#_pattern_format.\n A local-encoding to identify a file’s encoding on the local\n workstation. If '-' is specified for local-encoding,files that match the pattern\n are not transferred.\n A remote-encoding to specify the file’s desired character set on USS.\n This attribute must either match the local encoding or be set to EBCDIC. If set\n to EBCDIC, files are transferred in text mode and converted, otherwise they are\n transferred in binary mode. Remote files are tagged either with the remote\n encoding or as binary.\n\n A .zosattributes file can either be placed in the top-level directory you want\n to upload, or its location can be specified by using the --attributes parameter.\n .zosattributes files that are placed in nested directories are ignored.\n\n\n USAGE\n -----\n\n zowe zos-files upload dir-to-uss <inputDir> <USSDir> [options]\n\n POSITIONAL ARGUMENTS\n --------------------\n\n inputDir\t\t (string)\n\n The local directory path that you want to upload to a USS directory\n\n USSDir\t\t (string)\n\n The name of the USS directory to which you want to upload the local directory\n\n OPTIONS\n -------\n\n --binary | -b (boolean)\n\n Data content in binary mode, which means that no data conversion is performed.\n The data transfer process returns each record as-is, without translation. No\n delimiters are added between records.\n\n --recursive | -r (boolean)\n\n Upload all directories recursively.\n\n --binary-files | --bf (string)\n\n Comma separated list of file names to be uploaded in binary mode. Use this\n option when you upload a directory in default ASCII mode, but you want to\n specify certain files to be uploaded in binary mode. All files matching\n specified file names will be uploaded in binary mode. If a .zosattributes file\n (or equivalent file specified via --attributes) is present, --binary-files will\n be ignored.\n\n --ascii-files | --af (string)\n\n Comma separated list of file names to be uploaded in ASCII mode. Use this optio
|
Integration Tests (Daemon)
Process completed with exit code 1.
|
Loading