Catalog AdminORCatalog Managerfor the
Google Cloud organization associated with the Google Cloud project which
has Service Catalog enabled. If you don't have this role, contact
your Organization Administrator to request access.
Storage Adminfor
the Google Cloud project where you want to create your solution. If your
Terraform config is in a different project, you must also have the
Storage Admin role for the project that contains your Terraform config.
Cloud Build Editorfor the Google Cloud project where you want to create the solution.
If you plan to use your own service account, you must also have theService Account Userrole for the Google Cloud project that contains the service account that you
plan to use.
If you don't have these roles, contact your Organization Administrator to
request access.
If you plan to use your own service account, your service account must have
the followingIAM roles:
Storage Adminfor
the Google Cloud project where you want to create your solution. If your
Terraform config is in a different project, your service account must
also have the roleStorage Object Viewerfor the project containing the Terraform config.
Logs Writerfor the
Google Cloud project where you want to create your solution.
If you don't have these roles, contact your Organization Administrator to
request access.
Update a solution
When you edit a solution in Service Catalog, you immediately update
the solution in any catalogs where it's assigned. Updating a solution doesn't
affect existing deployments, and users who access the solution after you update
it can only deploy the latest version.
For Terraform solutions, if you update the configuration, a new version appears
to users on the user'sDeploymentspage in the Google Cloud console. Users can
choose to update their deployment to the latest version.
In the list of solutions, click the solution name to open theSolutions
Detailspage.
In the top menu, clickEDIT.
Make any needed updates to the solution.
Optionally, you can provide your own service account by clicking the
checkbox next toSelect or enter your own service account. If your
service account is located in the same Google Cloud project where you're
creating your solution, selectSelect a service account from the current project, and select your
service account from the drop-down menu. If your service account is located
in a different Google Cloud project from your solution, selectEnter a service account email from any project, and enter the email of
your service account.
ClickUPDATE.
The updated solution details now appear on theSolutions Detailspage.
Update a Terraform configuration
Terraform solutions use Cloud Storage'sObject Versioningto manage updates to configuration files. To update the configuration file of a
Terraform solution, you have the following options:
Use a different Cloud Storage object that contains a new configuration
file. To change the Cloud Storage object for a solution,edit the
solution detailsand update theLink to Terraform configwith the URL path to the new object. After you
update the solution details, users can immediately deploy the latest version.
Update the solution's current Cloud Storage object with a new
version of the configuration. For steps to upload a new configuration file,
visitUploading objects. After you update
the solution's Cloud Storage object, you must alsoview and apply the
changesto the solution in Service Catalog.
View and apply a newer version of a configuration
When Service Catalog detects changes to a Terraform configuration file,
you must apply the latest version to update the solution for your users.
To view and apply the latest version of a Terraform configuration:
Go to the Service Catalog AdminSolutionspage in the
Google Cloud console. Go to the Solutions page
In the table of solutions, go to the solution'sVersion statusand clickNew version available.
On theSolutions Detailspage, clickCompare versionsto download and
compare the current and latest version of the configuration. After you
compare versions, clickCloseto return to theSolution Detailspage.
ClickApply newer version.
UnderNew version highlights, add a description to tell users about the
updates to the configuration.
Optionally, you can provide your own service account by clicking the checkbox
next toSelect or enter your own service account. If your service account
is located in the same Google Cloud project where you're creating your
solution, selectSelect a service account from the current project, and
select your service account from the drop-down menu. If your service account
is located in a different Google Cloud project from your solution, selectEnter a service account email from any project, and enter the email of
your service account.
ClickUpdate.
Delete solutions from Service Catalog
When you delete a solution, you remove the solution from any associated catalogs,
and your Service Catalog users can no longer view or launch the solution. For Deployment Manager-based solutions, users can continue to access
and use their existing deployments.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Managing solutions\n==================\n\nIn this guide, you learn how to update and delete solutions in Service Catalog.\n\nIf you prefer to remove access to a solution, see [Removing a solution from a\ncatalog](/service-catalog/docs/assign-solutions#remove_solution_from_catalog).\n\nBefore you begin\n----------------\n\n- You must have the following\n [Identity and Access Management (IAM) roles](/iam/docs/understanding-roles):\n\n - [Catalog Admin](/service-catalog/docs/access-control#instance_admin_role) *OR* [Catalog Manager](/service-catalog/docs/access-control#catalog_manager_role) for the Google Cloud organization associated with the Google Cloud project which has Service Catalog enabled. If you don't have this role, contact your Organization Administrator to request access.\n - [Storage Admin](/iam/docs/understanding-roles#cloud-storage-roles) for the Google Cloud project where you want to create your solution. If your Terraform config is in a different project, you must also have the Storage Admin role for the project that contains your Terraform config.\n - [Cloud Build Editor](/build/docs/iam-roles-permissions#predefined_roles) for the Google Cloud project where you want to create the solution.\n\n If you plan to use your own service account, you must also have the\n [Service Account User](/iam/docs/understanding-roles#service-accounts-roles)\n role for the Google Cloud project that contains the service account that you\n plan to use.\n\n If you don't have these roles, contact your Organization Administrator to\n request access.\n- If you plan to use your own service account, your service account must have\n the following [IAM roles](/iam/docs/understanding-roles):\n\n - [Storage Admin](/iam/docs/understanding-roles#cloud-storage-roles) for the Google Cloud project where you want to create your solution. If your Terraform config is in a different project, your service account must also have the role [Storage Object Viewer](/iam/docs/understanding-roles#cloud-storage-roles) for the project containing the Terraform config.\n - [Logs Writer](/iam/docs/understanding-roles#logging-roles) for the Google Cloud project where you want to create your solution.\n\n If you don't have these roles, contact your Organization Administrator to\n request access.\n\nUpdate a solution\n-----------------\n\nWhen you edit a solution in Service Catalog, you immediately update\nthe solution in any catalogs where it's assigned. Updating a solution doesn't\naffect existing deployments, and users who access the solution after you update\nit can only deploy the latest version.\n\nFor Terraform solutions, if you update the configuration, a new version appears\nto users on the user's **Deployments** page in the Google Cloud console. Users can\nchoose to update their deployment to the latest version.\n\nEdit solution details\n---------------------\n\nTo edit and update a solution:\n\n1. Go to the Service Catalog Admin [**Solutions** page](https://console.cloud.google.com/project/_/catalog/admin/solutions) in the Google Cloud console. \n [Go to the Solutions page](https://console.cloud.google.com/project/_/catalog/admin/solutions)\n2. Click **Select** to choose the Google Cloud project.\n3. In the list of solutions, click the solution name to open the **Solutions\n Details** page.\n4. In the top menu, click **EDIT**.\n5. Make any needed updates to the solution.\n6. Optionally, you can provide your own service account by clicking the\n checkbox next to **Select or enter your own service account** . If your\n service account is located in the same Google Cloud project where you're\n creating your solution, select\n **Select a service account from the current project** , and select your\n service account from the drop-down menu. If your service account is located\n in a different Google Cloud project from your solution, select\n **Enter a service account email from any project**, and enter the email of\n your service account.\n\n | **Note:** If you don't provide your own service account, Service Catalog uses the default Cloud Build service account settings. For more information, see [Cloud Build Service Account Change](/build/docs/cloud-build-service-account-updates).\n7. Click **UPDATE**.\n\nThe updated solution details now appear on the **Solutions Details** page.\n\nUpdate a Terraform configuration\n--------------------------------\n\nTerraform solutions use Cloud Storage's [Object Versioning](/storage/docs/object-versioning)\nto manage updates to configuration files. To update the configuration file of a\nTerraform solution, you have the following options:\n\n- Use a different Cloud Storage object that contains a new configuration\n file. To change the Cloud Storage object for a solution, [edit the\n solution details](#edit_solution_details) and update the\n **Link to Terraform config** with the URL path to the new object. After you\n update the solution details, users can immediately deploy the latest version.\n\n- Update the solution's current Cloud Storage object with a new\n version of the configuration. For steps to upload a new configuration file,\n visit [Uploading objects](/storage/docs/uploading-objects). After you update\n the solution's Cloud Storage object, you must also [view and apply the\n changes](#apply_version) to the solution in Service Catalog.\n\n### View and apply a newer version of a configuration\n\nWhen Service Catalog detects changes to a Terraform configuration file,\nyou must apply the latest version to update the solution for your users.\n\nTo view and apply the latest version of a Terraform configuration:\n\n1. Go to the Service Catalog Admin **Solutions** page in the\n Google Cloud console.\n\n [Go to the Solutions page](https://console.cloud.google.com/project/_/catalog/admin/solutions)\n\n2. In the table of solutions, go to the solution's **Version status** and click\n **New version available**.\n\n3. On the **Solutions Details** page, click **Compare versions** to download and\n compare the current and latest version of the configuration. After you\n compare versions, click **Close** to return to the **Solution Details** page.\n\n4. Click **Apply newer version**.\n\n5. Under **New version highlights**, add a description to tell users about the\n updates to the configuration.\n\n6. Optionally, you can provide your own service account by clicking the checkbox\n next to **Select or enter your own service account** . If your service account\n is located in the same Google Cloud project where you're creating your\n solution, select **Select a service account from the current project** , and\n select your service account from the drop-down menu. If your service account\n is located in a different Google Cloud project from your solution, select\n **Enter a service account email from any project**, and enter the email of\n your service account.\n\n | **Note:** If you don't provide your own service account, Service Catalog uses the default Cloud Build service account settings. For more information, see [Cloud Build Service Account Change](/build/docs/cloud-build-service-account-updates).\n7. Click **Update**.\n\nDelete solutions from Service Catalog\n-------------------------------------\n\nWhen you delete a solution, you remove the solution from any associated catalogs,\nand your Service Catalog users can no longer view or launch the solution. For Deployment Manager-based solutions, users can continue to access\nand use their existing deployments.\n\nIf you prefer to keep the solution in Service Catalog, you can [remove the\nsolution from a catalog](/service-catalog/docs/assign-solutions#remove_solution_from_catalog).\n\nTo delete one or more solutions:\n\n1. Go to the Service Catalog Admin **Solutions** page in the Google Cloud console. \n [Go to the Solutions page](https://console.cloud.google.com/project/_/catalog/admin/solutions)\n2. Click **Select** to choose the Google Cloud project.\n3. In the list of solutions, check the box next to each solution you want to delete.\n4. With the solution(s) selected, in the top menu, click **DELETE**.\n5. Click **CONFIRM**.\n\nThe solution(s) are deleted from Service Catalog.\n\nNext steps\n----------\n\n- [Assign the solution to a catalog](/service-catalog/docs/assign-solutions)."]]