Tags on Fabric pool in GCP about terraform-provider-netapp-cloudmanager HOT 1 OPEN

Question 1: Can we tag on Fabric Pool via Terraform?

As of my last update, Terraform's NetApp Cloud Manager provider does not explicitly support tagging Google Cloud Storage buckets used as Fabric Pools directly through the Terraform configuration for CVO deployments. Fabric Pools are utilized within NetApp CVO to tier cold data to Google Cloud Storage, but the management of tags directly through Terraform for these specific resources isn't provided out-of-the-box.

Question 2: Can we tag on Google Cloud Storage manually?

Yes, you can apply tags manually to Google Cloud Storage buckets through the Google Cloud Console or using the gcloud command-line tool.

These tags (also referred to as labels in GCP) can help you with cost allocation and management.
To add a label to a Google Cloud Storage bucket, you can use the following gcloud command:

gcloud storage buckets update [BUCKET_NAME] --update-labels=[KEY]=[VALUE]

Replace [BUCKET_NAME], [KEY], and [VALUE] with your bucket's name and the label key-value pair you wish to apply.

Question 3: If we tag on Google Cloud Storage manually, does it affect the system or Terraform code?

Tagging Google Cloud Storage buckets manually does not directly affect the operation of the system or the Terraform code used to deploy NetApp CVO. However, you should be aware of a few considerations:

State Management: Terraform manages state based on the configuration files and the resources it creates. If you manually add tags to a bucket that Terraform is managing (like those associated with a Fabric Pool), Terraform won’t recognize these changes unless they are imported into its state or reflected in the Terraform configuration. (I need to try in my GCP PoC)
Configuration Drift: Manual changes can lead to configuration drift (As we know ), where the actual state of the environment differs from the state known to Terraform. This can be problematic if Terraform attempts to manage or reconfigure those resources later.

For Best Practice:

If you decide to manually tag resources managed by Terraform, it’s a good practice to consistently manage these tags outside of Terraform to prevent potential configuration conflicts or drift.

from terraform-provider-netapp-cloudmanager.