Skip to content
This repository has been archived by the owner on Feb 24, 2021. It is now read-only.

Implement ready-to-run signal for secure bootstrapping implementation #349

Closed
bnevis-i opened this issue Nov 18, 2020 · 0 comments · Fixed by #372
Closed

Implement ready-to-run signal for secure bootstrapping implementation #349

bnevis-i opened this issue Nov 18, 2020 · 0 comments · Fixed by #372
Assignees
Labels
3-high priority denoting release-blocking issues enhancement New feature or request security-services
Milestone

Comments

@bnevis-i
Copy link
Collaborator

Part of implementation of secure bootstrapping ADR.

Create a container to raise the ready-to-run signal/socket.

This could be implemented as a new container, or tacked on to the existing vault-worker.

According to the ADR, it could be combined with bootstrap/control container.

@bnevis-i bnevis-i added enhancement New feature or request 3-high priority denoting release-blocking issues security-services labels Nov 18, 2020
@bnevis-i bnevis-i added this to the Ireland milestone Nov 18, 2020
@jim-wang-intel jim-wang-intel linked a pull request Jan 5, 2021 that will close this issue
2 tasks
jim-wang-intel added a commit to jim-wang-intel/developer-scripts that referenced this issue Jan 27, 2021
Docker-compose deploys with a new security-bootstrapper service which controls the security bootstrapping steps for various phases.
The details are summarized in ADR secure bootstrapping.

Add command env addition and command overrides for core-services

Now the environment vars for security-stage-gate are in env file and overrides when necessary.

Update asc-http-export-secure and asc-mqtt-export-secure to be gated by security-bootstrapper.

Added common-sec-stage-gate.env description

Updated some typos in the document

Standardize the security-bootstrapper env file and naming of some docker containers
eg vault-worker -> secretstore-setup, edgex-proxy -> proxy-setup

Use the name common-sec-stage-gate.env as the env file for security-bootstrapper

Fix the problem of missing common.env and env quotation

Standardize the naming for appservice to app-service

Closes: edgexfoundry#349, edgexfoundry#237

Signed-off-by: Jim Wang <[email protected]>
lenny-goodell pushed a commit that referenced this issue Jan 27, 2021
Docker-compose deploys with a new security-bootstrapper service which controls the security bootstrapping steps for various phases.
The details are summarized in ADR secure bootstrapping.

Add command env addition and command overrides for core-services

Now the environment vars for security-stage-gate are in env file and overrides when necessary.

Update asc-http-export-secure and asc-mqtt-export-secure to be gated by security-bootstrapper.

Added common-sec-stage-gate.env description

Updated some typos in the document

Standardize the security-bootstrapper env file and naming of some docker containers
eg vault-worker -> secretstore-setup, edgex-proxy -> proxy-setup

Use the name common-sec-stage-gate.env as the env file for security-bootstrapper

Fix the problem of missing common.env and env quotation

Standardize the naming for appservice to app-service

Closes: #349, #237

Signed-off-by: Jim Wang <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
3-high priority denoting release-blocking issues enhancement New feature or request security-services
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants