-
Notifications
You must be signed in to change notification settings - Fork 107
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
Jk/cumulus 3785 2 #3702
Jk/cumulus 3785 2 #3702
Conversation
Super Constructor: When calling the super(message) constructor, it's better to pass a more descriptive message, like "CumulusApiClientError: " + message, so that when you catch this error, you'll immediately know what type of error it is without having to inspect the class name.
…ot provided the implementation for this function. Ensure that it handles errors correctly. In the getPrivateKey() method, KMS.decryptBase64String(fetchedKey) is used, but it appears the result isn't awaited. If decryptBase64String is asynchronous, you need to use await. Encryption & Decryption: decrypt is imported and used, but you have not provided the implementation for this function. Ensure that it handles errors correctly. In the getPrivateKey() method, KMS.decryptBase64String(fetchedKey) is used, but it appears the result isn't awaited. If decryptBase64String is asynchronous, you need to use await.
This reverts commit 10d3166.
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.
Changes look good to me but there's a conflict in the CL that needs to be resolved before this can be merged.
@@ -14,7 +14,7 @@ const { s3 } = require('@cumulus/aws-client/services'); | |||
* @param {Object} res - express response object | |||
* @returns {Promise<Object>} the promise of express response object | |||
*/ | |||
async function handleGetRequst(req, res) { | |||
async function handleGetRequest(req, res) { |
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.
Is this called anywhere else (e.g. a test?) that might also need updating?
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 verified the refactor in the Core codebase (text search for references) - I don't believe it's used in the dashboard directly.
@@ -188,6 +188,13 @@ to update to at least [cumulus-ecs-task:2.1.0](https://hub.docker.com/layers/cum | |||
- **CUMULUS-3606** | |||
- Updated with additional documentation covering tunneling configuration | |||
using a PKCS11 provider | |||
- **CUMULUS-3700** |
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.
These need fixed.
Summary: Summary of changes
Addresses CUMULUS-3785
Changes
This PR includes contributions from the following user PRs:
#3485
#3590
#3628
#3685
in addition to minor corrections/CHANGELOG updates from me/the team.
PR Checklist