Is DRY principle relevant for configuration

DRY (Don’t repeat yourself) principle is a valid one in many areas, as stated:

They apply it quite broadly to include “database schemas, test plans, the build system, even documentation

So it’s code related,so is it relevant for configuration?

Example I have properties file with duplicate values to control different brands label

BRAND1_AMOUNT=Amount BRAND2_AMOUNT=Amount BRAND3_AMOUNT=Amount BRAND4_AMOUNT=Amount BRAND5_AMOUNT=Amount

in pseudo code I don’t repeat myself, for example

  getProperty(getBrand() + "_AMOUNT") 

Am I failing to use DRY principle here, or is configuration duplications is irrelevant/less significant/non-issue in this principle?