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

Descriptive file names, VaultConnector implementation and tests, Key services implementation #17

Merged
merged 11 commits into from
Nov 20, 2024

Conversation

MGTheTrain
Copy link
Owner

Checklist

  • I adhere the trunk-based workflow
  • I verify that the CHANGELOG.md includes comprehensive documentation for the implemented features or fixed bugs. Increment the minor version such as from 0.1.0 to 0.2.0 for implemented features and increment the patch version from 0.1.0 to 0.1.1 for bug fixes. If any breaking changes occur, increment the major version, like from 0.1.0 to 1.0.0. Also see Semantic Versioning 2.0.0
  • I ensure that all merge conflicts are resolved before asking for a PR reviewer
  • To ensure the success of all pull request workflows, I run the format-and-lint.sh and run-test.sh locally.

Reference/Link to the issue solved with this PR (if any)

@MGTheTrain MGTheTrain changed the title Opt/general Descriptive file names, VaultConnector implementation and tests, Key service implementation Nov 20, 2024
MGTheTrain

This comment was marked as outdated.

@MGTheTrain MGTheTrain merged commit 515ac3c into main Nov 20, 2024
2 checks passed
@MGTheTrain MGTheTrain changed the title Descriptive file names, VaultConnector implementation and tests, Key service implementation Descriptive file names, VaultConnector implementation and tests, Key services implementation Nov 20, 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