We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have a internal struct now:
type pairServiceNew struct { pairs []Pair // Required pairs HasCredential bool Credential string // Optional pairs HasDefaultServicePairs bool DefaultServicePairs DefaultServicePairs HasDisable100Continue bool Disable100Continue bool HasEndpoint bool Endpoint string HasForcePathStyle bool ForcePathStyle bool HasHTTPClientOptions bool HTTPClientOptions *httpclient.Options HasServiceFeatures bool ServiceFeatures ServiceFeatures HasUseAccelerate bool UseAccelerate bool HasUseArnRegion bool UseArnRegion bool }
Maybe we can export this struct as StorageConfig and implement following methods for it:
StorageConfig
FromPairs(ps Pair...)
NewStorage(ps Pair...)
FromString(conn string)
NewStorageFromString(conn string)
We need the following changes:
NewStorageFromConfig(cfg StorageConfig)
HasUseAccelerate
hasUseAccelerate
FromPairs
FromString
The text was updated successfully, but these errors were encountered:
Moved to https://forum.beyondstorage.io/t/idea-about-servicer-storager-init-logic/185
Sorry, something went wrong.
No branches or pull requests
We have a internal struct now:
Maybe we can export this struct as
StorageConfig
and implement following methods for it:FromPairs(ps Pair...)
-> parse from pairs, just likeNewStorage(ps Pair...)
FromString(conn string)
-> parse from connection string, just likeNewStorageFromString(conn string)
We need the following changes:
NewStorageFromConfig(cfg StorageConfig)
?HasUseAccelerate
needs to be converted to internal ->hasUseAccelerate
?StorageConfig
?FromPairs
,FromString
so that we can register it?The text was updated successfully, but these errors were encountered: