gcloud-help/gcloud/beta/saas-runtime/saas/update

NAME
    gcloud beta saas-runtime saas update - update a SaaS

SYNOPSIS
    gcloud beta saas-runtime saas update (SAAS : --location=LOCATION)
        [--labels=[LABELS,...]
          | --update-labels=[UPDATE_LABELS,...] --clear-labels
          | --remove-labels=REMOVE_LABELS]
        [--locations=[name=NAME]
          | --add-locations=[name=NAME] --clear-locations
          | --remove-locations=[name=NAME]] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (BETA) Update a SaaS

EXAMPLES
    To update the SaaS, run:

        $ gcloud beta saas-runtime saas update my-saas

POSITIONAL ARGUMENTS
     Saas resource - Identifier. The resource name (full URI of the resource)
     following the standard naming scheme:

         "projects/{project}/locations/{location}/saas/{saas}" The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

     To set the project attribute:
      ◆ provide the argument saas on the command line with a fully specified
        name;
      ◆ provide the argument --project on the command line;
      ◆ set the property core/project.

     This must be specified.

       SAAS
          ID of the saas or fully qualified identifier for the saas.

          To set the saas attribute:
          ▸ provide the argument saas on the command line.

          This positional argument must be specified if any of the other
          arguments in this group are specified.

       --location=LOCATION
          Location ID

          To set the location attribute:
          ▸ provide the argument saas on the command line with a fully
            specified name;
          ▸ provide the argument --location on the command line.

FLAGS
     Update labels.

     At most one of these can be specified:

       --labels=[LABELS,...]
          Set labels to new value. The labels on the resource, which can be
          used for categorization. similar to Kubernetes resource labels.

           KEY
              Keys must start with a lowercase character and contain only
              hyphens (-), underscores (_), lowercase characters, and numbers.

           VALUE
              Values must contain only hyphens (-), underscores (_), lowercase
              characters, and numbers.

          Shorthand Example:

              --labels=string=string

          JSON Example:

              --labels='{"string": "string"}'

          File Example:

              --labels=path_to_file.(yaml|json)

       --update-labels=[UPDATE_LABELS,...]
          Update labels value or add key value pair. The labels on the
          resource, which can be used for categorization. similar to Kubernetes
          resource labels.

           KEY
              Keys must start with a lowercase character and contain only
              hyphens (-), underscores (_), lowercase characters, and numbers.

           VALUE
              Values must contain only hyphens (-), underscores (_), lowercase
              characters, and numbers.

          Shorthand Example:

              --update-labels=string=string

          JSON Example:

              --update-labels='{"string": "string"}'

          File Example:

              --update-labels=path_to_file.(yaml|json)

       At most one of these can be specified:

         --clear-labels
            Clear labels value and set to empty map.

         --remove-labels=REMOVE_LABELS
            Remove existing value from map labels. Sets remove_labels value.

            Shorthand Example:

                --remove-labels=string,string

            JSON Example:

                --remove-labels=["string"]

            File Example:

                --remove-labels=path_to_file.(yaml|json)

     Update locations.

     At most one of these can be specified:

       --locations=[name=NAME]
          Set locations to new value. List of locations that the service is
          available in. Rollout refers to the list to generate a rollout plan.

           name
              Name of location. Example flag usage:
              --locations=name=us-central1.

          Shorthand Example:

              --locations=name=string --locations=name=string

          JSON Example:

              --locations='[{"name": "string"}]'

          File Example:

              --locations=path_to_file.(yaml|json)

       --add-locations=[name=NAME]
          Add new value to locations list. List of locations that the service
          is available in. Rollout refers to the list to generate a rollout
          plan.

           name
              Name of location. Example flag usage:
              --locations=name=us-central1.

          Shorthand Example:

              --add-locations=name=string --add-locations=name=string

          JSON Example:

              --add-locations='[{"name": "string"}]'

          File Example:

              --add-locations=path_to_file.(yaml|json)

       At most one of these can be specified:

         --clear-locations
            Clear locations value and set to empty list.

         --remove-locations=[name=NAME]
            Remove existing value from locations list. List of locations that
            the service is available in. Rollout refers to the list to generate
            a rollout plan.

             name
                Name of location. Example flag usage:
                --locations=name=us-central1.

            Shorthand Example:

                --remove-locations=name=string --remove-locations=name=string

            JSON Example:

                --remove-locations='[{"name": "string"}]'

            File Example:

                --remove-locations=path_to_file.(yaml|json)

GCLOUD WIDE FLAGS
    These flags are available to all commands: --access-token-file, --account,
    --billing-project, --configuration, --flags-file, --flatten, --format,
    --help, --impersonate-service-account, --log-http, --project, --quiet,
    --trace-token, --user-output-enabled, --verbosity.

    Run $ gcloud help for details.

API REFERENCE
    This command uses the saasservicemgmt/v1beta1 API. The full documentation
    for this API can be found at: https://cloud.google.com/saas-runtime/docs

NOTES
    This command is currently in beta and might change without notice.