Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DPE-3325] Dynamically adding Peer Data Secrets (groped on-demand) #135

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

juditnovak
Copy link
Contributor

@juditnovak juditnovak commented Jan 28, 2024

Most charms use a single secret on app, and another one on unit level. Therefore this was the functionality provided by the DataPeer and the DataPeerUnit interfaces.

This change is extending that behavior to what is only used by a few charms (Opensearch, Pgbouncer) allowing for multiple secrets on either level. The implemetation goes in a way, that new secret fields can also form new groups or be saved into an individual secret labelled after the key.

@juditnovak juditnovak force-pushed the DPE-3325_multi_secrets_dynamic_update branch 5 times, most recently from 514b74e to 876f7ba Compare January 29, 2024 00:22
@juditnovak juditnovak force-pushed the DPE-3325_multi_secrets_dynamic_update branch from ac43cce to 8c17173 Compare January 29, 2024 02:43
@juditnovak juditnovak force-pushed the DPE-3325_multi_secrets_dynamic_update branch from 8c17173 to f500c1a Compare January 29, 2024 23:22
@juditnovak juditnovak force-pushed the DPE-3325_multi_secrets_dynamic_update branch from f500c1a to f467156 Compare January 29, 2024 23:46
@juditnovak juditnovak marked this pull request as ready for review January 30, 2024 00:27
@juditnovak juditnovak changed the title [DPE-3325] Secret groups extendible [DPE-3325] Dynamically adding Peer Data Secrets (groped on-demand) Jan 30, 2024
Copy link
Member

@delgod delgod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need good case for absolutely dynamic secret allocation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants