Configuration service to detect partial loads so that the properties are reload in the case

[tianliang0038]

Context:
we’ve already written the ConfigLoader tool of the config service which reads in the project’s properties and stores them in Vault. We now need to detect on start up the properties were partially loaded and reload in this case.

DOD

• Ensure secure handling of sensitive configurations
• Add new scenario for continue reloading
• Unit tests will be added to foundation-configuration-store
• Update documentation
  • reflect the configuration changes needed for the deployment in the antora docs
  • relevant baseline READMEs with any potential nuances with testing implementations

BDD test scenarios

  Scenario: The Configuration Service deal with partial load on start up
     Given a base URI indicating a directory housing valid base configurations 
        And an environment-specific URI indicating a directory housing valid environment-specific configurations
     When the configuration service starts
       Then the configurations are partially loaded into the configuration store
         And the configuration service checks the that the given configurations were partially loaded 
         And the configuration tries reloading until status is fully-loaded. (max 3 tries)

Test Steps:

1. Create a downstream project

mvn archetype:generate -U -DarchetypeGroupId=com.boozallen.aissemble \
                      -DarchetypeArtifactId=foundation-archetype \
                      -DarchetypeVersion=1.7.0-SNAPSHOT \
                      -DgroupId=com.boozallen.aissemble.test \
                      -DartifactId=test-issue-129 \
                      -DprojectGitUrl=git.example.com/test-issue-129 \
                      -DprojectName="Issue#129 Test"

2. Unzip the to_be_added file.
3. Copy the SparkPipeline.json file -pipeline-models/src/main/resources/pipelines directory
4. Repeatedly execute mvn clean install, following the manual actions after each build until no more remain.
5. Unzip and copy the test-issues-129-configuration-store-docker folder to the -docker directory and include the module to the -docker/pom.xml file

    <modules>
       ...
        <module>test-issue-129-configuration-store-docker</module> 
        <!-- TODO: Add docker modules here -->
    </modules>

6. Run mvn clean install
7. Unzip and copy the configuration-store-service folder to be under the -deploy/src/main/resources/app
8. Include below content to the Tilt file

yaml = helm(
   'test-issue-129-deploy/src/main/resources/apps/config-store-service',
   name='config-store-service',
   values=['test-issue-129-deploy/src/main/resources/apps/config-store-service/values.yaml',
       'test-issue-129-deploy/src/main/resources/apps/config-store-service/values-dev.yaml']
)
k8s_yaml(yaml)

# configuration-store
docker_build(
    ref='boozallen/test-issue-129-configuration-store-docker',
    context='test-issue-129-docker/test-issue-129-configuration-store-docker',
    build_args=build_args,
    dockerfile='test-issue-129-docker/test-issue-129-configuration-store-docker/src/main/resources/docker/Dockerfile'
)

9.  Tilt up; wait for the vault service is ready, scroll up to find the root key, unseal keys (see below example),

• in the -docker/test-issue-129-configuration-store-docker/src/main/resources/krausening/base/encrypt.properties file, replace the secrets.root.key with the ROOT KEY content

• in the -docker/test-issue-129-configuration-store-docker/src/main/resources/krausening/base/encrypt.properties file, replace the secrets.unseal.keys with the UNSEAL KEYS content (make sure to remove the [], ", and any space)