...
MettleCI CLI commands most commonly execute on the MettleCI Agent Host (described here) and communicate with the DataStage Engine to perform build and deployment tasks. Those commands which communicate over SSH (most notably those from the Remote Namespace with the privateKey option) are dependent upon correct configuration of the SSH between these two hosts.
In the diagram above the MettleCI Agent Host (described here) stores a private key file (named client.key in the diagram above) for which the public key equivalent (e.g. client.key.pub) is stored inside the ~/.ssh/authorized_keys file of the user account you are using to execute the MettleCI Workbench - typically mciworkb. This permits SSH connection between the MettleCI Agent Host and your DataStage Engine upon which the MettleCI Workbench is running.
...
| Code Block |
|---|
$> ls -ld /home/mciworkb/.ssh drwx------ 2 rootmciworkb rootdstage 144 Feb 16 14:3126 .ssh |
These properties can be established with the following commands:
...
| Code Block | ||
|---|---|---|
| ||
$> ls -ld /home/mciworkb/.ssh/authorized_keys -rw------- 1 mciworkb dstage 1167 Feb 16 14:2631 .ssh/authorized_keys |
Third Party Systems
...