Make CloudConfigurationManager.GetSetting("setting") less verbose
Each calls to CloudConfigurationManager.GetSetting("setting") generate garbage in the trace outputs. Its not necessary and very annoying when analysing output traces.
The simple statement CloudConfigurationManager.GetSetting("setting") generates this:
Getting "setting" from ServiceRuntime: FAIL.
Getting "setting" from ConfigurationManager: PASS (0).
Besides the obvious annoyance-factor this might also have security implications. The PASS-entry writes the actual value of the setting (e.g. a SQL or blob connection string) to the trace log which possibly exposes the data in an unwanted fashion (i.e. via log access or by hooking in a trace listener).
Could not agree more. At least allow us to independently configure the tracing level of the CloudConfigurationManager trace messages so we can turn these off without disabling tracing globally.