Skip to content

Fix recorder defaults#24399

Merged
andrewsayre merged 2 commits into
devfrom
recorder-defaults
Jun 8, 2019
Merged

Fix recorder defaults#24399
andrewsayre merged 2 commits into
devfrom
recorder-defaults

Conversation

@balloob
Copy link
Copy Markdown
Member

@balloob balloob commented Jun 8, 2019

Breaking Change:

We used to have a bug that caused users that did not specify recorder: in their configuration (probably most of you), to not have their database automatically purged. This will start happening now as per the default settings. This might take a while the first time as it hasn't done any clean up in a while.

Description:

If the recorder integration was loaded as a dependency of another integration, the default config was not being applied. This is probably the case for 95% of our users.

This means that we never purged old DBs 🙈

Adding breaking change to clarify what is going on.

Related issue (if applicable): fixes #24386

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

Comment thread tests/components/recorder/test_init.py
@balloob balloob force-pushed the recorder-defaults branch from 97eac06 to 19d22c3 Compare June 8, 2019 20:55
@andrewsayre andrewsayre merged commit 848a2a9 into dev Jun 8, 2019
@delete-merged-branch delete-merged-branch Bot deleted the recorder-defaults branch June 8, 2019 23:18
@balloob balloob mentioned this pull request Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Recorder component] Default purge settings ignored?

4 participants