-
Notifications
You must be signed in to change notification settings - Fork 58
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
Call revocation actions #159
Conversation
2a0879c
to
f7e7180
Compare
7b55ede
to
2693f38
Compare
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.
Looks like great progress!! 😄
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.
This is looking good to me. It would be nice to have some tests, just trying to think how we can do that. Not sure if we need to mock or can rely on the CI containers having a py env.
4e55d27
to
1067596
Compare
@lukehinds This is a good point and I'm adding some unit tests. |
@ashcrow @lukehinds I will have to figure out this CI failure tomorrow (not able to replicated it locally) and might add some more unit tests, but was wondering if you have other comments on how it works currently. Thanks. |
d1cfb6a
to
7725ccd
Compare
d7ceb56
to
4b33cc8
Compare
Tests passing again! |
8e0eeb9
to
af04103
Compare
0ad6fe3
to
5e029f5
Compare
Signed-off-by: Lily Sturmann <[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.
👍 😄
|
||
let mut outputs = Vec::new(); | ||
|
||
if Path::new(&action_file).exists() { |
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.
future: It may make sense to load this once rather than when we run revocations. However, I believe this is fine and may be what we want long term depending on the expectations of the users.
looks good to me , @lkatalin you can self merge if you like (just in case you have further tweaks). |
This code runs those revocation scripts which were sent by the tenant and can be accessed from the secure mount point post-attestation.
I've decided not to check whether the revocation scripts begin with
local_action
, since they are all listed inaction_list
anyhow. But if someone has a reason that they should be marked that way, I can add this check back again.I had a few other thoughts and questions inline marked with
TODO
and would love some suggestions on those points. The most important being: If these scripts don't run for whatever reason (ex. the Python version was too old), is that detected in some other part of the code? It seems like we would want a guarantee that a node can't continue to be in the cluster if it doesn't run the scripts, since it could still be in communication with the compromised node, for example.