Skip to content

QueueName not correctly encoded in Solace PubSub+ Scaler #4936

@sueltschi-sbb

Description

@sueltschi-sbb

Report

The 'queueName' Value in https://keda.sh/docs/2.11/scalers/solace-pub-sub/ isn't URL decoded in https://github.com/kedacore/keda/blob/main/pkg/scalers/solace_scaler.go#L248

This leads to problems when a queue name contains a slash (e.g. messages/large) because it leads to an invalid path when calling the SEMP Rest API resulting in a "400 Bad Request" response.

A workaround for now is to manually URL-encode the queueName value

Expected Behavior

The queueName should be correctly URL-encoded

Actual Behavior

Queue names containing a slash lead to "400 Bad Request" responses from the SEMP endpoint

Steps to Reproduce the Problem

  1. create a queue containing a slash in the name (e.g. 'messages/large')
  2. create a solace-event-queue trigger for this queue
  3. observe that the trigger fails to execute with a "400 Bad Request" message

Logs from KEDA operator

No response

KEDA Version

None

Kubernetes Version

None

Platform

Red Hat OpenShift

Scaler Details

No response

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    Ready To Ship

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions