SUPERUSER-DELETE

On this page

Deletes a superuser that can manage MemSQL Ops.

Superusers are privileged users that can make changes that modify SingleStore and MemSQL Ops behavior. By default, no superuser is defined. In this case, all who access the MemSQL Ops interface have read/write access.

Usage

usage: memsql-ops superuser-add [--settings-file SETTINGS_FILE]
                                [-p [PASSWORD]]
                                username

Add a superuser that can manage MemSQL Ops.

positional arguments:
  username              The name for this superuser.

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.
  -p [PASSWORD], --password [PASSWORD]
                        The password for this superuser. Leave blank to read
                        the MEMSQL_PASSWORD environment variable, or have a
                        password prompt if MEMSQL_PASSWORD is not set.

Last modified: April 25, 2023

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