Hi @Kathy Satterlee Thank you for the quick answer. I knew somebody was going to ask “why not fleetctl” 🙂 . I just didn’t want to get in to details to just get the answer.
Short version is, it is an option, but more work than adding an env variable flag would have been.
Longer version: <waves hands vaguely towards automation, CI/CD pipeline, docker compose image that passes command line flag env variables, and doesn’t have fleetctl installed on build machine> Yeah, I could add fleetctl to the build machine with docker and run it after docker has started fleet, but if there were an env variable flag to do this, it would be a one line change to the compose file. And ultimately, it turns out none of this was needed since “Software Inventory” now defaults to “on”.
Our instance didn’t have it on (i used fleetctl to enable it) and we wanted to make sure if we ever had to rebuild from scratch that change wouldn’t be lost. Infrastructure as code, and all that.