meta_server_tag is needed, when all BBB sesrvers are tagged

[cwaidelich]

Describe the bug
The description "When making a "create" API call towards Scalelite, you can optionally pass a meta_server-tag parameter with a string value. " under https://github.com/blindsidenetworks/scalelite/blob/master/docs/tags-README.md does not apply, when scalelite has one server configured and that server has a tag applied.

Calling the create API from BBB will return a "No server available" in case no meta_server_tag ist send.

To Reproduce
Create a Scalelite - BBB Construction. No Frontend needed.

Connect the Scalelite with a tag over either:
servers:add['bbb.domain.com', 'abc','1','BBB1']

or

servers:sync['/tmp/scalelite-backend-server-configuration.yaml','force']

with a file content similar to this:

servers:
bbb.domain.com:
secret: abc
enabled: true

Over API Mate, try to connect to scalelite with the following Call:

https://bbb.doamin.com/bigbluebutton/api/create?allowStartStopRecording=true&attendeePW=ap&autoStartRecording=false&meetingID=random-1659833&moderatorPW=mp&name=random-1659833&record=false&voiceBridge=76282&welcome=%3Cbr%3EWelcome+to+%3Cb%3E%25%25CONFNAME%25%25%3C%2Fb%3E%21&checksum=05d84495b09b3c3b35c1398211832fdcf7819e3f

You wiill see a No servers found response

Deployment:
Running Scalelite Services, Redis and Postgres in one big Compose.yml.
We are our own trust certificated network.
If you need specific informations, please ask.

None of the logs gave any output of the error.

Expected behavior
API Mate Response:

SUCCESS random-1659833 7b31cbade3b947e01b68b8332a51ee94b7468a4f-1740490825834 bbb-none ap mp 1740490825834 177717297 613-555-1234 Tue Feb 25 13:40:25 UTC 2025 false 0 false

[Ithanil]

Why would you use a tag if there is only a single server? A tagged server will never be selected for a create call without a tag specified, that's how the feature is built. Please read the description and examples carefully:

NOTE: Create calls without or with ''/'!' as meta_server-tag will only match untagged servers. So, for a frontend unaware of the feature, SL will behave as previously if a pool of untagged ("default") servers is maintained. It is recommended to always add your default servers as untagged servers.