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