Update Bucket
Updates the properties and settings of a Google Cloud Storage bucket.
Common Properties
- Name - The custom name of the node.
- Color - The custom color of the node.
- Delay Before (sec) - Waits in seconds before executing the node.
- Delay After (sec) - Waits in seconds after executing node.
- Continue On Error - Automation will continue regardless of any error. The default value is false.
info
If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.
Inputs
- GCS Client Id - The client identifier obtained from the Connect node.
- Bucket Name - The name of the bucket to update.
- Label Name - The name of a label to add or update on the bucket.
- Label Value - The value for the label being added or updated.
Options
- Storage Class - The storage class for the bucket:
- Standard - For frequently accessed data
- Nearline - For data accessed less than once per month
- Coldline - For data accessed less than once per quarter
- Archive - For data accessed less than once per year
- Enable Versioning - Whether to enable or disable object versioning:
- True - Enable versioning to keep multiple versions of objects
- False - Disable versioning
How It Works
The Update Bucket node modifies the properties and settings of a Google Cloud Storage bucket. When executed, the node:
- Validates the provided inputs (GCS Client Id, Bucket Name)
- Uses the existing storage client connection
- Updates the bucket's storage class if specified
- Enables or disables versioning if specified
- Adds or updates labels if label name and value are provided
Requirements
- A valid GCS Client Id from a successful Connect node execution
- Valid bucket name that exists in Google Cloud Storage
- Proper permissions to modify bucket properties
Error Handling
The node will return specific errors in the following cases:
- Empty or invalid GCS Client Id
- Empty or invalid Bucket Name
- Bucket does not exist
- Invalid storage class value
- Insufficient permissions to modify the bucket
- Google Cloud Storage service errors
Usage Notes
- Storage class changes may affect pricing and data retrieval performance
- Enabling versioning helps protect against accidental deletion but increases storage costs
- Labels can be used for cost allocation and organization
- Multiple properties can be updated in a single execution
- Some bucket properties cannot be changed after creation (such as location)
- Make sure the authenticated account has the necessary permissions to modify buckets
- Storage class changes may take some time to propagate
- Label updates replace existing labels with the same name