This is not true, as we use only use access key id during the creation of
s3 bucket to generate volume name from accessKeyID.
For other requests like create/list/read key, the flow is
1. GetVolumeName(Bucket)
2.GetVolume(GetVolumeName(Bucket))
3.GetBucket
Got it, thanks to explain it. It's more confusing than I thought :-(
Even if a volume is defined for an ACCESS_KEY_ID, it's not guaranteed to
be the volume for a specific bucket (as it's used only to __create__ the
buckets).
What do you think about defining the volume name for the ACCESS_KEY_ID
as the current namespace/context. Remove the mapping table at all and
always use the actual volume during **any* operation? (similar to the
kubernetes current context...)
I rewrote the document and added 4 options (unfortunately all of them
are painful...), including this one.
https://hackmd.io/uqSYkmd8SXGAAjQx3sObQg?both
Can you please add if you have more (and add pro/con to any of them if
you see...)
Thanks a lot,
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
