feat(security): Add secret store config for delayed start

[bnevis-i]

Signed-off-by: Bryon Nevis [email protected]

PR Checklist

Please check if your PR fulfills the following requirements:

• I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
• I am not introducing a new dependency (add notes below if you are)
• I have added unit tests for the new feature or bug fix (if not, why?)
• I have fully tested (add details below) this the new feature or bug fix (if not, why?)
• I have opened a PR for the related docs change (if not, why?)

Testing Instructions

In compose scripts, make run delayed-start

New Dependency Instructions (If applicable)

[bnevis-i]

@jpwhitemn Example of the boilerplate for delayed start services
@jim-wang-intel Please make sure I got this correct (do we want to default localhost like everything else?)

[jim-wang-intel]

@jpwhitemn Example of the boilerplate for delayed start services @jim-wang-intel Please make sure I got this correct (do we want to default localhost like everything else?)

@bnevis-i / @jpwhitemn :
Format and naming-wise are correct; but i do have a question: do we need to make these configuration for all-core-services as I thought they don't do delayed-start (like core-data, for example)?

[bnevis-i]

@jpwhitemn Example of the boilerplate for delayed start services @jim-wang-intel Please make sure I got this correct (do we want to default localhost like everything else?)

@bnevis-i / @jpwhitemn : Format and naming-wise are correct; but i do have a question: do we need to make these configuration for all-core-services as I thought they don't do delayed-start (like core-data, for example)?

The point of the exercise is that we make the configuration visible, even if we don't intend to enable it at this point.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
7.2% Duplication

[lenny-goodell]

LGTM