Skip to content

Commit d0630aa

Browse files
Merge pull request #39 from fingerprintjs/readme/remove-store-name
2 parents c3e7e92 + 6ed7696 commit d0630aa

File tree

2 files changed

+6
-8
lines changed

2 files changed

+6
-8
lines changed

README.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -71,13 +71,6 @@ This is a quick overview of the installation setup. For detailed step-by-step in
7171

7272
See the [Fastly Compute proxy integration guide](https://dev.fingerprint.com/docs/fastly-compute-proxy-integration#step-4-configure-the-fingerprint-client-agent-to-use-your-service) in our documentation for more details.
7373

74-
### Using custom store names
75-
76-
By default, the service package provided in releases assumes the following names for the Config store and Secret Store:
77-
78-
* `Fingerprint_Compute_Config_Store_<SERVICE_ID>`
79-
* `Fingerprint_Compute_Secret_Store_<SERVICE_ID>`
80-
8174
## Feedback and support
8275

8376
Please reach out to our [Customer Success team](https://fingerprint.com/support/) if run into any issues with the integration.

contributing.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,12 @@ For proposing changes, use the standard [pull request approach](https://docs.git
2222
2. Run `pnpm build` to compile the project and assemble the WebAssembly output.
2323
3. The build artifact is located in the `bin/main.wasm` file, which will be deployed to Fastly.
2424

25-
### Custom Store Name Prefix
25+
### Using custom store names
26+
27+
By default, the service package provided in releases assumes the following names for the Config store and Secret Store:
28+
29+
* `Fingerprint_Compute_Config_Store_<SERVICE_ID>`
30+
* `Fingerprint_Compute_Secret_Store_<SERVICE_ID>`
2631

2732
To use a custom name prefix for both(Secret and Config) stores, use the `STORE_NAME_PREFIX` environment variable to build a custom service package:
2833

0 commit comments

Comments
 (0)