Maybe it would be possible to add additional console log when solace event broker is ready for configuring ?
For now we’re searching for “Primary Virtual Router is now active” on /usr/sw/jail/logs/system.log which is making waiting complicated (executing grep/cat on this file in a loop instead of waiting for console log).
Hi @Tomasz ,
Can you share more about what you’re trying to do here? Is this for manual configuration or automated via your CI/CD pipeline?
We need some additional information to be able to determine when we can execute solace configuration using cli.
You can see the example here:
testcontainers-java/SolaceContainer.java at main · testcontainers/testcontainers-java
Testcontainers is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker containe… For now we are checking system.log file in a loop to verify solace readiness and then we’re executing configuration script.
Interesting, but if we were to write something to the console wouldn’t you now just be checking the console output in a loop for a different message? or does testcontainers have some sort of built-in support that handles that?
Veryfing console log is already implemented on testcontainers and this can be used (with this new information) as a container wait strategy.
But this information can be useful even for standard solace setup (using docker container for example) - to show the time when user can manually configure solace.