You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2022. It is now read-only.
We are using github action for waypoint and we are gettin the below error
Error: Failed to fetch version metadata file Error: unsupported media type requested, only [application/vnd+hashicorp.releases-api.v0+json application/vnd+hashicorp.releases-api.v1+json] are available
Here is the step where we are getting this error.
steps:
- uses: actions/checkout@v2
- name: Deploy Waypoint
uses: hashicorp/action-setup-waypoint@main
with:
version: "0.8.2"
- run: waypoint init
The same error is happening on the tests on this repo:
The weird thing with this issue is that it is very inconsistent for us. It just started a few days agos. Sometimes re-deploying works fine, other times you wait an hour or two.
I also ran into the same issue. I created a fork from the PR for #301 and added the missing Accept header. Assuming Hashicorp starts accepting PRs. I'll make a proper PR for it. Until then, you can use the fork.
This is not currently actively maintained by the Waypoint team. We may revisit it in the future, but in the interest of clarity, we will archive this project.
We are using github action for waypoint and we are gettin the below error
Error: Failed to fetch version metadata file Error: unsupported media type requested, only [application/vnd+hashicorp.releases-api.v0+json application/vnd+hashicorp.releases-api.v1+json] are available
Here is the step where we are getting this error.
steps:
- uses: actions/checkout@v2
- name: Deploy Waypoint
uses: hashicorp/action-setup-waypoint@main
with:
version: "0.8.2"
- run: waypoint init
The same error is happening on the tests on this repo:
https://github.com/hashicorp/action-setup-waypoint/runs/6479406538?check_suite_focus=true
The text was updated successfully, but these errors were encountered: