Brownie configuration structure mismatch

[zivkovicmilos]

Description

The current go specification that is used to unmarshal Brownie configuration YAML files does not conform to the official Brownie configuration file layout:

tenderly-cli/providers/deployment_provider.go

Lines 22 to 30 in edaae48

	type Config struct {
	ProjectDirectory string `json:"project_directory" yaml:"project_directory"`
	BuildDirectory string `json:"contracts_build_directory" yaml:"build_directory"`
	Networks map[string]NetworkConfig `json:"networks" yaml:"-"`
	Solc map[string]Optimizer `json:"solc" yaml:"solc"`
	Compilers map[string]Compiler `json:"compilers" yaml:"compiler"`
	ConfigType string `json:"-"`
	Paths Paths `json:"paths" yaml:"paths"`
	}

The Brownie config is currently unmarshalled into this structure here.

Proposed solution

Currently, I have a draft PR that includes a Brownie configuration read test, but doesn't modify the common Config structure.

The obvious solution here would probably be to create a separate configuration structure for each provider, because they can have subtle differences, and use that.

Should I open a separate PR that standardizes these configuration reads?

@delta003 @Riphal @mspuz