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
The GET locations by entity API call referenced here is always returning a 404 location not found error, even when we have verified the component exists and the location exists. The exact error we get is "Found no location with type component and target default/zzz-test".
After further investigation into Backstage's code, we believe the error is coming from line 148 in DefaultLocationStore.ts. It seems it is passing the entityRefString to the parseLocationRef method when it should be passing the locationKeyValue.
👍 Expected behavior
The GET location by entity API call should return the id, type, and target of a Location based on the kind, namespace, and name of an entity.
👎 Actual Behavior with Screenshots
404 error even when the data is verified to be correct.
👟 Reproduction steps
Make an API call to the catalog using the GET location by entity call: "/locations/by-entity/{kind}/{namespace}/{name}" and see that even when the inputs are correct it only returns a 404 error.
📃 Provide the context for the Bug.
No response
🖥️ Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?
📜 Description
The GET locations by entity API call referenced here is always returning a 404 location not found error, even when we have verified the component exists and the location exists. The exact error we get is "Found no location with type component and target default/zzz-test".
After further investigation into Backstage's code, we believe the error is coming from
line 148
inDefaultLocationStore.ts
. It seems it is passing theentityRefString
to theparseLocationRef
method when it should be passing thelocationKeyValue
.👍 Expected behavior
The GET location by entity API call should return the id, type, and target of a Location based on the kind, namespace, and name of an entity.
👎 Actual Behavior with Screenshots
404 error even when the data is verified to be correct.
👟 Reproduction steps
Make an API call to the catalog using the GET location by entity call: "/locations/by-entity/{kind}/{namespace}/{name}" and see that even when the inputs are correct it only returns a 404 error.
📃 Provide the context for the Bug.
No response
🖥️ Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: