Include descriptive information on created resources
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 224
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
When creating resources such as keys it is a good practice to include some descriptive information with them to make it easier to identify their intent later.
For example, when creating keys the description field can be set.
$ aws kms create-key --description "for awspics"
The alias value which appears on the kms console can also be set. This will appear on the KMS console in the list of keys.
$ aws kms create-alias --alias-name alias/awspics --target-key-id xxx
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the CloudFormation resource definitions for created keys and other resources, then determine which descriptions and KMS aliases should be included; done means the generated resources carry useful descriptive metadata and the stack remains deployable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100