In the token substitution part, there was some confusion on whether it was working - we figured it out, but would have been easier if we had some more logging in the pipeline step for token substitution. We don't want to list the secrets, but we could list out the property name (logger.namedvalue.) that had an override, and the total number of overrides. This way when the user runs the pipeline, they can clearly see in the log (github/azure devops) on whether their secret was picked up properly for token substitution.
In the token substitution part, there was some confusion on whether it was working - we figured it out, but would have been easier if we had some more logging in the pipeline step for token substitution. We don't want to list the secrets, but we could list out the property name (logger.namedvalue.) that had an override, and the total number of overrides. This way when the user runs the pipeline, they can clearly see in the log (github/azure devops) on whether their secret was picked up properly for token substitution.