Closed drewmullen closed 4 months ago
Hi 👋 thanks for reaching out.
For general questions we recommend reaching out to the [community forum](https://discuss.hashicorp.com/c/packer) for greater visibility.
As the GitHub issue tracker is only watched by a small subset of maintainers and is really reserved for bugs and enhancements, you'll have a better chance of finding someone who can help you in the forum.
We'll mark this issue as needs-reply to help inform maintainers that this question is awaiting a response.
If no activity is taken on this question within 30 days it will be automatically closed.
If you find the forum to be more helpful or if you've found the answer to your question elsewhere please feel free to post a response and close the issue.
After doing a few hours of research I am closing this issue and have opened a better scoped question on discuss: https://discuss.hashicorp.com/t/plugin-development-how-can-i-debug-my-step-functions/64796
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
This is my first time developing a Packer builder and I'm trying to debug an issue in my code. With Terraform Provider development I have a setup for vscode debuging which exposes runtime variables and allows me to declare break points, step into / over /out of functions, etc.
Using the below launch.json I can run a test in debug mode. However, its not finding my plugin:
Launch.json
This seems to indicate to me that its looking for a pre-compiled binary... so if i add the
PACKER_PLUGIN_PATH
it can find the binary. HOWEVER, then its not actually using my source which means it doesnt respect break points...Yall have any idea how i can configure VSCode to compile this as part of the test run and use break points, etc?