Legacy Configuration¶

Configuring an S3 object store connection¶

The legacy method of configuring an object store connection is by creating a top level s3 section in a configuration file such as s3_custom.yaml. This is still supported and will continue to work as is. This requires that under the object_store section the value of type is set to detect.

object_store:
  type: detect

This is the default after install or upgrade.

Migrating to new configuration¶

Before migrating to the new configuration, create a backup copy of any s3 configuration files under [etc directory]/config.d.

For each file containing a top level s3 section, rename the section to object_store. Make sure the names of these files are lexicographically greater than object_store.yaml. One of the files should set the value of type under object_store to s3. The remaining configuration can be left unchanged.

For example the following configuration

s3:
  endpoint: <URL endpoint>
  accessKeyId: <access key>
  secretAccessKey: <secret key>

becomes

object_store:
  type: s3
  endpoint: <URL endpoint>
  accessKeyId: <access key>
  secretAccessKey: <secret key>

Verification¶

Verify Object Store

run the hubctl verify objectstore command

If keeping the legacy configuration or having migrated it, it is necessary to verify that the connection information for the object store is correct. To do this, use the following hubctl command:

hubctl verify objectstore