Great questions! By "silently" / "unattended," do you mean non-interactive in the sense that you are using scripts / automation / infrastructure-as-code etc. to install or upgrade Connect?
It is unfortunate that our documentation does not make this pattern super clear. I am hopeful that we will soon get to a proper apt/yum repository, which will simplify this whole process considerably! In the meantime, the best place I know to reference is where we build our Docker containers:
I have to admit that we used to use the
installer.sh script in a non-interactive fashion and ran into enough trickiness / confusion that we went back to using the
.deb directly. For a non-interactive installation, sometimes that is easiest.
Unfortunately, it is not very pretty It is also potentially prone to issues in URLs changing / etc. Again, until we have an apt / yum repository, I think this is the best we have I hope that helps though!
If you can say any more about your use case, it would definitely help me present that case while we are looking to build the apt/yum repositories and simplifying this process for our own internal automation!
EDIT: it is worth noting that this approach requires more explicit choices with operating system, architecture, etc. The script mostly tries to abstract some of that annoyance away.