bottlerocket-os / bottlerocket-os/twoliter
image_id SSM parameters should use `aws:ec2:image` data type
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 34
- Forks
- 45
- Avg merge
- 11h 13m
- Merged PRs (30d)
- 16
Description
What I'd like:
I'd like for the image_id parameters to have the aws:ec2:image data type, so that they can be used directly by the EC2 RunInstances API.
aws ec2 run-instances --image-id "resolve:ssm:/path/to/parameter" ...
The image_version parameters should continue to use the text data type.
Note that the data type can't be changed for existing parameters.
Any alternatives you've considered:
Alternatives for dealing with existing parameters:
- only support the
aws:ec2:imagedata type for new variants - teach
pubsysto fall back to updating the value astextif it encounters an exception updating the value asaws:ec2:image - add another parameter (
ec2_image_id) with the new data type - add an "API" prefix to the path (
{variant}/{arch}/2022-12-12/image_id) and continue publishing the old data type under ({variant}/{arch}/image_id)
Contributor guide
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 file or test is named; start by locating the SSM parameter publishing logic and the pubsys path that creates or updates image_id and image_version parameters. Confirm how existing parameters are handled, then verify that new image_id parameters use aws:ec2:image while image_version remains text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100