diff --git a/next.config.js b/next.config.js index d2dde435..e10be883 100644 --- a/next.config.js +++ b/next.config.js @@ -83,6 +83,12 @@ export default withNextra({ { source: '/testing/javascript-reference', destination: '/testing/script/javascript-reference', permanent: true }, { source: '/testing/assertions.html', destination: '/testing/tests/assertions', permanent: true }, { source: '/testing/javascript-reference.html', destination: '/testing/script/javascript-reference', permanent: true }, + + // Breadcrumb fix redirects - Issue #474 + { source: '/testing', destination: '/testing/tests/introduction', permanent: true }, + { source: '/testing/script', destination: '/testing/script/getting-started', permanent: true }, + { source: '/testing/automate-test', destination: '/testing/automate-test/overview', permanent: true }, + { source: '/testing/tests', destination: '/testing/tests/introduction', permanent: true }, // - /license-management redirects (old structure to new structure) { source: '/license-management/license-management', destination: '/license-overview', permanent: true }, diff --git a/public/screenshots/get-started/import-export/import_collection/import-env.webp b/public/screenshots/get-started/import-export/import_collection/import-env.webp new file mode 100644 index 00000000..15ceac7a Binary files /dev/null and b/public/screenshots/get-started/import-export/import_collection/import-env.webp differ diff --git a/src/pages/get-started/import-export-data/_meta.js b/src/pages/get-started/import-export-data/_meta.js index 2cdc0ab4..264f6e4f 100644 --- a/src/pages/get-started/import-export-data/_meta.js +++ b/src/pages/get-started/import-export-data/_meta.js @@ -1,6 +1,7 @@ export default { "import-collections": "Import Collections", "export-collections": "Export Collections", + "import-export-environments": "Import/Export Environments", "postman-migration": "Postman Migration", "script-translator": "Script Translator" } \ No newline at end of file diff --git a/src/pages/get-started/import-export-data/import-export-environments.mdx b/src/pages/get-started/import-export-data/import-export-environments.mdx new file mode 100644 index 00000000..f441d3cd --- /dev/null +++ b/src/pages/get-started/import-export-data/import-export-environments.mdx @@ -0,0 +1,55 @@ +import { Callout } from "nextra/components"; + +# Import Export Environment Variables + + + Make sure you have Bruno version 2.14 or later installed to use this feature. + + +You can import and export environment variables (collection and global) to share them across teams or back them up for later use. + +## Accessing Import/Export Options + +1. Go to the **Environments** section (top right corner). + +![Environment Variables location](/screenshots/variables/env-action.webp) + +2. Click on **Configure** to access the environment settings. + +3. You will see the **Import** and **Export** options in the bottom left corner. + +![Export Option](/screenshots/variables/click-export-option.webp) + +## Importing Environment Variables + +The import feature accepts environment files in both **Bruno** and **Postman** formats. + +### Steps to Import + +1. Click on the **Import** button in the environment configuration screen. + +2. Select the environment file you want to import. +3. The variables will be added to your environment (global or collection, depending on which you're configuring). + +![Import Environment](/screenshots/get-started/import-export/import_collection/import-env.webp) + +## Exporting Environment Variables + +### Steps to Export + +1. Go to the **Environments** section. +2. Click on **Configure**. +3. Click the **Export** button. +4. If you have multiple environments, select which environments you want to export. +5. Choose the location where you want to save the exported JSON file. + +![Export Collection Environment Location](/screenshots/variables/export-collection-env-location.webp) + +6. The environment variables will be saved as a JSON file that can be shared or backed up. + +The export procedure is the same for both collection and global environment variables. + + + Secret variables (variables marked as secret) will not be included in the exported JSON file for security reasons. + + diff --git a/src/pages/testing/script/javascript-reference.mdx b/src/pages/testing/script/javascript-reference.mdx index 8a3c0e81..44061d9e 100644 --- a/src/pages/testing/script/javascript-reference.mdx +++ b/src/pages/testing/script/javascript-reference.mdx @@ -524,6 +524,7 @@ Bruno provides a comprehensive variable system that allows you to manage and acc let data = res.getBody(); let token = bru.setEnvVar("access_token", data.token, { persist: true }); } + onResponse(res); ``` - **`hasEnvVar(key)`** - Check if the environment variable exists. diff --git a/src/pages/variables/collection-variables.mdx b/src/pages/variables/collection-variables.mdx index 25feefc3..816a1d8d 100644 --- a/src/pages/variables/collection-variables.mdx +++ b/src/pages/variables/collection-variables.mdx @@ -26,38 +26,6 @@ let namespace = bru.getCollectionVar("namespace"); ## Import/Export Collection Variables -You can import and export collection variables to share them across teams or back them up for later use. - -### Accessing Import/Export Options - -1. Go to the **Environments** section (top right corner). - -![No-Environment](/screenshots/variables/no-environment.webp) - -2. Click on **Configure** to access the environment settings. - -3. You will see the **Import** and **Export** options in the bottom left corner. - -![Export Option](/screenshots/variables/click-export-option.webp) - -### Importing Environment Variables - -The import feature accepts environment files in both **Bruno** and **Postman** formats: - -1. Click on the **Import** button. -2. Select the environment file you want to import -3. The variables will be added to your collection. - -### Exporting Environment Variables - -1. Click on the **Export** button. -2. If you have multiple environments, select which environments you want to export. -3. Choose the location where you want to save the exported JSON file. - -![Export Collection Environment Location](/screenshots/variables/export-collection-env-location.webp) - -4. The environment variables will be saved as a JSON file that can be shared or backed up. - - - Secret variables (variables marked as secret) will not be included in the exported JSON file for security reasons. + + For detailed instructions on importing and exporting collection environment variables, see the [Import/Export Environments](/get-started/import-export-data/import-export-environments) guide. diff --git a/src/pages/variables/environment-variables.mdx b/src/pages/variables/environment-variables.mdx index 5c50ff1b..47f29a48 100644 --- a/src/pages/variables/environment-variables.mdx +++ b/src/pages/variables/environment-variables.mdx @@ -36,5 +36,5 @@ vars { ``` - Check out the [Collection Variables](/variables/collection-variables#import-export-collection-variables) and [Global Environment Variables](/variables/global-environment-variables#import-export-global-environment-variables) documentation for import and export options. + For information on importing and exporting environment variables, see the [Import/Export Environments](/get-started/import-export-data/import-export-environments) guide. diff --git a/src/pages/variables/global-environment-variables.mdx b/src/pages/variables/global-environment-variables.mdx index c0446eab..6c0d80d2 100644 --- a/src/pages/variables/global-environment-variables.mdx +++ b/src/pages/variables/global-environment-variables.mdx @@ -48,38 +48,6 @@ To use a global environment variable, reference it using the format `{{var_name} ## Import/Export Global Environment Variables -You can import and export global environment variables to share them across teams or back them up for later use. - -### Accessing Import/Export Options - -1. Go to the **Environments** section (top right corner). - -![No-Environment](/screenshots/variables/no-environment.webp) - -2. Click on **Configure** to access the environment settings. - -3. You will see the **Import** and **Export** options in the bottom left corner. - -![Export Option](/screenshots/variables/click-export-option.webp) - -### Importing Environment Variables - -The import feature accepts environment files in both **Bruno** and **Postman** formats: - -1. Click on the **Import** button. -2. Select the environment file you want to import -3. The variables will be added to your global environment. - -### Exporting Environment Variables - -1. Click on the **Export** button. -2. If you have multiple environments, select which environments you want to export. -3. Choose the location where you want to save the exported JSON file. - -![Export Global Environment Location](/screenshots/variables/export-global-env-location.webp) - -4. The environment variables will be saved as a JSON file that can be shared or backed up. - - - Secret variables (variables marked as secret) will not be included in the exported JSON file for security reasons. + + For detailed instructions on importing and exporting global environment variables, see the [Import/Export Environments](/get-started/import-export-data/import-export-environments) guide.