github.com/hashicorp/packer@v1.14.3/website/content/partials/packer-plugin-sdk/communicator/Config-not-required.mdx (about)

     1  <!-- Code generated from the comments of the Config struct in communicator/config.go; DO NOT EDIT MANUALLY -->
     2  
     3  - `communicator` (string) - Packer currently supports three kinds of communicators:
     4    
     5    -   `none` - No communicator will be used. If this is set, most
     6        provisioners also can't be used.
     7    
     8    -   `ssh` - An SSH connection will be established to the machine. This
     9        is usually the default.
    10    
    11    -   `winrm` - A WinRM connection will be established.
    12    
    13    In addition to the above, some builders have custom communicators they
    14    can use. For example, the Docker builder has a "docker" communicator
    15    that uses `docker exec` and `docker cp` to execute scripts and copy
    16    files.
    17  
    18  - `pause_before_connecting` (duration string | ex: "1h5m2s") - We recommend that you enable SSH or WinRM as the very last step in your
    19    guest's bootstrap script, but sometimes you may have a race condition
    20    where you need Packer to wait before attempting to connect to your
    21    guest.
    22    
    23    If you end up in this situation, you can use the template option
    24    `pause_before_connecting`. By default, there is no pause. For example if
    25    you set `pause_before_connecting` to `10m` Packer will check whether it
    26    can connect, as normal. But once a connection attempt is successful, it
    27    will disconnect and then wait 10 minutes before connecting to the guest
    28    and beginning provisioning.
    29  
    30  <!-- End of code generated from the comments of the Config struct in communicator/config.go; -->