Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2200

Setting a static variable via maxctrl gives a non accurate error message "Unknown global parameter"

    XMLWordPrintable

    Details

      Description

      I think an existing but static variable should give a different error when tried to be set dynamically, what we have now is:

      $ maxctrl -u user1 -p 123 -h 127.0.0.1:8989 alter maxscale log_augmentation 1
      Error: Server at 127.0.0.1:8989 responded with status code 403 to `PATCH maxscale`:{
          "errors": [
              {
                  "detail": "Unknown global parameter: log_augmentation=1"
              }
          ]
      }
      

      Same message as with a totally non-existing parameter:

      $ maxctrl -u user1 -p 123 -h 127.0.0.1:8989 alter maxscale something_random 123
      Error: Server at 127.0.0.1:8989 responded with status code 403 to `PATCH maxscale`:{
          "errors": [
              {
                  "detail": "Unknown global parameter: something_random=123"
              }
          ]
      }
      

      Also error message perhaps could be formatted better, e.g.:

      Error: Server at 127.0.0.1:8989   Code 403 : "Unknown global parameter: something_random=123"
      

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            claudio.nanni Claudio Nanni (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration