Great improvements! Looking forward to it, Bob.

Hi Pietro,

I love these type of tools as they shed so much light in otherwise dark corner of our systems.

Great job and thank you very much for sharing this!

Another amazing and rich contest :-) Thank you amazing team! Looking forward to the submissions!

Whoahoo! Thanks for sharing it @Muhammad Waseem

holy cow #2 :-) so much precious info on this thread!

Nice work @Evgeny Shvarov those typical things you want to do quickly and never remember and have to read the docs :-)

There are already many useful suggestions and tools on display here... amazing community! Thank you!

Looking forward to this one! ;-)

Nice work on the containers side @Bob Kuszewski !

Already liking Codespace a lot and the new AI direction Microsoft/Github is working with. I think that is the future as per ChatGPT shows & now with a well presented article for ObjectScript (thank @Dmitry!) what is there not to like? So many options!

There are some reasonable enhancements in there. Thank you Dmitry.

Hi Dmitry,

Again, thanks for pointing things out. Let me comment on a couple of things as you so strongly say that you do not recommend the facility provided.

The first thing is that the %Installer although it still work it is out of sync with internal classes. It is also cumbersome to feed it through in a declarative way to an IRIS instance. The hope with the CPF merge and its actions is to provide a more modern tool that fits with modern, declarative, gitops paradigms. The third is that containers forces us to think about the distinction between build and run phases and the CPF merge is definitely into the injection of configuration at the run phase. To that point, the actual ```iris merge``` was added later for organizations working with VMs that still want to supply a CPF Merge so that they can more adequately adhere to a declarative approach with tools like Ansible, CloudFormation etc. As I said, we use it daily in the cloud to configure just about anything we need. I know we can now go down a rabbit hole and chase my-use case vs yours so I shall leave it at it and I hope you can understand the intention.

I think we can probably fix the error code returned that comes from within IRIS just like anything else we call as we perform the merge.

It would be good to hear other feedback and what other features we should implement and we hope to hear from a wider audience too.

Hi Dmitry,

Thanks for trying out the CPF merge utility. I am sorry to hear you found it not very useful because in many areas, especially cloud compositions we use it daily, it's of declarative nature and just aids in just about anything we do with containers.

The utility was created to be indempotent so if you have a database or namespace and you run it again it won't create new resources so, yes, the process run successfully it just did not bother you telling you you made a mistake by submitting the same request twice.

For the password use the following container:

containers.intersystems.com/intersystems/passwordhash:1.1

HTH

First InterSystems IRIS Cloud use case! Whoahoo Thanks Ron Sweeney

Thank you for all those pictures Irene! They tell a story! :-)

This is amazing to my js-dated eyes. Congrats @Sean Connelly.

Q: Are we back to a full & tight integration & experience that we had in Studio? With BP support and all? Posterity will cast their vote on that but I see a clean unadulterated architecture and I think the option to add Python support so I think we are on a winner :-)

All the best Sean and thanks for sharing it.

Great resource for anybody @Yury - Thanks!

Good work and thanks for sharing it.

Thanks Bob for the timely post.