Skip to content

Conversation

@zeroshade
Copy link
Member

If the MANIFEST is missing the Files.signature then we first try looking for driver + '.sig' and then error out.

Adds a new CLI argument --allow-missing-signature which will allow installing if the signature is missing.

Copy link
Member

@amoeba amoeba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this. Seems fine.

What did you think about maybe removing the partially-installed driver when install fails like this?

m := InstallCmd{Driver: "test-driver-no-sig"}.
GetModelCustom(baseModel{getDriverList: getTestDriverList, downloadPkg: downloadTestPkg})
out := suite.runCmdErr(m)
suite.Contains(out, "signature file 'test-driver-1-not-valid.so.sig' for driver is missing")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we test the state of the tmpdir after failure so we know what files remain when install fails? It'd be good as a regression test if we change the behavior.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I make the change in this PR to clean up after the failed install?

@zeroshade zeroshade merged commit a034489 into main Sep 17, 2025
7 checks passed
@zeroshade zeroshade deleted the install-no-signature branch September 17, 2025 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants