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

Add vault caching of secrets on relation test #1084

Merged
merged 1 commit into from Jul 26, 2023
Merged

Conversation

ajkavanagh
Copy link
Contributor

@ajkavanagh ajkavanagh commented Jul 20, 2023

This specific test is for the certificates relation to ensure that the
data presented to units related to vault have a consistent set of data.

Review that tests this change: https://review.opendev.org/c/openstack/charm-vault/+/883947

This specific test is for the certificates relation to ensure that the
data presented to units related to vault have a consistent set of data.
Copy link
Member

@freyes freyes left a comment

Choose a reason for hiding this comment

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

LGTM

@freyes freyes merged commit 8991edd into master Jul 26, 2023
6 checks passed
@freyes freyes deleted the vault-cache-test branch July 26, 2023 21:29
openstack-mirroring pushed a commit to openstack/charm-vault that referenced this pull request Jul 26, 2023
This cache is used to store certificates and keys
issued by the leader unit. Non-leader units read
these certificates and keep data in their
"tls-certificates" relations up to date.
This ensures that charm units that receive certs
from vault can read from relation data of any
vault unit and receive correct data.

This patch is mostly the same as
I18aa6c9193379ea454851b6f60a8f331ef88a980
but improved to avoid LP#1896542 by removing
the section where a certificate can be reused
from cache during create_certs.

Co-Authored-By: Rodrigo Barbieri <rodrigo.barbieri@canonical.com>
Co-Authored-By: Alex Kavanagh <alex.kavanagh@canonical.com>

func-test-pr: openstack-charmers/zaza-openstack-tests#1084

Closes-Bug: #1940549
Closes-Bug: #1983269
Closes-Bug: #1845961
Related-Bug: #1896542
Change-Id: I0cca13d2042d61ffc6a7c13eccb0ec8c292020c9
openstack-mirroring pushed a commit to openstack/openstack that referenced this pull request Jul 26, 2023
* Update charm-vault from branch 'master'
  to 1a1953b0ef23f724e9295505b100eca22ef9a6cd
  - Implement cert cache for vault units (v4)
    
    This cache is used to store certificates and keys
    issued by the leader unit. Non-leader units read
    these certificates and keep data in their
    "tls-certificates" relations up to date.
    This ensures that charm units that receive certs
    from vault can read from relation data of any
    vault unit and receive correct data.
    
    This patch is mostly the same as
    I18aa6c9193379ea454851b6f60a8f331ef88a980
    but improved to avoid LP#1896542 by removing
    the section where a certificate can be reused
    from cache during create_certs.
    
    Co-Authored-By: Rodrigo Barbieri <rodrigo.barbieri@canonical.com>
    Co-Authored-By: Alex Kavanagh <alex.kavanagh@canonical.com>
    
    func-test-pr: openstack-charmers/zaza-openstack-tests#1084
    
    Closes-Bug: #1940549
    Closes-Bug: #1983269
    Closes-Bug: #1845961
    Related-Bug: #1896542
    Change-Id: I0cca13d2042d61ffc6a7c13eccb0ec8c292020c9
@ajkavanagh ajkavanagh changed the title Add vault cachine of secrets on relation test Add vault caching of secrets on relation test Oct 13, 2023
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.

None yet

2 participants