Feature: access-key and secret-key as Juju Config instead of action

[mcarvalhor]

Hi everyone,

Currently we need to run sync-s3-credentials action in order to provide the access-key and secret-key to the s3-integrator charm.

This is a feature request to add these as Juju config as well (or instead).
Since Terraform Juju Provider doesn't support actions, this becomes a manual step which cannot be automated.

If it's a Juju config, we can automate it using Terraform Juju Provider and Terraform Openstack Provider.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-5556.

This message was autogenerated

[dragomirp]

Hi, @mcarvalhor, the plan is to switch to a configuration pointing to a secret like in the azure-storage-integrator charm. Would that work for your use case?

[mcarvalhor]

Hi @dragomirp

I think that works! Since Terraform Juju provider supports secrets as well:

• https://registry.terraform.io/providers/juju/juju/latest/docs/resources/secret

[hloeung]

Any updates on this? Thanks.

[taurus-forever]

@deusebio ^^^
Do we have some plans/ETAs we can share about s3-integrator migration to https://github.com/canonical/object-storage-integrators ?

[deusebio]

The design plans are clear, meaning how we want to handle the merge of s3 and azure storage integration, which has been detailed in the spec document DA103 - Object Storage Integrator Charms.

For the implementation unfortunately we don't have any ETA as this was not planned as part of the 24.05 goals. I'm afraid that especially in the first weeks of 2025 there will be very limited room for this, but we'll use mid-cycle to trigger the discussions and figure out a reasonable ETA for this.