We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using below code with go generate -v -x
go generate -v -x
//go:generate packer-sdc struct-markdown //go:generate packer-sdc mapstructure-to-hcl2 -type ProvisionerConfig
will get stuck forever doing nothing
❯ go generate -v -x data.go packer-sdc mapstructure-to-hcl2 -type DataSourceOutput,DataSourceConfig data.hcl2spec.go main.go post-processor.go packer-sdc mapstructure-to-hcl2 -type PostProcessorConfig post-processor.hcl2spec.go provisioner.go packer-sdc struct-markdown
git clone https://git.panekj.dev/pj/packer-plugin-http.git cd packer-plugin-http go generate -v -x
packersdk.Version
❯ packer-sdc --version 0.4.0
require ( github.com/hashicorp/hcl/v2 v2.14.1 github.com/hashicorp/packer-plugin-sdk v0.4.0 github.com/zclconf/go-cty v1.10.0 golang.org/x/net v0.8.0 )
Same thing happening on 0.3.4
0.3.4
OS: macOS 13.1 Architecture: arm64
macOS 13.1
arm64
❯ go version go version go1.20.2 darwin/arm64
can reproduce it on Ubuntu 22.04 x64
The text was updated successfully, but these errors were encountered:
Hi there @panekj I don't have access to your repo to test against. Are you still running into this issue?
If so, can you please provide access to the plugin so that we can test against it to see what might be happening. Thanks.
Sorry, something went wrong.
No branches or pull requests
Overview of the Issue
Using below code with
go generate -v -x
will get stuck forever doing nothing
Reproduction Steps
Packer Plugin SDK version
packersdk.Version
Same thing happening on
0.3.4
Operating system and Environment details
OS:
macOS 13.1
Architecture:
arm64
can reproduce it on Ubuntu 22.04 x64
The text was updated successfully, but these errors were encountered: