In a continious integration processes, for some applications, for testing purposes, it's useful to run vanilla IRIS and run integration tests, for Python applications for instance
And the best way to do it, is to use services feature in popular CI's. This feature can be used to start any published docker image, and integration tests may use it.
But unfortunately, running IRIS that way is completely useless, as it requires changing the password. In most of the world, and those platforms offers, to use environment variables to setup the database.
GitHub https://docs.github.com/en/actions/using-containerized-services/about-service-containers
Gitlab https://docs.gitlab.com/ee/ci/services/
Thank you for submitting the idea. The status has been changed to "Future consideration".
Stay tuned!
0
Future consideration
And even so, I see no reasons of using PasswordHash at all, in any scenarios, for me it looks like completely useless idea, and also for some reasons, InterSystems decided to deliver this tool separately only as a docker image.
When the world goes one way, IRIS looks like lives in another universe, with a different rules, and developers should find a ways, how to fit it here
we can discuss on DC
https://community.intersystems.com/post/iris-service-continuous-integration
How PasswordHash will help?
I need to run vanilla docker image with IRIS, in a cloud environment, where I have almost no control, only docker image name, and can pass environment variables, that's it
You mean, use some one more external image, to generate hash, and how I would use it?
I understand the convenience with environment variable, but why PasswordHash is not enough?