Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit ded1192

Browse files
Merge branch 'main' into repo-sync
2 parents ef0e80e + b91de04 commit ded1192

File tree

2 files changed

+1
-8
lines changed

2 files changed

+1
-8
lines changed

synthetics/test-config/global-variables.rst

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Define a global variables once, then you can use the variable across all of your
1212

1313
How can you use global variables?
1414
===================================
15-
Global variables are stored securely in the Splunk Synthetic Monitoring platform, but the keys and values of all global variables in your account are visible to all users with Manager or Administrator access.
15+
Global variables are stored securely in the Splunk Synthetic Monitoring platform, but the keys and values of all global variables in your account are visible to all users.
1616

1717
To preserve your account's security, don't use production credentials, real credit card information, or other sensitive data in global variables for your checks. Instead, try using placeholder credentials to test workflows that require information to be entered during a test.
1818

@@ -26,9 +26,6 @@ When you :strong:`conceal` a global variable, its value is permanently concealed
2626

2727
To preserve security, the value of a concealed global variable is never revealed to any user of the account after it has been created and saved. The value is scrubbed from the Splunk Synthetic Monitoring UI, from test results, and from alert messages.
2828

29-
Prerequisites
30-
================
31-
You need administrator access in Splunk Synthetic Monitoring to create and reference global variables.
3229

3330
Create a global variable
3431
===============================

synthetics/test-config/private-locations.rst

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -190,10 +190,6 @@ When using runner, it's important to correctly configure the proxy settings to a
190190

191191
- By default, the runner will set the ``NO_PROXY`` variable in the Dockerfile to include ``127.0.0.1``. If you override ``NO_PROXY``, you must ensure that ``127.0.0.1`` and ``localhost`` are still present, or browser tests may fail.
192192

193-
4. :strong:`Startup Check`:
194-
195-
- The runner includes a startup check to validate that ``NO_PROXY`` contains ``127.0.0.1`` and ``localhost``. If these are missing, you might encounter unexpected behavior in test execution.
196-
197193

198194

199195

0 commit comments

Comments
 (0)