Operations feeds endpoint fails when called without data_type filtering

[davidgamez]

Describe the bug

After GBFS is present on the DB, /v1/operations/feeds fails while parsing the feeds information

Steps/Code to Reproduce

1. Use the following curl command, replacing the token and function_url with the appropriate values

curl --request GET \
  --url 'https://<<function_url>>/v1/operations/feeds?offset=1&limit=100' \
  --header 'Authorization: Bearer <<token>>'

Expected Results

All feeds are returned from the proper limit and offset.

Actual Results

The following error is returned:

{
  "detail": "Internal server error: Unsupported feed type: gbfs"
}

Screenshots

No response

Files used

No response

Additional notes

No response

[emmambd]

@davidgamez @AlfredNwolisa I am still getting this bug post-release: #1112

[davidgamez]

@davidgamez @AlfredNwolisa I am still getting this bug post-release: #1112

Let's fix #1152 I'm having issues getting all feeds due to the future status

[davidgamez]

Working as expected in v1.8.1