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

ON HOLD: store expects base64 encoded keys #46

Closed
wants to merge 1 commit into from

Conversation

cmwylie19
Copy link
Collaborator

Store now encodes keys so the expect would look like this:

[23:51:51.704] INFO (77258): observed
    updates: [
      {
        "YQ==": "1",
        "Yg==": "2",
        "Yw==": "3",
        "b2JzZXJ2ZWQ=": "yay"
      }

Signed-off-by: Case Wylie <cmwylie19@defenseunicorns.com>
@cmwylie19 cmwylie19 changed the title chore: store expects base64 encoded keys ON HOLD: store expects base64 encoded keys Jun 27, 2024
cmwylie19 added a commit to defenseunicorns/pepr that referenced this pull request Jul 23, 2024
## Description

This PR Migrates the Store to a v2 data path, migrates keys from
previous version before a read of the CR, patches them to v2, then
starts a watch. It also adds fuzzing, property-based, more unit and
journey tests.

<img width="690" alt="image"
src="https://github.com/defenseunicorns/pepr/assets/1096507/9b9522ad-2724-4579-866d-f73424e34991">


## Related Issue

Fixes #915 
<!-- or -->
Relates to PR
defenseunicorns/pepr-excellent-examples#46
updating the e2e test to expect the keys base64 encoded

## Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Other (security config, docs update, etc)

## Checklist before merging

- [x] Test, docs, adr added or updated as needed
- [x] [Contributor Guide
Steps](https://docs.pepr.dev/main/contribute/#submitting-a-pull-request)
followed

---------

Signed-off-by: Case Wylie <cmwylie19@defenseunicorns.com>
Co-authored-by: Barrett <81570928+btlghrants@users.noreply.github.com>
@cmwylie19
Copy link
Collaborator Author

we already fixed this in another PR

@cmwylie19 cmwylie19 closed this Aug 28, 2024
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.

1 participant