I am working on trying to automate the deployment of an Ignition Gateway to an EC2 instance but I am facing a few hurdles I haven’t been able to solve successfully yet.
Here is what I am doing that works:
- Docker container from ignition official image latest
- GitHub actions using Teraform to deploy the infra and run the docker deploy
After that I hit a couple of hurdles I am not sure of how to overcome
There is no way to setup and enable an API key during the docker deployment as far as I can tell. There is also no way to do the configuration settings during the docker deploy either beyond the very basic of setting up the username, password and a couple of other very basic things.
I then tried creating a local docker deployment, manually creating the API key and having a backup image that already has that but is basically unconfigured other than that. I managed to get that to deploy, but the API key loses it’s Administration setting and it seems the hash changes when the backup is restored, the API key is therefore useless for this purpose.
I was trying to avoid modification of config.idb directly but I don’t see another option.
I know - you’re asking why in the world this matters and why anyone would try and do this. The answer to that is that the edge gateways may eventually need to be a fully automated install on the local machines that are the local HMIs and I may not always be able to be available to do the install. I need to be able to create a deployable package for the edge gateways that can self-configure during deployment by personnel that are unlikely to have the necessary skills to do all of the configuration.
Anyone have any ideas on this?