Implementing Azure Key Vault for secure secrets as well as local configuration file

[ConstantineK]

• Functionality to store/load azure secrets.
• Blog post on setting up the AKV (since its probably not going to cross accounts if it requires azure ad.)
• Check if local file exists and if not attempt to load azure secrets, and die if all processes fail.
• Has to work with existing pester testing.

[mkellerman]

Keep in mind that we will need to store multiple ApiKey's and Token's to do a full scope of tests.

[mkellerman]

Can you please start with the local configuration file, so we can move towards that locally for now?

[ConstantineK]

Sounds good - I was going to start there anyway since I am not sure yet which configuration items would need to be stored (besides the most obvious ones), going to look at the relevant code and isolate the needed pieces first, test that it works, then start poking at the cloud.

[mkellerman]

Right now, all we need are these:

$OAuthSettings = @{
  ApiKey = $env:ApiKey
  ApiSecret = $env:ApiSecret
  AccessToken = $env:AccessToken
  AccessTokenSecret =$env:AccessTokenSecret
}
Set-TwitterOAuthSettings @OAuthSettings

But multiple sets of them.

[mkellerman]

[Suggestion] Instead of managing 4 different keys per group, we could make a single key.

ApiToken = "${env:ApiKey}:${env:ApiSecret}:${env:AccessToken}:${env:AccessTokenSecret}"

Or a JSON object, so it's the same as the config.json file?

$ApiToken = '{"ApiKey":"111","ApiSecret":"111","AccessToken":"111","AccessTokenSecret":"111"}'

[mkellerman]

Did anyone look into this?

#34 has been submitted to use XML file for config. Can someone comment and help with review?

[mkellerman]

Closing.. no activity.