Il 15 settembre 2026, tutti gli ambienti Cloud Composer 1 e Cloud Composer 2 versione 2.0.x raggiungeranno la fine del ciclo di vita pianificata e non potrai più utilizzarli. Ti consigliamo di pianificare la migrazione a Cloud Composer 3.
Questa pagina spiega come assegnare etichette agli ambienti Cloud Composer e poi suddividere i costi di fatturazione in base a queste etichette.
Informazioni sulle etichette dell'ambiente
Le etichette di ambiente sono coppie chiave-valore che puoi assegnare ai tuoi
ambienti. Ad esempio, se owner:engineering-team è un'etichetta personalizzata, allora
owner è la chiave e engineering-team è il valore.
Ogni ambiente può avere più etichette, ma le chiavi delle etichette per un singolo
ambiente devono essere univoche. Puoi assegnare la stessa chiave e lo stesso valore a più
ambienti.
Etichette dell'ambiente nei report sulla fatturazione
Le etichette dell'ambiente che assegni ai tuoi ambienti sono visibili nei report di fatturazione, in modo da poter suddividere i costi in base sia alle chiavi sia ai valori delle etichette.
Le etichette non vengono applicate in modo retroattivo. Ad esempio, se assegni un'etichetta il
15 maggio, i costi di fatturazione del 14 maggio non contengono l'etichetta assegnata.
Assegnare etichette ai nuovi ambienti
Puoi assegnare etichette quando crei un ambiente. Per saperne di più,
vedi Creazione di ambienti.
Assegnare etichette agli ambienti esistenti
Console
Vai alla pagina Ambienti nella console Google Cloud :
Per rimuovere tutte le etichette, includi labels nel parametro di ricerca updateMask
e non fornire il valore di sostituzione.
Aggiornare singole etichette
Per aggiornare un'etichetta o aggiungerne una nuova a quelle esistenti, includi
labels.LABEL_KEY nel parametro di query updateMask e fornisci una
sostituzione nel corpo della richiesta.
Per rimuovere le etichette, includi labels.LABEL_KEY nel parametro di query updateMask e non fornire il valore di sostituzione.
Terraform
Per creare un ambiente con parametri predefiniti in una posizione specificata, modifica il blocco labels nella configurazione Terraform ed esegui terraform apply.
resource "google_composer_environment" "example" {
name = "example-environment"
region = "us-central1"
labels = {
LABEL_KEY = "LABEL_VALUE"
}
}
Sostituisci:
LABEL_KEY con la chiave dell'etichetta dell'ambiente che vuoi creare o
aggiornare. Per rimuovere le etichette, elimina i relativi campi.
LABEL_VALUE con il valore dell'etichetta dell'ambiente.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-03 UTC."],[[["\u003cp\u003eEnvironment labels are key-value pairs you can assign to Cloud Composer environments to organize and track resources, such as \u003ccode\u003eowner:engineering-team\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThese labels can be used in billing reports to break down costs based on the assigned label keys and values, allowing for detailed cost analysis.\u003c/p\u003e\n"],["\u003cp\u003eLabels can be assigned to both new and existing environments through the Google Cloud console, \u003ccode\u003egcloud\u003c/code\u003e command-line tool, API, and Terraform.\u003c/p\u003e\n"],["\u003cp\u003eWhen using \u003ccode\u003egcloud\u003c/code\u003e, labels can be cleared, updated, or removed by using the arguments \u003ccode\u003e--clear-labels\u003c/code\u003e, \u003ccode\u003e--update-labels\u003c/code\u003e, and \u003ccode\u003e--remove-labels\u003c/code\u003e, respectively, which are applied in that order if used together.\u003c/p\u003e\n"],["\u003cp\u003eChanges to labels are not retroactive in billing reports, and it may take up to one day for label assignments to be reflected in these reports.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\n[Cloud Composer 3](/composer/docs/composer-3/manage-environment-labels \"View this page for Cloud Composer 3\") \\| [Cloud Composer 2](/composer/docs/composer-2/manage-environment-labels \"View this page for Cloud Composer 2\") \\| **Cloud Composer 1**\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page explains how to assign labels to your Cloud Composer environments and then break down billing costs based on these labels.\n\nAbout environment labels\n\nEnvironment labels are key-value pairs that you can assign to your\nenvironments. For example, if `owner:engineering-team` is a custom label, then\n`owner` is the key, and `engineering-team` is the value.\n\nEach environment can have multiple labels, but the label keys for a single\nenvironment must be unique. You can assign a same key and value to several\nenvironments.\n\nEnvironment labels in billing reports\n\nEnvironment labels that you assign to your environments are visible in billing\nreports, so you can break down costs based on both keys and values from the\nlabels.\n| **Important:** It might take **up to 1 day** for environment labels to propagate to billing reports. However, the billing costs are labeled starting from the moment when you assigned the label to your environment.\n\nLabels don't apply retroactively. For example, if you assign a label on\nMay 15, billing costs for May 14 do not contain the assigned label.\n\nAssign labels to new environments\n\nYou can assign labels when you create an environment. For more information,\nsee [Creating environments](/composer/docs/composer-1/create-environments#labels).\n\nAssign labels to existing environments \n\nConsole\n\n1. Go to the **Environments** page in the Google Cloud console:\n\n [Go to Environments](https://console.cloud.google.com/composer/environments)\n2. Select your environment.\n\n3. Go to the **Labels** tab.\n\n4. Click **Edit** , then click **Add label**.\n\n5. Add a key-value pair for the label, then click **Save**.\n\n6. Wait until the environment updates.\n\ngcloud\n\nWhen you update an environment using\nthe [`gcloud composer`](/sdk/gcloud/reference/composer/environments/update) command, the following arguments\nspecify labels for the environment:\n\n- `--clear-labels` removes all labels.\n\n- `--update-labels` updates specified labels; creates new labels if they\n don't already exist.\n\n- `--remove-labels` removes specified labels; specified label that do not\n exist are ignored.\n\nIf you use several of these arguments, they are applied in the following\norder: `--clear-labels`, `--update-labels`, `--remove-labels`.\n\n**Update or create labels** \n\n gcloud composer environments update \u003cvar translate=\"no\"\u003eENVIRONMENT_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e \\\n --update-labels \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-nv\"\u003eLABEL_KEY\u003c/span\u003e\u003c/var\u003e=\u003cvar translate=\"no\"\u003eLABEL_VALUE\u003c/var\u003e\n\n**Remove specified labels** \n\n gcloud composer environments update \u003cvar translate=\"no\"\u003eENVIRONMENT_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e \\\n --remove-labels \u003cvar translate=\"no\"\u003eLABEL_KEY\u003c/var\u003e\n\n**Remove all labels** \n\n gcloud composer environments update \u003cvar translate=\"no\"\u003eENVIRONMENT_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e \\\n --clear-labels\n\nReplace:\n\n- `ENVIRONMENT_NAME` with the name of the environment.\n- `LOCATION` with the region where the environment is located.\n- `LABEL_KEY` with the environment label key that you want to create, update, or remove.\n- `LABEL_VALUE` with the environment label value.\n\n**Example**\n\nThe following example updates the `owner` label, creates the new `env`\nlabel, and removes the `misc` label: \n\n gcloud composer environments update example-environment \\\n --location us-central1 \\\n --update-labels owner=engineering-team,env=production \\\n --remove-labels misc\n\nAPI\n\nWhen you update an environment, in the [Environment](/composer/docs/reference/rest/v1/projects.locations.environments#Environment)\nresource, specify new labels of your environment.\n\n**Replace all labels**\n\nTo replace all labels, include `labels` in the `updateMask` query parameter\nand provide a replacement in the request body. \n\n // PATCH https://composer.googleapis.com/v1/\n // ?{name=projects/*/locations/*/environments/*}\n // &updateMask.fieldPaths=labels\n\n {\n \"labels\":{\n \"\u003cvar translate=\"no\"\u003eLABEL_KEY\u003c/var\u003e\": \"\u003cvar translate=\"no\"\u003eLABEL_VALUE\u003c/var\u003e\"\n }\n }\n\nReplace:\n\n- `LABEL_KEY` with a key of the environment label.\n- `LABEL_VALUE` with a new value for the environment label.\n\nExample: \n\n // PATCH https://composer.googleapis.com/v1/\n // ?{name=projects/*/locations/*/environments/*}\n // &updateMask.fieldPaths=labels\n\n {\n \"labels\": {\n \"owner\": \"engineering-team\",\n \"env\": \"production\"\n }\n }\n\n**Remove all labels**\n\nTo remove all labels, include `labels` in the `updateMask` query parameter\nand do not provide the replacement value.\n\n**Update individual labels**\n\nTo update a label or add a new label to existing labels, include\n`labels.LABEL_KEY` in the `updateMask` query parameter and provide a\nreplacement in the request body. \n\n // PATCH https://composer.googleapis.com/v1/\n // ?{name=projects/*/locations/*/environments/*}\n // &updateMask=labels.\u003cvar translate=\"no\"\u003eLABEL_KEY\u003c/var\u003e\n\n {\n \"labels\":{\n \"\u003cvar translate=\"no\"\u003eLABEL_KEY\u003c/var\u003e\": \"\u003cvar translate=\"no\"\u003eLABEL_VALUE\u003c/var\u003e\"\n }\n }\n\nReplace:\n\n- `LABEL_KEY` with a key of the environment label.\n- `LABEL_VALUE` with a new value for the environment label.\n\nExample: \n\n // PATCH https://composer.googleapis.com/v1/\n // ?name=projects/example-project/locations/\n // us-central1/environments/example-environment\n // &updateMask=labels.owner,labels.env\n\n {\n \"labels\": {\n \"owner\": \"engineering-team\",\n \"env\": \"production\"\n }\n }\n\n**Remove individual labels**\n\nTo remove labels, include `labels.LABEL_KEY` in the `updateMask` query\nparameter and do not provide the replacement value.\n\nTerraform\n\nTo create an environment with default parameters is a specified location,\nedit the `labels` block in your Terraform configuration and run\n`terraform apply`. \n\n resource \"google_composer_environment\" \"example\" {\n name = \"example-environment\"\n region = \"us-central1\"\n\n labels = {\n \u003cvar translate=\"no\"\u003eLABEL_KEY\u003c/var\u003e = \"\u003cvar translate=\"no\"\u003eLABEL_VALUE\u003c/var\u003e\"\n }\n\n }\n\nReplace:\n\n- `LABEL_KEY` with the environment label key that you want to create or update. To remove labels, delete their fields.\n- `LABEL_VALUE` with the environment label value.\n\nExample: \n\n resource \"google_composer_environment\" \"example\" {\n name = \"example-environment\"\n region = \"us-central1\"\n\n labels = {\n owner = \"engineering-team\"\n env = \"production\"\n }\n }\n\nView labels in reports\n\nAfter the labels for your environment propagate to billing reports, you can break down billing costs based on these labels:\n\n1. [View Cloud Billing reports](/billing/docs/how-to/reports#getting_started) for your\n Cloud Billing account.\n\n2. On the **Reports** page:\n\n 1. Click **Show filters**.\n 2. In the **Filters** dialog, expand the **Labels** section.\n 3. [Filter the displayed data](/billing/docs/how-to/reports#filters) based on keys and values of your environment labels.\n\nWhat's next\n\n- [Cloud Composer pricing](/composer/pricing)"]]