Open lavocatt opened 2 weeks ago
My intuition is telling me that this might be because when we work with the dev environment we are running the version 0.0.21 of the dynamic plugin sdk, but when we run in prod, the dynamic plugin sdk is running the version 1.x.x
I'm trying to update the dynamic sdk version on my branch to see if I can get to reproduce these issues in dev mode. That would be a good start.
Intuition was correct! I can reproduce the bugs in dev now. I'm opening a draft PR to track the progress on the matter.
For 4.15, react-router also needs to get updated.
I've been running tests against 4.12 and our production build is working fine:
4.14 also works well
After a more thorough exploration it seems like this is due to the react-router library. We're using an outdated version of it. We must upgrade it.
There is something going on with the production build that we need to understand and hopefully fix before the demo.
On the production build it is impossible to list the broker pods of a deployed broker
Even though the pod is running fine and the status says "ok":![image](https://github.com/artemiscloud/activemq-artemis-self-provisioning-plugin/assets/86971992/48382226-5421-40bf-825a-c6e86e880c2a)
On the production build, upon creating a broker, the namespace selection is broken