GCS Registry FeatureStore #5335

Hi, I'm starting to deploy the Feast Operator to use its FeatureStore CRD on GKE. I've connected it to my GitHub repo, and here’s the feature_store.yaml I'm using:

project: test
registry: 
  path: gs://feast-test-data/registry.pb
provider: gcp

I setup CI/CD and checked registry.pb exist in that bucket. However, it seems like my FeatureStore resource isn’t picking it up correctly. When I run kubectl exec and cat feature_store.yaml, I see this:

...
registry:
    path: /feast-data/registry.db
    registry_type: file
...

I thought we no longer needed to explicitly define the registry in FeatureStore (assuming it's handled from feature_store.yaml)? I’m confused because when I run kubectl explain, I get the following:

k explain featurestore.spec.services.registry.local.persistence.store
GROUP:      feast.dev
KIND:       FeatureStore
VERSION:    v1alpha1

FIELD: store <Object>

DESCRIPTION:
  RegistryDBStorePersistence configures the DB store persistence for the
  registry service

FIELDS:
  secretKeyName <string>
    By default, the selected store "type" is used as the SecretKeyName

  secretRef     <Object> -required-
    Data store parameters should be placed as-is from the "feature_store.yaml"
    under the secret key.

  type  <string> -required-
  enum: sql, snowflake.registry
    Type of the persistence type you want to use.

It looks like the type only supports sql and snowflake.registry? Does that mean GCS-based registry paths like gs://... aren't supported directly here?