Incorrect API endpoint for Harness OnPrem- pipelines/execution
Closed this issue · 2 comments
Expected Behavior
Expected the correct API Endpoint
Actual behavior
Endpoint does not work.
Context
See code
The following is implemented:
const response = await fetch(
`${await backendBaseUrl}/harness/gateway/pipeline/api/pipelines/execution/v2/summary?${query}`,
{
method: 'POST',
},
);
According to the API spec it should be:
const response = await fetch(
`${await backendBaseUrl}/harness/gateway/pipeline/api/pipelines/execution/summary?${query}`,
{
method: 'POST',
},
);
Hey Travis - thanks for the bug report! @Debanitrkl @sandeepa-kv-jois can you please take a look? If the API endpoints are different for on-prem, we should have separate calls based on whether or not Harness is hosted on app.harness.io
.
Hi @travismgibson, so looks like this API endpoint issue that you were facing is due to the pipeline services not being updated to the latest one on the on-prem version you're using.
The usage of v2 endpoints, is quite new(~3 months old) and was recently added.
An update to the recent version of on-prem release would solve this issue of yours, marking it as not a bug for plugin side of things.
Thanks