@@ -11,7 +11,7 @@ If running in AWS Lambda, store the config in SecretManager in a secret named
1111` ckr-config ` .
1212
1313If running in GCP CloudFunctions, store the config in GCS, e.g. in
14- ` your_bucket/ckr-config.json ` , then set an env var
14+ ` your_bucket/ckr-config.json ` , then set an env var
1515` CKR_BUCKET_NAME=your_bucket ` .
1616
1717Otherwise, when running the binary or code directly, pop the config into
@@ -22,27 +22,29 @@ a file called `config.json` in `/etc/cloud-key-rotator/`.
2222For scraping of AWS key ages:
2323
2424``` json
25-
2625{
2726 "EnableKeyAgeLogging" : true ,
2827 "RotationMode" : false ,
29- "CloudProviders" : [{
30- "Name" :" aws"
31- }]
28+ "CloudProviders" : [
29+ {
30+ "Name" : " aws"
31+ }
32+ ]
3233}
3334```
3435
3536For scraping of GCP key ages:
3637
3738``` json
38-
3939{
4040 "EnableKeyAgeLogging" : true ,
4141 "RotationMode" : false ,
42- "CloudProviders" : [{
43- "Project" :" my-project" ,
44- "Name" : " gcp"
45- }]
42+ "CloudProviders" : [
43+ {
44+ "Project" : " my-project" ,
45+ "Name" : " gcp"
46+ }
47+ ]
4648}
4749```
4850
@@ -55,6 +57,7 @@ If you add a Datadog struct to the config, you can get `cloud-key-rotator` to po
5557 "MetricEnv" : " prod" ,
5658 "MetricName" : " cloud-key-rotator.age" ,
5759 "MetricProject" : " my_project" ,
60+ "MetricService" : " my_service" ,
5861 "MetricTeam" : " my_team"
5962 },
6063 "DatadogAPIKey" : " okj23434poz3j4o324p455oz3j4o324" ,
0 commit comments