Replacing this now means that anything expecting a brooklyn.entity.ConfigKey.HasConfigKey can no longer take an AttributeSensorAndConfigKey. I believe that's why the change hand't been made yet. Depends how long that deprecated code has been around for (and how long we want to support it) as to whether that's important.