Update [email protected] #37429
Merged
Update [email protected] #37429
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jbardin
added
the
no-changelog-needed
SarahFrench
reviewed
Aug 12, 2025
Go-plugin now reports stack traces via and Error log level, so we need to update the logger to watch that level instead. We also must explicitly enable logging for the plugin, because go-plugin will otherwise no send any logs at all.
jbardin
force-pushed
the
jbardin/update-go-plugin
branch
from
5359d5a to
7ed24d2
Compare
mildwonkey
approved these changes
Aug 13, 2025
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the go-plugin package to the latest release. Changes include
That second optimization is not something that Terraform can currently make use of though, because for a better user experience we still need to monitor the provider logs for stack traces. So even though neither of these changes directly affect Terraform, I'm making sure the upgrade is done now in isolation because the combination of those changes requires fixes in core to accommodate, and we can merge them now rather than surprising a future maintainer.