We have experienced issues with Craft updates since the project config feature was released. Typically we run a multi-node application cluster that auto-scales up/down as needed. The current theory on what's going wrong is that if we have changes to make during the course of an update (ie, configuration, enabling modules, etc) we'd make those changes and they would likely be applied to only one node in the cluster and never sync to the other nodes.
How are other people solving this? I don't see recommendations in the official Craft documentation but I can envision two possibilities:
- Commit all changes to project config and only rely on deploys to put it in place.
- Create a shared mount point for project config so that all nodes read from the same configuration.
Any other ideas? Any officially blessed approaches here? I'm betting #1 is preferred.