Packer
Oxide
@oxidecomputer
The Oxide multi-component plugin can be used with HashiCorp (IBM) Packer to create custom Oxide images.
- Community
Updated 2 weeks ago
- GitHub(opens in new tab)
Oxide Image
Type: oxide-image
The oxide-image data source fetches Oxide image
information for use in a Packer build. The image can be a project image or
silo image.
Configuration
The configuration arguments for the data source. Arguments can either be required or optional.
Required
name(string) - Name of the image to fetch.
Optional
host(string) - Oxide API URL (e.g.,https://oxide.sys.example.com). If not specified, this defaults to the value of theOXIDE_HOSTenvironment variable. When specified,tokenmust be specified. Conflicts withprofile.token(string) - Oxide API token. If not specified, this defaults to the value of theOXIDE_TOKENenvironment variable. When specified,hostmust be specified. Conflicts withprofile.profile(string) - Oxide credentials profile. If not specified, this defaults to the value of theOXIDE_PROFILEenvironment variable. Conflicts withhostandtoken.project(string) - Name or ID of the project containing the image to fetch. Leave blank to fetch a silo image instead of a project image.
Outputs
image_id(string) - ID of the image that was fetched.
Examples
Fetch a project image.
data "oxide-image" "example" {
name = "ubuntu"
project = "oxide"
}
Fetch a silo image.
data "oxide-image" "example" {
name = "ubuntu"
}