b2sdk._internal.exception.BadRequest: Rule with prefix '' must have at least one additional property defined (bad_request)

[cinemast]

While trying to change the CORS rules in one of our buckets, we receive the following error:

 # b2_bucket.media_bucket will be updated in-place
  ~ resource "b2_bucket" "media_bucket" {
        id          = "<redacted>"
        # (7 unchanged attributes hidden)

      ~ cors_rules {
          ~ allowed_origins    = [
                # (1 unchanged element hidden)
                "http://localhost:5173",
              + "https://localhost:5173",
                "http://localhost:4173",
              + "https://localhost:4173",
            ]
            # (5 unchanged attributes hidden)
        }

        # (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions in workspace "test"?
  OpenTofu will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

b2_bucket.media_bucket: Modifying... [id=<redacted>]
╷
│ Error: Traceback (most recent call last):
│   File "b2_terraform/provider_tool.py", line 606, in run_command
│   File "b2_terraform/provider_tool.py", line 132, in run
│   File "b2_terraform/provider_tool.py", line 281, in resource_update
│   File "b2sdk/_internal/session.py", line 329, in update_bucket
│   File "b2sdk/_internal/session.py", line 451, in _wrap_default_token
│   File "b2sdk/_internal/session.py", line 457, in _wrap_token
│   File "b2sdk/_internal/session.py", line 472, in _reauthorization_loop
│   File "b2sdk/_internal/session.py", line 462, in _api_token_callback
│   File "b2sdk/_internal/raw_api.py", line 917, in update_bucket
│   File "b2sdk/_internal/raw_api.py", line 546, in _post_json
│   File "b2sdk/_internal/b2http.py", line 390, in post_json_return_json
│   File "b2sdk/_internal/b2http.py", line 356, in post_content_return_json
│   File "b2sdk/_internal/b2http.py", line 309, in request_content_return_json
│   File "b2sdk/_internal/b2http.py", line 279, in request
│   File "b2sdk/_internal/b2http.py", line 588, in _translate_and_retry
│   File "b2sdk/v2/b2http.py", line 22, in _translate_errors
│   File "b2sdk/_internal/b2http.py", line 520, in _translate_errors
│ b2sdk._internal.exception.BadRequest: Rule with prefix '' must have at least one additional property defined (bad_request)
│
│
│   with b2_bucket.media_bucket,
│   on main.tf line 87, in resource "b2_bucket" "media_bucket":
│   87: resource "b2_bucket" "media_bucket" {
│
╵

[mlech-reef]

@cinemast it looks more like a problem with lifecycle_rules. Do you use it in your bucket? Could you post an entire resource and also terraform and B2 provider versions?

[cinemast]

resource "b2_bucket" "media_bucket" {
  bucket_name = "xxx-${terraform.workspace}"
  bucket_type = "allPrivate"
  cors_rules {
    allowed_operations = ["s3_put", "s3_head", "s3_get"]
    allowed_origins    = ["https://app.${local.group_vars.domain}", "http://localhost:5173", "http://localhost:4173"]
    cors_rule_name     = "xxx-cors-${terraform.workspace}"
    max_age_seconds    = 60
  }

  lifecycle_rules {
    file_name_prefix              = ""
    days_from_hiding_to_deleting  = null
    days_from_uploading_to_hiding = null
  }

  lifecycle_rules {
    file_name_prefix              = "healthcheck"
    days_from_hiding_to_deleting  = null
    days_from_uploading_to_hiding = null
  }
}

[mlech-reef]

According to the docs [1]:

You cannot set all three daysFrom parameters to unspecific or null.

In this case, two days_from_ parameters, as this provider doesn't support daysFromStartingToCancelingUnfinishedLargeFiles yet.

[1] https://www.backblaze.com/docs/cloud-storage-lifecycle-rules

[cinemast]

Hm, I don't quite understand. What I was trying to achieve is to not keep any version at all. We write to /healthcheck to see if our upload is working. However this creates a lot of versions, which we would like to avoid.

Can you help me out here?

[metadaddy]

Hi @cinemast - all Backblaze B2 buckets are versioned, but you can configure B2 to keep only the most recent version.

The settings you need for this are:

  lifecycle_rules {
    file_name_prefix              = "healthcheck"
    days_from_uploading_to_hiding = null
    days_from_hiding_to_deleting  = 1
  }

This will cause soft-deleted ('hidden') files to be hard-deleted after one day.

If you want files with the healthcheck prefix to automatically be deleted as quickly as possible, rather than in response to delete operation, you can do:

  lifecycle_rules {
    file_name_prefix              = "healthcheck"
    days_from_uploading_to_hiding = 1
    days_from_hiding_to_deleting  = 1
  }

Note that you cannot set either of the days_from_ parameters to 0. 1 is the minimum. Note also that there are restrictions that apply to overlapping prefixes - see https://www.backblaze.com/docs/cloud-storage-lifecycle-rules

There are two ways to hard-delete files faster than this

• Use a tool that is "version-aware" and configure it to perform an explicit hard-delete rather than the default soft-delete
• Hard-delete hidden file versions manually

[cinemast]

Thank you!