ironic/releasenotes/notes/fix-fields-missing-from-next-url-fd9fddf8e70b65ea.yaml

---
fixes:
  - |
    Fixes issue where the resource list API returned results with requested
    fields only until the API ``MAX_LIMIT``. After the API ``MAX_LIMIT`` is
    reached the API started ignoring user requested fields. This fix will make
    sure that the next url generated by the pagination code will include the
    user requested fields as query parameter.
Do not ignore 'fields' query parameter when building next url When an user calls the GET on an ironic resource it returns MAX_LIMIT number of resources at a time along with a next url. The default MAX_LIMIT is 1000. If the user requested specific set of fields from ironic API using the fields query parameter (eg: /v1/resource?fields=f1,f2,f3) The next url returned by the API ignores fields query parameter. This results in fields missing from the results after MAX_LIMIT is reached. This change fixes this problem by passing the fields as parameter to collections.get_next method and using the fields argument to build the query parameter. Change-Id: I62b59e8148171c72de0ccf63a1517e754b520c76 Story: 2006721 Task: 37093 2019-10-14 16:00:34 -07:00			`---`
			`fixes:`
			`- \|`
			`Fixes issue where the resource list API returned results with requested`
Fix up release notes for 14.0.0 Change-Id: I10286c48ddf3b7fba020db6175d5faa1c0911141 2020-02-07 16:27:17 +00:00			fields only until the API ``MAX_LIMIT``. After the API ``MAX_LIMIT`` is
			`reached the API started ignoring user requested fields. This fix will make`
			`sure that the next url generated by the pagination code will include the`
			`user requested fields as query parameter.`