copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2023-01-20 |
catalog, private catalog, update, private catalog product, update version, versions |
account |
{{site.data.keyword.attribute-definition-list}}
{: #update-private}
To update the software that's in your private catalog, you can add a new version or update and republish an existing version. {: shortdesc}
{: #prereq-update}
To complete this task, you need to be assigned the editor role on the catalog management service. For more information, see Assigning users access.
To update your software by using Terraform, make sure that you have completed the following: {: terraform}
- Install the Terraform CLI and configure the {{site.data.keyword.cloud_notm}} Provider plug-in for Terraform. For more information, see the tutorial for Getting started with Terraform on {{site.data.keyword.cloud}}. The plug-in abstracts the {{site.data.keyword.cloud_notm}} APIs that are used to complete this task.
- Create a Terraform configuration file that is named
main.tf
. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the Terraform documentation{: external}. {: terraform}
{: #update-editor-offering} {: ui}
The following steps walk through an example of making updates to a product's readme file to show the complete process for updating an existing software version.
- In the {{site.data.keyword.cloud}} console, go to Manage > Catalogs > Private catalogs, and select your catalog from the list.
- Click the name of your software product.
- Select Private products to navigate to the list of products that are in your private catalog.
- Click the Actions icon , and select Edit.
- Click the Edit readme tab.
- Click the Edit icon , add a new line of text to the Introduction section, and click Update.
- Click the Actions icon , and select Merge changes to publish the updated version to your account.
{: #update-version-cli} {: cli}
Complete the following steps to create a draft version, update it, and merge the changes to the current version of your software.
You need the version locator for your software. To find it, run the ibmcloud catalog offering list --catalog "your-private-catalog"
command and search for the existing version number.
{: important}
-
Create a draft version of your software.
ibmcloud catalog offering create-draft --version-locator <VERSION_LOCATOR>
{: codeblock}
-
Set another category.
ibmcloud catalog offering add-category --catalog "your-private-catalog" --offering "your-software" --category "category-type"
{: codeblock}
-
Merge the draft update to your software. This action merges the update to the version of your software that's published in your account.
ibmcloud catalog offering merge-draft --version-locator **<VERSION_LOCATOR_OF_DRAFT_VERSION>**
{: codeblock}
-
Search for the software in the {{site.data.keyword.cloud_notm}} catalog.
ibmcloud catalog get --public | grep your-software
{: codeblock}
{: #update-version-api} {: api}
You can programmatically update a version by calling the Catalog Management API as shown in the following sample request. For detailed information about the API, see Catalog Management API{: external}.
String catalogID = "{catalogID}";
String offeringID = "{offeringID}";
String label = "{label}";
String shortDesc = "{shortDesc}";
ReplaceOfferingOptions replaceOptions = new ReplaceOfferingOptions.Builder().catalogIdentifier(catalogID).id(offeringID).offeringId(offeringID).label(label).shortDescription(shortDesc).rev(revision.rev()).build();
Response<Catalog> response = service.replaceOffering(replaceOptions).execute();
System.out.println(response.getResult());
{: codeblock} {: java}
vcatalogID = "{catalogID}";
offeringID = "{offeringID}";
revision = "{revision}";
label = "{label}";
shortDesc = "{shortDesc}";
response = await service.replaceOffering({'catalogIdentifier': catalogID, 'offeringId': offeringID, 'id': offeringID, 'rev': revision, 'label': label, 'shortDescription': shortDesc});
console.log(response);
{: codeblock} {: javascript}
catalogID = "{catalogID}"
offeringID = "{offeringID}"
revision = "{revision}"
shortDesc = "{shortDesc}"
response = self.service.replace_offering(catalog_identifier=catalogID, offering_id=offeringID, id=offeringID, rev=revision, label=label, short_description=shortDesc)
print(response)
{: codeblock} {: python}
catalogID := "{catalogID}"
offeringID := "{offeringID}"
label := "{label}"
shortDesc := "{shortDesc}"
revision := "{revision}"
updateOptions := service.NewReplaceOfferingOptions(catalogID, offeringID)
updateOptions.SetID(offeringID)
updateOptions.SetLabel(label)
updateOptions.SetShortDescription(shortDesc)
updateOptions.SetRev(revision)
_, response, _ := service.ReplaceOffering(updateOptions)
fmt.Println(response)
{: codeblock} {: go}
{: #update-editor-terraform} {: terraform}
Use the following steps to update an existing version of your software by using Terraform.
-
Create an argument in your
main.tf
file. The following example accesses the software version by using thecm_version
resource, whereoffering_id
identifies the software.resource "cm_version" "cm_version" { catalog_identifier = "catalog_identifier" offering_id = "offering_id" zipurl = "zipurl" }
{: codeblock}
For more information, see the argument reference details on the Terraform Catalog Management{: external} page.
-
After you finish building your configuration file, initialize the Terraform CLI. For more information, see Initializing Working Directories{: external}.
terraform init
{: pre}
-
Provision the resources from the
main.tf
file. For more information, see Provisioning Infrastructure with Terraform{: external}.-
Run
terraform plan
to generate a Terraform execution plan to preview the proposed actions.terraform plan
{: pre}
-
Run
terraform apply
to create the resources that are defined in the plan.terraform apply
{: pre}
-