Related to #630.
We can set extra configuration via TempoStack's spec.extraConfig.tempo. However, if we define the connection to azure blob storage this way, so that we can set use_federated_token as per the documentation, the operator complains that spec.storage is not valid.
Alternatively, trying to set use_federated_token via the secret is also invalid, as the operator checks for the existence of the account_key key in the secret.
Related to #630.
We can set extra configuration via
TempoStack'sspec.extraConfig.tempo. However, if we define the connection to azure blob storage this way, so that we can setuse_federated_tokenas per the documentation, the operator complains thatspec.storageis not valid.Alternatively, trying to set
use_federated_tokenvia the secret is also invalid, as the operator checks for the existence of theaccount_keykey in the secret.