Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Suggested change to AmazonEbsSurrogate to fix unknown configuration key error and expected map got slice error #181

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Suggested change to AmazonEbsSurrogate to fix unknown configuration key error and expected map got slice error #181

wants to merge 2 commits into from

Commits on Oct 2, 2020

  1. Fixed ami_root_device expected map found slice 

    Packer expects ami_root_device to be map of values and not slice,
expecting a list of BlockDeviceMapping forces the user to do workarounds
like populate the ami_root_device with slice, pop it of and set it to be
map afterwards.
    Dennis Vinterfjärd committed Oct 2, 2020
    Configuration menu
    Copy the full SHA
    b945a31 View commit details
    Browse the repository at this point in the history

  2. Removed invalid parameter in AmazonEbsSurrogate 

    AmazonEbsSurrogate was expecting prop source_device_name, running packer
validate on output generated with source_device_name configured in
AmazonEbsSurrogate returns unknown configuration key:
"source_device_name"

source_device_name is not a valid parameter for amazon ebs builder
according to https://www.packer.io/docs/builders/amazon-ebs
    Dennis Vinterfjärd committed Oct 2, 2020
    Configuration menu
    Copy the full SHA
    00151c3 View commit details
    Browse the repository at this point in the history