From addbf79d9542f5d81c5abe7c73eae60f560aa6e1 Mon Sep 17 00:00:00 2001 From: David Leek Date: Tue, 2 Jul 2024 15:26:44 +0200 Subject: [PATCH] docs: add a docs entry for file based OSS featureset import (#7520) --- .../docs/how-to/how-to-environment-import-export.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/website/docs/how-to/how-to-environment-import-export.mdx b/website/docs/how-to/how-to-environment-import-export.mdx index e4cdf322f6..4accdad549 100644 --- a/website/docs/how-to/how-to-environment-import-export.mdx +++ b/website/docs/how-to/how-to-environment-import-export.mdx @@ -138,3 +138,14 @@ On the other hand, the environment import/export feature was designed to export Further, the environment import/export comes with a much more stringent validation and will attempt to stop any corrupted data imports. +## Startup import {#startup-import} + +You can also import on startup by using an import file in JSON format and the import will be applied on top of existing data. Currently the startup import supports the same data supported in OSS import. + +Unleash lets you do this both via configuration parameters and environment variables. The relevant parameters/variables are: + +| config parameter | environment variable | default | value | +|--------------------|-------------------------|---------------|---------------------------------------| +| `file` | `IMPORT_FILE` | none | path to the configuration file | +| `project` | `IMPORT_PROJECT` | `default` | which project to import into | +| `environment` | `IMPORT_ENVIRONMENT` | `development` | which environment to import for | \ No newline at end of file