Skip to content
This repository has been archived by the owner on Jul 12, 2023. It is now read-only.

Make e2e-runner publish a real client #1850

Merged
merged 1 commit into from
Feb 22, 2021
Merged

Conversation

sethvargo
Copy link
Member

This gives us all the JSON parsing + automatic fallback and nice error messages when something fails. This commit changes the required configuration for KEY_SERVER from the full URL to the /publish endpoint to just the URL to the key server. Where previously you may have configured KEY_SERVER=https://foo.bar/v1/publish, please re-configure with KEY_SERVER=https://foo.bar. The system attempts to maintain backwards compatibility by parsing the URL, but this may be removed at a later date.

Release Note

Upgrade e2e-runner's HTTP client. This changes the required configuration for `KEY_SERVER` from the full URL to the `/publish` endpoint to _just_ the URL to the key server. Where previously you may have configured `KEY_SERVER=https://foo.bar/v1/publish`, please re-configure with `KEY_SERVER=https://foo.bar`. The system attempts to maintain backwards compatibility by parsing the URL, but this may be removed at a later date.

This gives us all the JSON parsing + automatic fallback and nice error messages when something fails. This commit changes the required configuration for `KEY_SERVER` from the full URL to the /publish endpoint to *just* the URL to the key server. Where previously you may have configured `KEY_SERVER=https://foo.bar/v1/publish`, please re-configure with `KEY_SERVER=https://foo.bar`. The system attempts to maintain backwards compatibility by parsing the URL, but this may be removed at a later date.
@googlebot googlebot added the cla: yes Auto: added by CLA bot when all committers have signed a CLA. label Feb 22, 2021
@sethvargo
Copy link
Member Author

The goal here is to remove all instances of:

invalid character '<' looking for beginning of value

which sporadically occur across environments. Our best guess is that the server is sometimes sending an HTML response when it should be sending JSON, however, we don't know the actual response body. We have logic for handling this edge case in the clients package, but the e2e runner was not using the clients package to interact with the key server.

@google-oss-robot
Copy link

@mikehelmick: changing LGTM is restricted to collaborators

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@google-oss-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mikehelmick, sethvargo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mikehelmick
Copy link
Contributor

/lgtm

@google-oss-robot
Copy link

@mikehelmick: changing LGTM is restricted to collaborators

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sethvargo
Copy link
Member Author

/lgtm

@google-oss-robot
Copy link

@sethvargo: you cannot LGTM your own PR.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@google-oss-robot google-oss-robot merged commit 2506813 into main Feb 22, 2021
@google-oss-robot google-oss-robot deleted the sethvargo/e2e_client branch February 22, 2021 16:58
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes Auto: added by CLA bot when all committers have signed a CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants