Skip to content
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.

[EdgeX Auto-Collector] Identify the components responsible for security #66

Closed
LavenderQAQ opened this issue Nov 14, 2022 · 1 comment · Fixed by #70
Closed

[EdgeX Auto-Collector] Identify the components responsible for security #66

LavenderQAQ opened this issue Nov 14, 2022 · 1 comment · Fixed by #70
Assignees

Comments

@LavenderQAQ
Copy link
Member

What would you like to be added:
By looking at the structure of edgex-compose, we can find that each edgex version above hanoi is divided into safe and unsafe versions. The insecure version of edgex is a subset of the secure version. In other words, the secure version of edgex will add some components and configurations on the basis of the insecure version. For the added components, we can scan the component information by grabbing the docker-compose-<version>-no-secty.yml file to see which components are secure. For the added configuration, since the added environment variables do not have any effect on the running of the insecure version, we can ignore them.
Write the result to the IsSecurity field in Component

type Component struct {
	Name         string            `yaml:"name"`
	Image        string            `yaml:"image"`
	Volumes      []string          `yaml:"volumns,omitempty"`
	ComponentEnv map[string]string `yaml:"componentEnv,omitempty"`
	// TODO: We need to collect another no-security file and mark which components are not secure
	IsSecurity bool `yaml:"isSecurity"`
	// A pointer to the Env of the previous level
	envRef *map[string]string
}

Refer to Add a security switch

Why is this needed:
Refer to EdgeX Auto-colllector Proposal

others
/kind feature

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant