-
Notifications
You must be signed in to change notification settings - Fork 218
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
Pass enclave path as CLI argument rather than in configuration #5665
Pass enclave path as CLI argument rather than in configuration #5665
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.
I think the daily canary should be touched so that we check that we can still spin up very old nodes?
pass_enclave_path_on_cli@76208 aka 20230921.18 vs main ewma over 20 builds from 75737 to 76203 Click to see tablemain
pass_enclave_path_on_cli
|
…into pass_enclave_path_on_cli
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
…soft#5665) (cherry picked from commit a9be7ea)
#5384
We haven't deprecated a configuration option before, so I'm inventing the process here. There's a new CLI option that will be preferred if it is present. If it is not present, but the config entry is, we'll use the config entry and log a warning. The config entry is listed in the schema but no longer required. A future removal step should simply remove it from the schema (and struct definition), and remove the fallback assignment in the code.
NB: Still need to do the same for
attestation.security_context_directory
, will do that in a separate PR.