You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -43,7 +43,7 @@ Currently supported variable and secrets implementations:
43
43
44
44
The main driver is to use component level configuration objects, if stored in a `"namespaced"` manner e.g. in AWS ParamStore as `/nonprod/component-service-a/configVar`, however this is not a requirement and the param name can be whatever. Though whilst using some sort of a organised manner it will be more straight forward to allow other services to consume certain secrets/params based on resource/access policies.
45
45
46
-
> Beware size limitation with certain config/vault implementations. In which case it's best to split certain items up e.g. TLS certs `/nonprod/component-service-a/pub-cert`, `/nonprod/component-service-a/private-cert`, `/nonprod/component-service-a/chain1-cert`, etc...
46
+
> Beware size limitation with certain config/vault implementations. In which case it's best to split certain items up e.g. TLS certs `/nonprod/component-service-a/pub-cert`, `/nonprod/component-service-a/private-cert`, `/nonprod/component-service-a/chain1-cert`, etc...
47
47
48
48
Where `configVar` can be either a parseable string `'som3#!S$CRet'` or a number `3306` or a parseable single level JSON object like `{host: ..., pass: ...., port: ...}` which can be returned whole or accessed via a key separator for a specific value.
49
49
@@ -92,7 +92,7 @@ _An example token would look like this_
92
92
93
93
The `AWSSECRETS` the strategy identifier to choose the correct provider at runtime. Multiple providers can be referenced in a single run via a CLI or with the API.
94
94
95
-
This is not overrideable and must be exactly as it is in the provided list of providers.
95
+
This is not overrideable and must be exactly as it is in the provided list of providers.
The `/path/to/my/key` part from the [example token](#awssecretspathtomykeylookupinsideobjectmetadata) is the actual path to the item in the backing store.
109
+
The `/path/to/my/key` part from the [example token](#awssecretspathtomykeylookupinsideobjectmetadata) is the actual path to the item in the backing store.
110
110
111
111
See the different special considerations per provider as it different providers will require different implementations.
112
112
@@ -116,7 +116,7 @@ __THIS IS OPTIONAL__
116
116
117
117
The `|` symbol from the [example token](#awssecretspathtomykeylookupinsideobjectmetadata) is used to specify the key seperator.
118
118
119
-
If an item retrieved from a store is JSON parseable map it can be interrogated for further properties inside.
119
+
If an item retrieved from a store is JSON parseable map it can be interrogated for further properties inside.
120
120
121
121
### __Look up key__
122
122
@@ -154,7 +154,7 @@ See [examples of working with files](docs/examples.md#working-with-files) for mo
154
154
155
155
### TokenMetadataConfig
156
156
157
-
The `[meta=data]` from the [example token](#awssecretspathtomykeylookupinsideobjectmetadata) - is the optional metadata about the target in the backing provider
157
+
The `[meta=data]` from the [example token](#awssecretspathtomykeylookupinsideobjectmetadata) - is the optional metadata about the target in the backing provider
158
158
159
159
IT must have this format `[key=value]` - ITISOPTIONAL
160
160
@@ -199,7 +199,7 @@ The token itself must contain all of the following properties, so that it would
199
199
200
200
- Storage account name [`STORAGE_ACCOUNT_NAME`]
201
201
- TableName [`TABLE_NAME`]
202
-
- > It might make sense to make this table global to the domain or project
202
+
- > It might make sense to make this table global to the domain or project
203
203
- PartitionKey [`PARTITION_KEY`]
204
204
- > This could correspond to the component/service name
205
205
- RowKey [`ROW_KEY`]
@@ -230,7 +230,7 @@ when using Vault in AWS - you can set the value of the `VAULT_TOKEN=aws_iam` thi
230
230
231
231
The HashicorpVault functions in the same exact way as the other implementations. It will retrieve the JSON object and can be looked up within it by using a key separator.
Lorem Ipsum is AWSPARAMSTR:///djsfsdkjvfjkhfdvibdfinjdsfnjvdsflj <= in middle of sentencenot simply random text.
429
-
It has roots in a piece of classical Latin literature from 45
429
+
It has roots in a piece of classical Latin literature from 45
430
430
BC, making it over 2000 years old. Richard McClintock, a Latin professor at
431
431
Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, c
432
432
onsectetur, from a Lorem Ipsum passage , at the end of line => AWSPARAMSTR:///djsfsdkjvfjkhfdvibdfinjdsfnjvdsflj
433
433
and going through the cites of the word in c
434
434
lassical literature, discovered the undoubtable source. Lorem Ipsum comes from secti
435
435
ons in singles =>'AWSPARAMSTR:///djsfsdkjvfjkhfdvibdfinjdsfnjvdsflj'1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil)
436
436
in doubles => "AWSPARAMSTR:///djsfsdkjvfjkhfdvibdfinjdsfnjvdsflj"
437
-
by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular
438
-
during the :=> embedded in text RenaissanceAWSPARAMSTR:///djsfsdkjvfjkhfdvibdfinjdsfnjvdsflj[] embedded in text <=:
437
+
by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular
438
+
during the :=> embedded in text RenaissanceAWSPARAMSTR:///djsfsdkjvfjkhfdvibdfinjdsfnjvdsflj[] embedded in text <=:
439
439
The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32.`,
0 commit comments