-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add artifacts support #1189
base: master
Are you sure you want to change the base?
Add artifacts support #1189
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the usecase for this?
Change-type: patch Signed-off-by: Alex Gonzalez <[email protected]>
Artifacts are needed to program some device types, like the CM4 with secure boot support. Change-type: patch Signed-off-by: Alex Gonzalez <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Several clarifications,
- Are we hoping to send several artifacts in the future? If it's a singular folder or file, then would it be better to call it
artifact
ortestArtifact
orextraArtifact
- Adding it here in the e2e suite.js wouldn't have an effect since there is no
artifacts
property in the suites/config.js
- Either we add it to config.js and it gets tested in the e2e tests of leviathan
- Or we don't add it at all in the e2e tests.
I have introduced this in the config.js schema so at least it won't error out when the client processes it.
Signed-off-by: Vipul Gupta (@vipulgupta2048) <[email protected]>
Signed-off-by: Vipul Gupta (@vipulgupta2048) <[email protected]>
No description provided.