This project is mirrored from https://gitee.com/NQL886/packer.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 14 Dec, 2019 1 commit
  2. 13 Dec, 2019 1 commit
  3. 12 Dec, 2019 2 commits
  4. 11 Dec, 2019 2 commits
  5. 22 Nov, 2019 1 commit
  6. 06 Nov, 2019 1 commit
    • nywilken's avatar
      provisioner/shell: Add `env_var_format` support to shell provisioner · 3522e13b
      nywilken authored
      * Move setting of default EnvVarFormat to the Prepare function
      * Add generated hcl2 structure for the updated Shell provisioner config
      * Move `EnvVarFormat` field to shared common shell type
      * Add description for the `env_var_format` parameter
      * Update `env_var_format` when used with `use_env_var_file`
      3522e13b
  7. 31 Oct, 2019 2 commits
    • Adrien Delorme's avatar
      Change back to make sure all durations are a time.Duration · 81932922
      Adrien Delorme authored
      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.
      81932922
    • Adrien Delorme's avatar
      Force durations to be passed a strings · bf3d9841
      Adrien Delorme authored
      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".
      bf3d9841
  8. 15 Oct, 2019 1 commit
  9. 26 Jul, 2019 1 commit
  10. 30 May, 2019 1 commit
  11. 23 May, 2019 3 commits
  12. 17 May, 2019 1 commit
  13. 09 Apr, 2019 1 commit
  14. 08 Apr, 2019 1 commit
    • Adrien Delorme's avatar
      allow a provisioner to timeout · f555e7a9
      Adrien Delorme authored
      * I had to contextualise Communicator.Start and RemoteCmd.StartWithUi
      NOTE: Communicator.Start starts a RemoteCmd but RemoteCmd.StartWithUi will run the cmd and wait for a return, so I renamed StartWithUi to RunWithUi so that the intent is clearer.
      Ideally in the future RunWithUi will be named back to StartWithUi and the exit status or wait funcs of the command will allow to wait for a return. If you do so please read carrefully https://golang.org/pkg/os/exec/#Cmd.Stdout to avoid a deadlock
      * cmd.ExitStatus to cmd.ExitStatus() is now blocking to avoid race conditions
      * also had to simplify StartWithUi
      f555e7a9
  15. 03 Apr, 2019 1 commit
  16. 14 Mar, 2019 2 commits
  17. 12 Dec, 2018 1 commit
    • Adrien Delorme's avatar
      Add tmp package that offers Dir & File funcs · b7222d1f
      Adrien Delorme authored
      this regroups the calls of tmp func calls into one package.
      the tmp pkg allows to store tmp files under a common directory for easier managment
      
      Squashed commit of the following:
      commit 74b674c01560c6b547e9cab5e8afb486f0fe7d6c
      Merge: fc94b5714 66001525d
      Author: Matthew Patton <mpatton@enquizit.com>
      Date:   Fri Nov 2 02:02:38 2018 -0400
      
          Merge branch 'remove_TMPDIR_docs' of github.com:tb3088/packer into remove_TMPDIR_docs
      
      commit fc94b571428447aaf2e5171967c95cdf9e5c73ff
      Author: Matthew Patton <mpatton@enquizit.com>
      Date:   Fri Nov 2 01:42:38 2018 -0400
      
          update tests to honor configured temporary directory
      
      commit 5a562359f4937af506607dd96ed1c46426093f52
      Author: Matthew Patton <mpatton@enquizit.com>
      Date:   Thu Nov 1 18:52:38 2018 -0400
      
          sync straggler to refactor. implement tests at packer/configfile instead of buried in docker.
      
      commit 9d5a4a0935bfd049e2f8f50ad73e4455b42c9410
      Author: Matthew Patton <mpatton@enquizit.com>
      Date:   Thu Nov 1 15:39:46 2...
      b7222d1f
  18. 07 Dec, 2018 1 commit
  19. 06 Dec, 2018 1 commit
  20. 08 Nov, 2018 1 commit
  21. 12 Oct, 2018 2 commits
  22. 10 Sep, 2018 1 commit
  23. 24 Aug, 2018 1 commit
  24. 20 Aug, 2018 1 commit
  25. 14 Jun, 2018 2 commits
  26. 25 Apr, 2018 1 commit
  27. 24 Apr, 2018 3 commits
    • DanHam's avatar
      Change to CMD % style path is no longer required · 54193754
      DanHam authored
      Unverified
      54193754
    • DanHam's avatar
      Dollar's in env vars used in paths may cause problems for ssh · 5b652316
      DanHam authored
      * Dollars are interpreted by *nix shells so paths using env vars such as
        ${env:SYSTEMROOT} will cause issues
      Unverified
      5b652316
    • DanHam's avatar
      Allow users to specify the location that the env vars file is uploaded to · 4e7feea1
      DanHam authored
      Previously the location the file was uploaded to was set internally and
      used ${env:SYSTEMROOT}/Temp as the destination folder.
      By default, in order to inject the required environment variables, the file
      is 'dot sourced' by the 'execute_command' using the {{ .Vars }} variable.
      Unfortunately the inclusion of the dollar in the path caused issues for
      users connecting over ssh as the (typically bash) shell running the execute
      command would try and interpret the dollar sign.
      The change allows users to specify the location the file is uploaded to,
      thereby allowing the user to specify a custom 'execute_command' that
      escapes any dollar signs that could be present in the path.
      If not set the upload path now defaults to using C:/Windows/Temp as the
      upload folder.
      4e7feea1
  28. 16 Apr, 2018 1 commit
  29. 23 Mar, 2018 2 commits