The globus-connect-server node create command provides a command-line interface to creating a node configuration file for use with globus-connect-server node setup. This is useful when you want to be able to redeploy a node’s configuration without maintaining any state on the node between redeploys.
When you invoke this command with its required arguments, it will create a new node ID and node-specific encryption key, and will add the node specific encryption key to the endpoint’s keychain. It will output a file containing the node id and key. This file can be passed to globus-connect-server node setup as the argument to the --import-node command-line option
endpoint key convertto update any existing deployment keys to include the client ID and secret.
- -h, --help
Show help message and exit.
Show the version and exit.
- -c, --client-id CLIENT_ID (required prior to 5.4.67, removed in 5.4.67)
Auth Client ID for the Globus Connect Server endpoint. See the note above for when to use this option.
- --deployment-key DEPLOYMENT_KEY_FILE
Path to deployment key created when setting up the endpoint. By default the path
- --export-node NODE_INFO_JSON
File to write node configuration to in order to restore the node by rerunning this command at a later time.
This example creates a node configuration using the client id stored in the
$CLIENT_ID environment variable and writes the resulting configuration to
globus-connect-server node create \ -c $CLIENT_ID \ --deployment-key deployment-key.json \ --export-node node.json