Context
Right now the secret-key config value of MinIO has a "" value as default. This then means that MinIO will create a random big password and use this value for the secret-key
https://github.com/canonical/minio-operator/blob/track/ckf-1.8/src/charm.py#L219-L234
Users should have a way in this case to be able to see the secret-key value that was autogenerated by the Charm.
Not that this change is only focused on the "interface" (actions) that users can use to get the value of secret-key. This could go hand in hand with #167, but can be a separate effort as well.
What needs to get done
- Have an action that returns the value of the
secret-key that MinIO will have, which is either
2. The value of the config
3. The value that MinIO generated
Definition of Done
- Ensure the action returns the value, whether it was generated or not
Context
Right now the
secret-keyconfig value of MinIO has a""value as default. This then means that MinIO will create a random big password and use this value for thesecret-keyhttps://github.com/canonical/minio-operator/blob/track/ckf-1.8/src/charm.py#L219-L234
Users should have a way in this case to be able to see the
secret-keyvalue that was autogenerated by the Charm.Not that this change is only focused on the "interface" (actions) that users can use to get the value of
secret-key. This could go hand in hand with #167, but can be a separate effort as well.What needs to get done
secret-keythat MinIO will have, which is either2. The value of the config
3. The value that MinIO generated
Definition of Done