Retrieve fields_to_replace.json contents from S3 bucket.

[mcdonnnj]

🚀 Feature Proposal

Retrieve JSON mapping old/new fields from S3 bucket using a helper script instead of bundling it in the repository.

Motivation

Keeping a version of the fields_to_replace.json file in the repository ties changes to deployment to changes in the repository which I feel should be decoupled.

Example

You would call the script with a given bucket and file name. The remote file would be retrieved and saved as fields_to_replace.json locally to integrate with the existing workflow for packaging.

Pitch

I would like the configuration provided by fields_to_replace.json to be decoupled from the repository. After discussion with @dav3r we settled on retrieving a configuration from S3 which mirrors the way we store some of our configuration files.

[mcdonnnj]

Rendered moot by current configuration.