Great article!

For cases, where you don't want to share the source at all (even if it's immediately deleted), the following approach would work:

1. On your system (with source code) execute:

set p=##class(%Studio.Project).%New()
do p.AddItem("WH.Color.cls")
do p.AddItem("WH.Size.cls")
do p.DeployToFile("c:\test\app.xml",,1)

It will create an XML export with object code only and no source code included.

2. Transfer the file into a target system and execute:

set sc=##class(%Studio.Project).InstallFromFile("c:\test\app.xml")

APPCODE must be RO if you want to leave it in the container to be replaced as a part of the container.

Up to $zstorage size.

Great article!

Some notes:

1. SQL grants should be granted in a namespace with an SQL object.
2. SQL grants can be granted only to users and roles that exist.

If you log $lts(OutBoundlist) do you see the expected list?

Looks great. Where's the source for copy-data.py?

Can you run: do $system.Python.Shell() on a server?

Route to two BOs ("Normal" and "High" priority) with different FailureTimeout. Use SDS to keep other settings in sync.

I highly recommend using Source Control and automated CICD pipelines and restricting manual access. This is the only way to forget about this type of issues altogether.

Still, here's how you can compare code on two servers.

Calling @Dmitry.Zasypkin.

Add a header field to your request in the form of Authorization: Basic <credentials>, where credentials is the Base64 encoding of username and password joined by a single colon :.  

What can be recommended?

Fixing memory leaks if you see your running jvm process consuming more and more memory.

Use CheckAddressExist:

w ##class(%SYSTEM.INetInfo).CheckAddressExist(ip)

Tried to reproduce on RHEL9, but I got the test value, same as @Jeffrey.Drumm.

Are you actually not getting the TEST env var? Or some other env var? IRIS process overwrites some env vars on start