You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the documentation does a good job in explaining, by giving examples, how to set S3 config options using the juju config s3-integrator bucket=.... on the provider side. But, there's an option to pass the bucket name from the requirer side. I think it would be very useful to add to the charm documentation the below points to cover:
1- How to set bucket names from requirer side? When to use that? What'd happen if we set both the provider and the requirer side?
2- How should the s3-integrator be deployed in a cluster where multiple charms want to use the s3 integrator with different bucket names/config? Should it be a one S3 integrator per charm or could we integrate all charms to one s3 integrator app?
3- What are some of the added benefits of using s3-integrator instead of relating a charm directly to an s3-like charm?
Actual behavior
N/A
Versions
N/A
Log output
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
michaeldmitry
changed the title
[Enhancement Proposal] Add more documentation on other ways to use S3 integrator
[Enhancement Proposal] Add more documentation on how to use S3 integrator
Sep 6, 2024
michaeldmitry
changed the title
[Enhancement Proposal] Add more documentation on how to use S3 integrator
[Enhancement Proposal] Add more documentation
Sep 6, 2024
Steps to reproduce
Expected behavior
I think the documentation does a good job in explaining, by giving examples, how to set S3 config options using the
juju config s3-integrator bucket=....
on the provider side. But, there's an option to pass the bucket name from the requirer side. I think it would be very useful to add to the charm documentation the below points to cover:1- How to set bucket names from requirer side? When to use that? What'd happen if we set both the provider and the requirer side?
2- How should the s3-integrator be deployed in a cluster where multiple charms want to use the s3 integrator with different bucket names/config? Should it be a one S3 integrator per charm or could we integrate all charms to one s3 integrator app?
3- What are some of the added benefits of using s3-integrator instead of relating a charm directly to an s3-like charm?
Actual behavior
N/A
Versions
N/A
Log output
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: