Bug #63018
open
to reproduce: https://gist.github.com/yuvalif/e4ab558dbed63fae18e28848be0bb49a
note that the right solution is to add the tenant name to the topic name when creating the name of the queue object.
however, doing that will create backward compatibility issues.
- when creating a new persistent topic, that did not exist before, this is ok to just add the tenant
- when handling the queues we just follow the names in the list of owned queues, so, there should not be any issue there
- when doing reserve/commit we should first add the tenant to the topic arn, to get the queue name, if we get ENOENT, we should create a new queue with the correct name, and use it
- when reading the stats in the admin command, we can probably first check for the name with the tenant, and then also look for the name without the tenat (and probably print a warning)
- when calling get topic in the admin command, we should also check for the name without the tenant, and print a warning if found
- we should add option to the "topic rm' command to delete the non-tenanted queue of tenanted topic
- Assignee set to Yuval Lifshitz
Also available in: Atom
PDF