There's also a new web/sites/default/config/field.field.node.article.body.yml file.
Suggested path forward:
Delete README.txt
Change the empty values in brightcove.brightcove_api_client.nsf_brightcove.yml to SECRET
Change the value in scheduler.settings.yml to SECRET and inject it from an env var rather than generating it dynamically
Similarly, pull in an admin email from an env var for update.settings.yml
The remainder of the config changes appear to be coming from updating Drupal. The majority we should probably keep (i.e. commit to the code base). A handful (perhaps including field.field.node.article.body.yml) can be deleted after installing Drupal, but before synchronizing configs.
Acceptance criteria
[ ] Running export on a fresh install shouldn't change any config files
User story
As a site developer, I want to see as few config diffs as possible so that my commits are concise.
Currently, if we do a fresh install locally and then run
we'll get several changes to our configs (as evident in
git diff
). Some of these are easy to explain, some less so.There's also a new
web/sites/default/config/field.field.node.article.body.yml
file.Suggested path forward:
README.txt
brightcove.brightcove_api_client.nsf_brightcove.yml
to SECRETscheduler.settings.yml
to SECRET and inject it from an env var rather than generating it dynamicallyupdate.settings.yml
field.field.node.article.body.yml
) can be deleted after installing Drupal, but before synchronizing configs.Acceptance criteria