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.

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

Post processor I handled buildvar type #152

Closed
melcloud opened this issue Sep 18, 2021 · 4 comments
Closed

Post processor I handled buildvar type #152

melcloud opened this issue Sep 18, 2021 · 4 comments
Labels

Comments

@melcloud
Copy link

Post manifest processor throws exception

With 1.0.3 version of the plug-in, the changes introduced for post processor broke manifest processor. Got error message: unhandled buildvar type: []interface{}

Reproduction Steps

  1. Add azure source with public gallery image
  2. Add post processor manifest

Plugin and Packer version

From packer version

1.7.4

Simplified Packer Buildfile

Post-processor "manifest" {
  Output = "manifest.json"
  Script_path = true
}

Operating system and Environment

Alpine 3

Log Fragments and crash.log

Post-processor failed: unhandled buildvar type: []interface {}

@melcloud melcloud added the bug label Sep 18, 2021
@biggles007
Copy link

Has anyone found a way around this? I would like to use the manifest functionality but can't find a workaround. I tried v1.0.2 of the plugin and got the same error.

@mag009
Copy link

mag009 commented Nov 12, 2021

same error reported #168

@vaygr
Copy link

vaygr commented Nov 22, 2021

A simple shell-local post-processor usage results in the same error.

dduportal added a commit to jenkins-infra/packer-images that referenced this issue Jan 11, 2022
@nywilken
Copy link
Contributor

nywilken commented Feb 8, 2022

Hello 👋 thanks again for reporting. This issue has been fixed in #182 ; some test binaries are available via the link below if you would like to test the fix.

https://app.circleci.com/pipelines/github/hashicorp/packer-plugin-azure/153/workflows/e0edb970-c2f0-4363-833a-5decb9e483d8/jobs/2047/artifacts

I'm going to close this issue. If you find that in testing with the test binaries you are still running into issues please drop a comment on the thread and we will reopen the issue. Cheers!

@nywilken nywilken closed this as completed Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants