-
Notifications
You must be signed in to change notification settings - Fork 8
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
Feature: As a project developer, I want to use the vault data access object that it's specified in the property file #108
Comments
DoD/OTS passed |
csun-cpointe
added a commit
that referenced
this issue
May 28, 2024
…-configuration-store-vault module
csun-cpointe
added a commit
that referenced
this issue
May 28, 2024
…-configuration-store-vault module
csun-cpointe
changed the title
TASK: As a project developer, I want to use the vault data access object that it's specified in the property file
FEATURE: As a project developer, I want to use the vault data access object that it's specified in the property file
May 28, 2024
csun-cpointe
added
enhancement
New feature or request
and removed
task
Support ticket - typically not code related
labels
May 28, 2024
csun-cpointe
changed the title
FEATURE: As a project developer, I want to use the vault data access object that it's specified in the property file
Feature: As a project developer, I want to use the vault data access object that it's specified in the property file
May 28, 2024
csun-cpointe
added a commit
that referenced
this issue
May 29, 2024
#108 vault property dao class can be injected when use the extensions-configuration-store-vault module
liangyun123
pushed a commit
that referenced
this issue
Jun 12, 2024
…-configuration-store-vault module
liangyun123
pushed a commit
that referenced
this issue
Jun 12, 2024
…-configuration-store-vault module
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
108Helper.zip
Description
Currently, when package the configuration-store-vault with the configuration store, the vault property dao was discovered in the CDI but can't be injected properly. The vault property dao file should be injected properly so that we can use the data access object that is specified in the property file.
DOD
Acceptance criteria required to complete the work
Test Strategy/Script
-pipeline-models/src/main/resources/pipelines
directorymvn clean install
, following the manual actions after each build until no more remain.test-issue-108-configuration-store-docker
folder to the-docker
directory and include the module to the -docker/pom.xml filemvn clean install
-deploy/src/main/resources/app
** in the
-docker/test-issue-108-configuration-store-docker/src/main/resources/krausening/base/encrypt.properties
file, replace thesecrets.root.key
with theROOT KEY
content** in the
-docker/test-issue-108-configuration-store-docker/src/main/resources/krausening/base/encrypt.properties
file, replace thesecrets.unseal.keys
with theUNSEAL KEYS
content (make sure to remove the [], ", and any space)References/Additional Context
As needed
The text was updated successfully, but these errors were encountered: