- NAME
-
- gcloud design-center spaces application-templates components update - update a component
- SYNOPSIS
-
-
gcloud design-center spaces application-templates components update(COMPONENT:--application-template=APPLICATION_TEMPLATE--location=LOCATION--space=SPACE) [--display-name=DISPLAY_NAME] [--application-info-apphub-id=APPLICATION_INFO_APPHUB_ID--application-info-deployment-region=APPLICATION_INFO_DEPLOYMENT_REGION--application-info-display-name=APPLICATION_INFO_DISPLAY_NAME--clear-application-info--scope-type=SCOPE_TYPE--attributes-business-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL] |--add-attributes-business-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]--clear-attributes-business-owners|--remove-attributes-business-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]--attributes-developer-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL] |--add-attributes-developer-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]--clear-attributes-developer-owners|--remove-attributes-developer-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]--attributes-operator-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL] |--add-attributes-operator-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]--clear-attributes-operator-owners|--remove-attributes-operator-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]--criticality-level=CRITICALITY_LEVEL--[no-]criticality-mission-critical--criticality-type=CRITICALITY_TYPE--environment=ENVIRONMENT--environment-type=ENVIRONMENT_TYPE] [--parameters=[key=KEY],[value=VALUE] |--add-parameters=[key=KEY],[value=VALUE]--clear-parameters|--remove-parameters=[key=KEY],[value=VALUE]] [GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
- Update a component in an application template.
- EXAMPLES
-
To update the display name to
My New Component Namein the componentmy-componentin application templatemy-app-template, spacemy-space, projectmy-projectand locationus-central1, run:gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --display-name="My New Component Name"Or run:
gcloud design-center spaces application-templates components update projects/my-project/locations/us-central1/spaces/my-space/applicationTemplates/my-app-template/components/my-component --display-name="My New Component Name"To update the parameters with new key-value pairs of
project_id:new-projectandservice_name:new-servicefor the componentmy-componentin application templatemy-app-template, spacemy-space, projectmy-projectand locationus-central1, run the following shorthand example:gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --parameters=key=project_id,value=new-project --add-parameters=key=service_name,value=new-serviceOr run the following JSON example:
gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --parameters='[{"key": "project_id", "value": "new-project"},{"key": "service_name", "value": "new-service"}]'Or create a YAML or JSON file with the parameters and run the following file example:
gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --parameters=my-parameters.yamlTo add new parameters key-value pair of
project_id:new-projectandservice_name:new-serviceto the componentmy-componentin application templatemy-app-template, spacemy-space, projectmy-projectand locationus-central1, run the following shorthand example:gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --add-parameters=key=project_id,value=new-project --add-parameters=key=service_name,value=new-serviceOr run the following JSON example:
gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --add-parameters='[{"key": "project_id", "value":"new-project"}, {"key": "service_name", "value": "new-service"}]'Or create a YAML or JSON file with the parameters and run the following file example:
gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --add-parameters=my-parameters.yamlTo clear all parameters from the component
my-componentin application templatemy-app-template, spacemy-space, projectmy-projectand locationus-central1, run:gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --clear-parametersTo remove an existing parameter key-value pair of
project_id:new-projectfrom the componentmy-componentin application templatemy-app-template, spacemy-space, projectmy-projectand locationus-central1, run:gcloud design-center spaces application-templates components update my-component --application-template=my-app-template --space=my-space --project=my-project --location=us-central1 --remove-parameters=key=project_id,value=my-project - POSITIONAL ARGUMENTS
-
-
Component resource - Identifier. The component name. 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
projectattribute:-
provide the argument
componenton the command line with a fully specified name; -
provide the argument
--projecton the command line; -
set the property
core/project.
This must be specified.
COMPONENT-
ID of the component or fully qualified identifier for the component.
To set the
componentattribute:-
provide the argument
componenton the command line.
This positional argument must be specified if any of the other arguments in this group are specified.
-
provide the argument
--application-template=APPLICATION_TEMPLATE-
The applicationTemplate id of the component resource.
To set the
application-templateattribute:-
provide the argument
componenton the command line with a fully specified name; -
provide the argument
--application-templateon the command line.
-
provide the argument
--location=LOCATION-
The location id of the component resource.
To set the
locationattribute:-
provide the argument
componenton the command line with a fully specified name; -
provide the argument
--locationon the command line.
-
provide the argument
--space=SPACE-
The space id of the component resource.
To set the
spaceattribute:-
provide the argument
componenton the command line with a fully specified name; -
provide the argument
--spaceon the command line.
-
provide the argument
-
provide the argument
-
Component resource - Identifier. The component name. 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.
- FLAGS
-
--display-name=DISPLAY_NAME- The component display name.
- This captures the apphub application details associated with the component.
--application-info-apphub-id=APPLICATION_INFO_APPHUB_ID-
The application ID of the apphub application. The ID must be 1-63 characters
long and should match the regular expression
^[a-z]([a-z0-9-]{0,61}[a-z0-9])?$. --application-info-deployment-region=APPLICATION_INFO_DEPLOYMENT_REGION-
Deployment region for the component. If the scope is set to REGIONAL, then the
apphub application is created in this region, e.g.
us-central1. --application-info-display-name=APPLICATION_INFO_DISPLAY_NAME- Display name for the application. The number of characters should be less than 64 characters.
--clear-application-info- Set component.applicationInfo back to default value.
- Scope of an application.
--scope-type=SCOPE_TYPE-
Scope Type.
SCOPE_TYPEmust be one of:global- Global type.
regional- Regional type.
- Consumer provided attributes.
-
Update attributes_business_owners.
At most one of these can be specified:
--attributes-business-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Set attributes_business_owners to new value. Business team that ensures user
needs are met and value is delivered.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--attributes-business-owners=channel={uri=string},displayName=string,email=string --attributes-business-owners=channel={uri=string},displayName=string,email=string
JSON Example:--attributes-business-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--attributes-business-owners=path_to_file.(yaml|json)
-
Or at least one of these can be specified:
--add-attributes-business-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Add new value to attributes_business_owners list. Business team that ensures
user needs are met and value is delivered.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--add-attributes-business-owners=channel={uri=string},displayName=string,email=string --add-attributes-business-owners=channel={uri=string},displayName=string,email=string
JSON Example:--add-attributes-business-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--add-attributes-business-owners=path_to_file.(yaml|json)
-
At most one of these can be specified:
--clear-attributes-business-owners- Clear attributes_business_owners value and set to empty list.
--remove-attributes-business-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Remove existing value from attributes_business_owners list. Business team that
ensures user needs are met and value is delivered.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--remove-attributes-business-owners=channel={uri=string},displayName=string,email=string --remove-attributes-business-owners=channel={uri=string},displayName=string,email=string
JSON Example:--remove-attributes-business-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--remove-attributes-business-owners=path_to_file.(yaml|json)
-
Update attributes_developer_owners.
At most one of these can be specified:
--attributes-developer-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Set attributes_developer_owners to new value. Developer team that owns
development and coding.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--attributes-developer-owners=channel={uri=string},displayName=string,email=string --attributes-developer-owners=channel={uri=string},displayName=string,email=string
JSON Example:--attributes-developer-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--attributes-developer-owners=path_to_file.(yaml|json)
-
Or at least one of these can be specified:
--add-attributes-developer-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Add new value to attributes_developer_owners list. Developer team that owns
development and coding.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--add-attributes-developer-owners=channel={uri=string},displayName=string,email=string --add-attributes-developer-owners=channel={uri=string},displayName=string,email=string
JSON Example:--add-attributes-developer-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--add-attributes-developer-owners=path_to_file.(yaml|json)
-
At most one of these can be specified:
--clear-attributes-developer-owners- Clear attributes_developer_owners value and set to empty list.
--remove-attributes-developer-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Remove existing value from attributes_developer_owners list. Developer team that
owns development and coding.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--remove-attributes-developer-owners=channel={uri=string},displayName=string,email=string --remove-attributes-developer-owners=channel={uri=string},displayName=string,email=string
JSON Example:--remove-attributes-developer-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--remove-attributes-developer-owners=path_to_file.(yaml|json)
-
Update attributes_operator_owners.
At most one of these can be specified:
--attributes-operator-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Set attributes_operator_owners to new value. Operator team that ensures runtime
and operations.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--attributes-operator-owners=channel={uri=string},displayName=string,email=string --attributes-operator-owners=channel={uri=string},displayName=string,email=string
JSON Example:--attributes-operator-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--attributes-operator-owners=path_to_file.(yaml|json)
-
Or at least one of these can be specified:
--add-attributes-operator-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Add new value to attributes_operator_owners list. Operator team that ensures
runtime and operations.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--add-attributes-operator-owners=channel={uri=string},displayName=string,email=string --add-attributes-operator-owners=channel={uri=string},displayName=string,email=string
JSON Example:--add-attributes-operator-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--add-attributes-operator-owners=path_to_file.(yaml|json)
-
At most one of these can be specified:
--clear-attributes-operator-owners- Clear attributes_operator_owners value and set to empty list.
--remove-attributes-operator-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL]-
Remove existing value from attributes_operator_owners list. Operator team that
ensures runtime and operations.
channel-
Communication channel of the contacts.
uri- URI of the channel.
displayName- Contact's name. Can have a maximum length of 63 characters.
email- Email address of the contacts.
Shorthand Example:--remove-attributes-operator-owners=channel={uri=string},displayName=string,email=string --remove-attributes-operator-owners=channel={uri=string},displayName=string,email=string
JSON Example:--remove-attributes-operator-owners='[{"channel": {"uri": "string"}, "displayName": "string", "email": "string"}]'
File Example:--remove-attributes-operator-owners=path_to_file.(yaml|json)
- Criticality of the Application, Service, or Workload
--criticality-level=CRITICALITY_LEVEL- Criticality level. Can contain only lowercase letters, numeric characters, underscores, and dashes. Can have a maximum length of 63 characters. Deprecated: Please refer to type instead.
--[no-]criticality-mission-critical-
Indicates mission-critical Application, Service, or Workload. Deprecated: Please
refer to type instead. Use
--criticality-mission-criticalto enable and--no-criticality-mission-criticalto disable. --criticality-type=CRITICALITY_TYPE-
Criticality Type.
CRITICALITY_TYPEmust be one of:high- High impact.
low- Low impact.
medium- Medium impact.
mission-critical- Mission critical service, application or workload.
- Environment of the Application, Service, or Workload
--environment=ENVIRONMENT- Environment name. Can contain only lowercase letters, numeric characters, underscores, and dashes. Can have a maximum length of 63 characters. Deprecated: Please refer to type instead.
--environment-type=ENVIRONMENT_TYPE-
Environment Type.
ENVIRONMENT_TYPEmust be one of:development- Development environment.
production- Production environment.
staging- Staging environment.
test- Test environment.
-
Update parameters.
At most one of these can be specified:
--parameters=[key=KEY],[value=VALUE]-
Set parameters to new value. The component parameters.
key- The key of the parameter.
value- The value of the parameter.
Shorthand Example:--parameters=key=string,value={…} --parameters=key=string,value={…}
JSON Example:--parameters='[{"key": "string", "value": {…}}]'
File Example:--parameters=path_to_file.(yaml|json)
-
Or at least one of these can be specified:
--add-parameters=[key=KEY],[value=VALUE]-
Add new value to parameters list. The component parameters.
key- The key of the parameter.
value- The value of the parameter.
Shorthand Example:--add-parameters=key=string,value={…} --add-parameters=key=string,value={…}
JSON Example:--add-parameters='[{"key": "string", "value": {…}}]'
File Example:--add-parameters=path_to_file.(yaml|json)
-
At most one of these can be specified:
--clear-parameters- Clear parameters value and set to empty list.
--remove-parameters=[key=KEY],[value=VALUE]-
Remove existing value from parameters list. The component parameters.
key- The key of the parameter.
value- The value of the parameter.
Shorthand Example:--remove-parameters=key=string,value={…} --remove-parameters=key=string,value={…}
JSON Example:--remove-parameters='[{"key": "string", "value": {…}}]'
File Example:--remove-parameters=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 helpfor details. - API REFERENCE
-
This command uses the
designcenter/v1API. The full documentation for this API can be found at: http://cloud.google.com/application-design-center/docs - NOTES
-
This variant is also available:
gcloud alpha design-center spaces application-templates components update
gcloud design-center spaces application-templates components update
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-03-24 UTC.