Add environment file flag to CLI

[colophonemes]

Adds an additional option --environment-file which allows the user to override the path to the default environment file and specify their own path.

This is useful if it's cleaner to keep your environment file somewhere other than the default, or if you need to specify multiple environments (e.g. in a monorepo that targets several different Contentful spaces).

[colophonemes]

Ping @stevenpetryk – if this is unlikely to land that's fine, but it'd be useful to know if we need to create our own fork.

[stevenpetryk]

Hey @colophonemes, I actually don't work at Intercom anymore, so I don't have access to this repo. I'll reach out to old colleagues and flag this to them.

[colophonemes]

Ah sorry, I didn't realise – thanks for offering to reach out, much appreciated.

[rafapaulin]

Why this one did not get merged?

[GabrielAnca]

Hi 👋🏻 I'd be happy to have something like this, I think adding flexibility would be great. In order to merge this we'd need:

• [ ] Rebase to solve the conflicts
• [ ] Rename the commit according to semantic release format: https://github.com/semantic-release/semantic-release#commit-message-format
• [ ] Add a test for this functionality 😄

[colophonemes]

I've since moved on from this, but anyone else is welcome to create a new PR based on my work here.

For the record, I ended up using https://www.npmjs.com/package/contentful-ts-generator, though not sure how the projects compare any more.