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
We've just added this plugin to our Backstage instance and are able to see our CircleCI jobs in Backstage but when clicking into a job the build logs fail to load.
What I believe is happening is that the request to get the build details succeeds because it goes through the backend proxy, but this request then returns a direct link to the build logs which looks something like this:
This output_url is then fetched straight from the browser instead of going via the backend proxy. This then fails as the endpoint isn't CORS enabled.
This request should instead be proxied through the backend like the other API calls to avoid the CORS issue. Of course an alternative solution would be to enable CORS on that endpoint but I'm not sure if that is the best option.
The text was updated successfully, but these errors were encountered:
Hello Contributors, @EricRibeiro and @KyleTryon, we are experiencing this issue with the current version v1.1. Is there any update on this matter? We are encountering a CORS error when attempting to open the build logs. Requests should be proxied through the backend, similar to other API calls, to avoid the CORS issue.
Please let us know what the best alternative solution would be to address this problem. Thank you.
We've just added this plugin to our Backstage instance and are able to see our CircleCI jobs in Backstage but when clicking into a job the build logs fail to load.
What I believe is happening is that the request to get the build details succeeds because it goes through the backend proxy, but this request then returns a direct link to the build logs which looks something like this:
This output_url is then fetched straight from the browser instead of going via the backend proxy. This then fails as the endpoint isn't CORS enabled.
This request should instead be proxied through the backend like the other API calls to avoid the CORS issue. Of course an alternative solution would be to enable CORS on that endpoint but I'm not sure if that is the best option.
The text was updated successfully, but these errors were encountered: