Value Configuration Files

On this page

Configuration

Atlas Device Sync, Atlas Edge Server, Data API, and HTTPS Endpoints are deprecated. Refer to the deprecation page for details.

Note

This page describes a legacy configuration file format. You should only use this information if you're using the deprecated realm-cli.

Any configuration files you pull with App Services CLI or export from the UI use the latest configuration version. For detailed information on the current configuration file format, see App Configuration.

You can define static values in the /values directory. Each value is defined in its own JSON file with the same name as the value.

app/
└── values/
    └── <value name>.json

Configuration

<value name>.json

{
  "id": "<Value ID>",
  "name": "<Value Name>",
  "from_secret": <boolean>,
  "value": <Stored JSON Value|Secret Name>
}

Field	Description
`id` String	A string that uniquely identifies the value. Atlas App Services automatically generates a unique ID for a value when you create it.
`name` String	A unique name for the value. This name is how you refer to the value in functions and rules.
`from_secret` Boolean	Default: `false`. If `true`, the value exposes a Secret instead of a plain-text JSON value.
`value` String, Array, or Object	The stored data that App Services exposes when the value is referenced. If `from_secret` is `false`, `value` can be a standard JSON string, number, array, or object. If `from_secret` is `true`, `value` is a string that contains the name of the Secret that the value exposes.

What are the Atlas Application Services?