Increase the length for parameters that expect a list of domain IDs.#5763
Conversation
Currently, when updating a service offering there is a limitation of the number of domains the offering can be updated. Multiple domain ids lead to the following API error: Error: (HTTP 431, error code 9999) Unable to execute API command updateserviceoffering due to invalid value. Value greater than max allowed length 255 for param: domainIds"
|
Aren't these calls also affected?
They all have the 'domainid' parameter which probably needs to be updated as well. These can all be assigned to multiple domains. |
|
@wido you are right.
However, I did not add the parameter changes in: I will update the PR adding for this call as well. |
|
@wido just updating that updateBackupOffering does not have domain IDs; therefore, it does not need changes. |
|
@blueorangutan package |
|
@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1888 |
|
@blueorangutan test |
|
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-2656)
|
|
code LGTM |
Test failure ^^^ is not related to the changes in this PR. |
) Currently, when updating a service offering there is a limitation of the number of domains the offering can be updated. Multiple domain ids lead to the following API error: Error: (HTTP 431, error code 9999) Unable to execute API command updateserviceoffering due to invalid value. Value greater than max allowed length 255 for param: domainIds"
Description
This PR proposes setting a length for domain id parameters that allow passing a list of UUIDs separated by a comma. Allowing to run the API command in use-cases where there are many domain admins.
Currently when calling API command with multiple domain ids (for example
updateServiceOffering) it leads to the following API error:I am targeting this implementation at 4.16.1.0 and considering it a bug due to the fact that we could not relly on the API to execute a few critical updates.
Admins end up either calling multiple times the API or (:warning: don't go this way) doing DB changes.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity