packer

Commit Graph

Author	SHA1	Message	Date
Sylvia Moss	bc11853ecf	Rename method writeSpecField to goFieldToCtyType (#8687 )	6 years ago
Sylvia Moss	08b0bd1d2c	Fix HCL2 code generation for slices within another slice (#8669 )	6 years ago
Adrien Delorme	13ea97a1df	mapstructure-to-hcl2: make basic named types pointers ( optional )	6 years ago
Adrien Delorme	dc5bde97d7	log& skip field if struct tag parse did not work	6 years ago
Adrien Delorme	731904d3d2	mapstructure-to-hcl2: use accessor for named types and not named type + go genrate + tests	6 years ago
Adrien Delorme	0785c2f6fc	build using HCL2 (#8423 ) This follows #8232 which added the code to generate the code required to parse HCL files for each packer component. All old config files of packer will keep on working the same. Packer takes one argument. When a directory is passed, all files in the folder with a name ending with “.pkr.hcl” or “.pkr.json” will be parsed using the HCL2 format. When a file ending with “.pkr.hcl” or “.pkr.json” is passed it will be parsed using the HCL2 format. For every other case; the old packer style will be used. ## 1. the hcl2template pkg can create a packer.Build from a set of HCL (v2) files I had to make the packer.coreBuild (which is our one and only packer.Build ) a public struct with public fields ## 2. Components interfaces get a new ConfigSpec Method to read a file from an HCL file. This is a breaking change for packer plugins. a packer component can be a: builder/provisioner/post-processor each component interface now gets a `ConfigSpec() hcldec.ObjectSpec` which allows packer to tell what is the layout of the hcl2 config meant to configure that specific component. This ObjectSpec is sent through the wire (RPC) and a cty.Value is now sent through the already existing configuration entrypoints: Provisioner.Prepare(raws ...interface{}) error Builder.Prepare(raws ...interface{}) ([]string, error) PostProcessor.Configure(raws ...interface{}) error close #1768 Example hcl files: ```hcl // file amazon-ebs-kms-key/run.pkr.hcl build { sources = [ "source.amazon-ebs.first", ] provisioner "shell" { inline = [ "sleep 5" ] } post-processor "shell-local" { inline = [ "sleep 5" ] } } // amazon-ebs-kms-key/source.pkr.hcl source "amazon-ebs" "first" { ami_name = "hcl2-test" region = "us-east-1" instance_type = "t2.micro" kms_key_id = "c729958f-c6ba-44cd-ab39-35ab68ce0a6c" encrypt_boot = true source_ami_filter { filters { virtualization-type = "hvm" name = "amzn-ami-hvm-????.??.?.????????-x86_64-gp2" root-device-type = "ebs" } most_recent = true owners = ["amazon"] } launch_block_device_mappings { device_name = "/dev/xvda" volume_size = 20 volume_type = "gp2" delete_on_termination = "true" } launch_block_device_mappings { device_name = "/dev/xvdf" volume_size = 500 volume_type = "gp2" delete_on_termination = true encrypted = true } ami_regions = ["eu-central-1"] run_tags { Name = "packer-solr-something" stack-name = "DevOps Tools" } communicator = "ssh" ssh_pty = true ssh_username = "ec2-user" associate_public_ip_address = true } ```	6 years ago
Megan Marsh	da53ac99be	when using a slice of an imported field type, the Underlying still returned the slice rather than the element type.	7 years ago
Adrien Delorme	f6af5ecf07	Update mapstructure-to-hcl2.go make log/usage prompt prefix coherent	7 years ago
Adrien Delorme	9dac7908a5	Update mapstructure-to-hcl2.go better comments	7 years ago
Adrien Delorme	0eb9090dcf	Create mapstructure-to-hcl2.go mapstructure-to-hcl2 fills the gaps between hcl2 and mapstructure for Packer By generating a struct that the HCL2 ecosystem understands making use of mapstructure tags. Packer heavily uses the mapstructure decoding library to load/parse user config files. Packer now needs to move to HCL2. Here are a few differences/gaps betweens hcl2 and mapstructure: * in HCL2 all basic struct fields (string/int/struct) that are not pointers are required ( must be set ). In mapstructure everything is optional. * mapstructure allows to 'squash' fields (ex: Field CommonStructType `mapstructure:",squash"`) this allows to decorate structs and reuse configuration code. HCL2 parsing libs don't have anything similar. mapstructure-to-hcl2 will parse Packer's config files and generate the HCL2 compliant code that will allow to not change any of the current builders in order to move to HCL2 to softly move to HCL2.	7 years ago

10 Commits (9891e75f75696d514baff262e8aacd9eb25a8051)