Closed daviderli614 closed 3 days ago
The changes introduce support for Azure Blob storage within the existing object storage framework. This includes the addition of a new AZBlobStorage
struct and corresponding fields and methods in various files. The ObjectStorageProviderSpec
is updated to include an AZBlob
field, while the StorageConfig
struct is enhanced to accommodate Azure Blob storage configuration parameters. Validation logic is also updated to ensure proper credential checks for the new storage type. Constants related to Azure account information are added, and deepcopy methods are implemented for the new struct.
File Path | Change Summary |
---|---|
apis/v1alpha1/common.go | Added AZBlob *AZBlobStorage to ObjectStorageProviderSpec , added GetAZBlobStorage() method, and defined AZBlobStorage struct with Container , SecretName , Root , and Endpoint fields. Added GetSecretName() and GetRoot() methods. |
apis/v1alpha1/constants.go | Added constants AccountName and AccountKey for Azure Blob storage configuration. |
apis/v1alpha1/validate.go | Introduced checkAZBlobCredentialsSecret for validating AZBlobStorage credentials in GreptimeDBCluster and GreptimeDBStandalone . |
apis/v1alpha1/zz_generated.deepcopy.go | Added deepcopy methods for AZBlobStorage and updated DeepCopyInto for ObjectStorageProviderSpec to handle the new AZBlob field. |
pkg/dbconfig/common.go | Enhanced StorageConfig by adding Container , AccountName , and AccountKey fields. Updated ConfigureObjectStorage to handle Azure Blob storage and introduced configureAZBlob method. |
In the land where data flows,
A new storage type now grows.
Azure's Blob, a friend so dear,
With secrets kept, it draws us near.
Containers full, keys in hand,
A hopping change across the land! 🐇🌟
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@daviderli614 It's mostly LGTM. I think we should use azblob
and AZBlob
as part of the naming instead of using blob
directly.
@daviderli614 It's mostly LGTM. I think we should use
azblob
andAZBlob
as part of the naming instead of usingblob
directly.
I changed it to use azblob to define this structure:
objectStorage:
azblob:
container: "greptimedb"
secretName: "azblob-credentials"
endpoint: "https://<storage-account>.blob.core.windows.net"
root: "cluster-with-blob-data"
Released issue: https://github.com/GreptimeTeam/greptimedb-operator/issues/215
Summary by CodeRabbit
New Features
AccountName
andAccountKey
.Bug Fixes
Documentation