Support a global configuration file

[canny]

Currently, each project must specify both the Pact Broker (or Pactflow) host and any credentials to publish or retrieve pacts.
It would be nice to have a utility (similar to aws configure or travis init) that creates a global config file (e.g. ~/.pact/config) where this data can be stored once and is understood by all of our CLI tools and test frameworks.
This isn't as much of a problem for CI/automation, but it is particularly acute for setting up developers in large scale teams.

https://pact.canny.io/admin/board/feature-requests/p/support-a-global-configuration-file

[canny]

This issue has been linked to a Canny post: Support a global configuration file 🎉

[YOU54F]

Beth - January 19, 2020

Does anyone think there would be a need for having multiple broker profiles? Or perhaps, being able to override the ~/.pact/config by putting a file in the project's local directory.

Matt Fellows - January 20, 2020

Beth: Good question. There is prior art again with the AWS_PROFILE concept. I ran into this issue with npm in the past where a private npm registry couldn't be configured whilst also using the public one.
I'm not sure how often people will have to deal with multiple brokers simultaneously though? (please prove me wrong people!)