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

fix: set keypair to ACTIVE #286

Conversation

paullatzelsperger
Copy link
Member

What this PR changes/adds

This PR fixes the handling of the KeyPairResource's ACTIVE state

Why it does that

There was no way to move the key pair to the ACTIVE state before.

Further notes

Linked Issue(s)

Closes #284

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

issue warning if new key is inactive, and no other active ones

add endpoint to KeyPairResourceApi

added tests
@paullatzelsperger paullatzelsperger added bug Something isn't working api labels Feb 29, 2024
@paullatzelsperger paullatzelsperger self-assigned this Feb 29, 2024
@@ -144,6 +148,13 @@
return this;
}

public KeyPairResource build() {

Check notice

Code scanning / CodeQL

Missing Override annotation Note

This method overrides
Builder<KeyPairResource,Builder>.build
; it is advisable to add an Override annotation.
@paullatzelsperger paullatzelsperger force-pushed the fix/284_set_keypair_to_active branch from fd0bdb0 to 92caf3c Compare February 29, 2024 09:46
@paullatzelsperger paullatzelsperger merged commit a411560 into eclipse-edc:main Feb 29, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Set state to ACTIVE when creating new key pairs
2 participants