Rebar.lock doesn't include dependencies from prod profile?

Except that I don’t want these dependencies except at (released, deployed, production) runtime. They’re various observability/metrics things that don’t work locally. I was hoping to avoid pulling them when they’re not gonna be used.

documentation

Sigh. OK.

The problem with that suggestion is that the relx block needs to go inside the prod profile, otherwise Rebar3 shell tries to run applications from relx block?

I think rebar4 needs to have better profile management, with an explicitly supported release, prod, production profile or whatever.