The INFO logging that AttributeDefinition generates when a deprecated attribute is used needs to be configurable, i.e. with a boolean flag so a dev can turn it off for attributes where it serves no purpose.

The logging only serves a purpose if an admin can take action to use some alternative config. If an attribute is deprecated only because in some future release it will go away, but there's no replacement now, the logging is just noise.

The log message itself should be improved:

1) Get rid of the ! at the end. It's not that exciting.
2) Include the address of the resource
3) Point the user at the read-resource-description output from which they can learn more about the deprecation.