Sign inTry Free

AGENT-SET-CREDENTIAL

On this page

Change the SSH credentials to access a specific host with a MemSQL Ops agent already deployed.

Usage

usage: memsql-ops agent-set-credential [--settings-file SETTINGS_FILE]
                                       [--no-prompt] [-u USER] [-P SSH_PORT]
                                       [-i SSH_KEY] [-p [PASSWORD]]
                                       [agent_id]

Set the SSH credentials to use for the specified agent.

positional arguments:
  agent_id              ID of the agent.

optional arguments:
  --settings-file SETTINGS_FILE
                        A path to a MemSQL Ops settings.conf file. If not set,
                        we will use the file in the same directory as the
                        MemSQL Ops binary.
  --no-prompt           Skip interactive prompts if ID is not provided. This
                        should be used for non-interactive scripts and
                        automation.
  -u USER, --user USER  The user for this credential. By default we will use
                        the same username as the user running this command.
  -P SSH_PORT, --port SSH_PORT
                        The SSH port for this credential. By default we will
                        use port 22.
  -i SSH_KEY, --private-key-file SSH_KEY
                        The path to the private key file for this credential.
  -p [PASSWORD], --password [PASSWORD]
                        The password for this credential. This will be used to
                        attempt sudo access, and if no private key is
                        specified, SSH will authenticate with this password.

Last modified: April 25, 2023

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK