-
Notifications
You must be signed in to change notification settings - Fork 8
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
added serverless function and kubectl hyperkube command to remove pem… #41
base: master
Are you sure you want to change the base?
Conversation
headers=ctx.obj['headers'] | ||
) | ||
if r.status_code == 404: | ||
sys.exit(1) |
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.
Should this fail with a message?
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.
Also, Why would it return a 404? It seems to only return a 200 or 500.
Line 93 in 556af41
except ClientError as e: |
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.
500 makes sense
@@ -110,6 +110,13 @@ functions: | |||
path: clusters/get-pem | |||
method: get | |||
private: true | |||
remove_pem: |
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 feel like a test should be added for adding and removing pems.
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.
Sounds good!! Now that the Moto framework in place should be no problem
What: new endpoint to request to remove pem for a given cluster
Why: Pipeline is currenltly not cleaning up pem files from hyperkube when a cluster is deleted.