neoakris
commented
4 weeks ago If anyone else runs into a similar scenario The following is a snippet of a temporary workaround I'm considering/might use.
import { execSync } from 'child_process'; //work around kms UX issue
import console = require('console'); //can help debug feedback loop
const alias_key_to_lookup = "alias/eks/test";
const cmd = `aws kms list-aliases | jq '.Aliases[] | select(.AliasName == "${alias_key_to_lookup}") | .TargetKeyId'`
const cmd_results = execSync(cmd).toString();
console.log(cmd_results)
//TO DO: never pass un-sanitized input / would need tight input sanitization.cmd_results = "" if not found cmd_results = "ac97959f-c5fb-4de0-a584-2d741c05ea0b" if found ^-- basically a more graceful failure that's a lot easier to handle with if statement checks.
khushail
go-to-k
github-actions[bot]
Describe the feature
Here's a code snippet for some context:
Current State of CDK 2.133.0:
[Error at /$STACK_NAME] Could not find any key with alias named eks/testI tried wrapping the above in try catch logic, but the program still does a hard stop with the above error as soon as it discovers the key doesn't exist.
Feature Request/Proposed Solution:
If no key exists, instead of an error, return undefined. This will make it easier to allow if statements to handle that scenario.
Use Case
While using EKS Blueprints, every time I delete and recreate a cluster (semi-frequently for ephemeral sandbox / test environments), due to its defaults it'll create a new KMS key each time, then on delete I get orphaned kms keys. EKS Blueprints allows passing in a pre-existing kms key to avoid this.
However I'd like to add logic for the following use case:
Basically I wanted to be able to create a function named ensure_existence_of_kms_key_with_alias()
This will allow me to implement logic where when I create a cluster it'll create a kms key, but if I delete and recreate the cluster it'll reuse the original kms key. (This avoids orphaned keys, and is also advantageous in the scenario of if disk backups were ever created using a kms key, then restore might be easier if a consistent kms key were used.)
Other Information
The proposed feature/solution shouldn't be a breaking change.
Acknowledgements
CDK version used
2.133.0 (build dcc1e75)
Environment details (OS name and version, etc.)
MacOS Sonoma 14.6.1