Skip to content

Conversation

@ethanndickson
Copy link
Member

@ethanndickson ethanndickson commented Nov 18, 2025

Fixes #20781

Previously, when GetProvisionerKey() failed, the actual error was swallowed:

error: unable to get provisioner key details

Now the actual error is preserved using error wrapping, so users can see the real cause (e.g., 404 Not Found, connection refused, invalid key, etc.):

error: unable to get provisioner key details: GET https://...: 404 Not Found

This makes it much easier to diagnose configuration issues.


Generated by mux

…details

Previously, when GetProvisionerKey() failed, the actual error was
swallowed and replaced with a generic 'unable to get provisioner key
details' message. This made it very difficult to diagnose issues
such as missing URLs, authentication failures, or network problems.

Now the actual error is preserved using error wrapping, so users can
see the real cause of the failure (e.g., 404 Not Found, connection
refused, invalid key, etc.).

Fixes #20781
@ethanndickson ethanndickson changed the title fix(provisioner): preserve actual error when getting provisioner key details fix(enterprise/cli): preserve actual error when getting provisioner key details Nov 18, 2025
@ethanndickson ethanndickson merged commit c12bba4 into main Nov 18, 2025
42 checks passed
@ethanndickson ethanndickson deleted the fix-provisioner-error-clarity branch November 18, 2025 15:09
@github-actions github-actions bot locked and limited conversation to collaborators Nov 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(provisioner): unclear error when not passing provisioner key details

3 participants