b4200c3590
go generate for the google compute export post processor after #8388
2019-12-02 11:32:16 +01:00
e1cb0c5f7e
Added support for specifying Service Account in Google Compute exporter post-processor. ( #8388 )
2019-12-02 11:29:34 +01:00
819329228a
Change back to make sure all durations are a time.Duration
...
It is simply the best/simplest solution and trying to prevent users from passing and integer here would be like opening a can of worms. Because:
* we cannot make mapstructure validate our duration string ( with an UnmarshalJSON func etc.)
* we cannot make mapstructure spit a string instead of a duration and packer will decode-encode-decode config.
* the hcl2 generated code asks for a string, so this will be enforced by default.
2019-10-31 16:12:07 +01:00
bf3d9841c6
Force durations to be passed a strings
...
Before this commit it was possible to set a duration using an integer or a float. Go's time.Duration is an int64 internally an mapstructure will take advantage of this and load the number as a int64 but `1` means one ns which is unexpected/confusing. To avoid confusion and enforce readability this forces users to pass a string with a unit for a duration; ex "56s".
2019-10-31 11:47:19 +01:00
078ba7c8c3
commit old code generation tool
...
for history
2019-10-15 12:56:42 +02:00
771a6e55ef
pp.google.[import|export]: unexport Account field
...
so it doesnt temper with hcl2 cfg generation
2019-10-15 12:56:42 +02:00
3c14c50aba
Allow user to real oauth token from properly configured Vault instance
2019-09-23 13:26:03 -07:00
0dfb3cc56f
replace some bespoke google auth code with code from golang's oauth2 library
2019-07-03 14:27:33 -07:00
a81abd297b
Merge remote-tracking branch 'origin/master' into context_provisioner
2019-04-08 20:09:01 +02:00
9dafa310f3
remove redundant keep_input_artifact code from googlecompute-export and googlecompute-import pps. The behavior coded here was already enforced by the core postprocessor code in packer/build.go
2019-04-03 12:05:38 -07:00
e65115a7a0
contextualize post-processor
2019-04-03 15:55:55 +02:00
12fc1fa751
default_keep_input_artifact
2019-04-02 16:51:58 -07:00
f9ae926d8f
googlecompute-export: set network project id to builder
2019-03-01 15:12:31 +01:00
8975f67901
googlecompute-export: add exporter instance configs
2019-01-25 11:36:18 +01:00
625201c819
Merge pull request #4148 from minimum2scp/features/googlecompute-export-application-default-credential
...
googlecompute-export: use application default credential
2018-02-05 09:51:21 -08:00
366dc3da0a
move multistep imports to helper.
...
gomvpkg -from "github.com/mitchellh/multistep" -to "github.com/hashicorp/packer/helper/multistep"
2018-01-24 17:09:15 -08:00
e45223a867
Fix -on-error issue not working.
...
When we supply -on-error flag for Packer with Hyper-v builder, it does not do anything.
2017-09-01 00:14:28 +05:30
81522dced0
move packer to hashicorp
2017-04-04 13:39:01 -07:00
5dc6b18365
googlecompute-export: use application default credential as same as googlecompute builder
2016-11-10 18:58:38 +09:00
61e2ea308e
googlecompute-export: Fixed scopes to run gcloud, gsutil in startup script
2016-11-10 17:54:28 +09:00
85210afe92
googlecompute: conditionally omit the wait for startup script step if no startup script is provided.
2016-11-02 15:20:21 -07:00
a8e57d83d2
gofmt project.
...
noticed many unrelated changes being added to patches because of gofmt.
ran `find . -not -path "./vendor/*" -name "*.go" -exec gofmt -w {} \;`
2016-09-29 14:13:06 -07:00
1b9b37bdc1
Added some error handling and logs for the GCE export startup script.
2016-08-15 16:25:57 -07:00
55b5a45ae4
Created googlecompute-export post-processor. Modified the googlecompute builder to pass a few configuration values to its resulting artifact. These values can then be used in googlecompute-export post-processor.
...
Added documentation and changed authentication stuff on temporary VM.
2016-08-15 14:36:26 -07:00
Adrien Delorme
Taneli Leppä
Megan Marsh
Arnaud Dezandee
Matthew Hooker
Vijaya Bhaskar Reddy Kondreddi
YAMADA Tsuyoshi
Scott Crunkleton
crunk1