Export Resources

Use the export API to retrieve ThunderID resources:

• POST /export: returns a JSON object.

JSON Response Shape

POST /export returns this payload:

json

{
  "resources": "# File: My_App.yaml\napiVersion: thunder/v1\n...",
  "environment_variables": "MY_APP_CLIENT_ID=\nMY_APP_CLIENT_SECRET=\n"
}

Field behavior:

• resources: Combined YAML output for all exported resources, with # File: headers and --- separators.
• environment_variables: environment file content with one empty assignment per detected template variable.

If the export has no template variables, environment_variables is an empty string.

Internal API Model Reference

The API reference schema also defines an internal ExportResponse model (see ExportResponse.envFile, backed by the EnvironmentFile schema/struct):

json

{
  "files": [
    {
      "fileName": "google-idp.yaml",
      "content": "resource_type: connection\ntype: google\n...",
      "size": 128
    }
  ],
  "envFile": {
    "fileName": ".env",
    "content": "GOOGLE_CLIENT_ID=\nGOOGLE_CLIENT_SECRET=\n",
    "size": 40
  },
  "summary": {
    "totalFiles": 2,
    "totalSizeBytes": 168
  }
}

When no template variables are detected, envFile is omitted (or null in internal JSON serialization paths).

Format Option

In options.format, only yaml is currently supported for generated resource content.