oxidecomputer / oxidecomputer/packer-plugin-oxide
Richer oxide-image data source (full output attributes, lookup by ID, most_recent + filters)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 1
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 3
Description
Problem
The oxide-image data source takes an exact image name and returns only image_id. Users coming from amazon-ami / digitalocean-image expect substantially more:
- Full output attributes: name, OS, version, size, block size, digest, description, creation timestamp — not just the ID.
- Lookup by ID in addition to name.
most_recent+ filter semantics so templates can express "latest noble image" instead of hard-coding an exact name that changes every release.
Additionally, silo-vs-project lookup currently relies on an SDK serialization quirk — the code comment in component/data-source/image/data_source.go:87 admits it: "This relies on the Go SDK omitting empty strings from serialization to fetch silo images." This should be explicit.
Fix
- Expand
DatasourceOutputwith the image attributes above. - Add
most_recentand name-filter/regex selection overImageList. - Make project vs silo lookup explicit rather than serialization-dependent.
- Consider whether a plural
oxide-imagesdata source is warranted or if filters on the singular one suffice.
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
Start in component/data-source/image/data_source.go, especially the lookup around line 87, and inspect DatasourceOutput and the ImageList usage. Define how project versus silo lookup, ID or name selection, filters, and most_recent interact; done means the data source returns the requested image attributes and supports the documented selection behavior without relying on SDK serialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100