built-in automation (nginx, mysql, and others) right now are used by about 6% of our customer base. As we've mentioned in a separate ticket, we do have plans to deprecate built-in automation because the absolute majority of our customers already using chef, ansible or just Scalr orchestration to orchestrate software without any limitations.
Adding new features as well as supporting new versions of built-in automation is extremely complex because we need to consider all possible combinations of Scalr and scalr-agent versions (all our enterprise customers using on-prem solution, and they can be 1-2 versions behind the current).
Right now we haven't decided yet on what is our level of support for build-in automation and what features we would add and what we don't before we officially deprecate built-in automation.
I must say that its very frustrating for me. We depend on Scalr and
changing the automation is going to be very difficult for us.
However for this specific issue there must be a simple workaround to add
the http2 setting to the nginx configuration.
If I understand correctly Scalr overwrites this setting. Is it possible to
write a script or something to add it on the server level without changing