Export Preset Secret Storage Configuration for Testing Integrations

Goal: Configure Godot export presets so that sensitive values (e.g., API keys) can be used during automated testing of third‑party integrations without committing actual production credentials to the repository.

Constraint: As of Godot 4.2, export preset values are saved as plain text in the project’s .godot or .import files, and the editor provides no encryption or vault interface for these fields. The community has discussed adding a secret‑management API, but no decision has been finalized, leaving the behavior undefined for secure test workflows.

Questions:

• Can export preset fields be marked as secret so their values are excluded from version‑controlled files while still being accessible at runtime?
• Should the editor provide a runtime masking option that prevents plain‑text values from being logged or transmitted during test execution?
• Is there a consensus on introducing a formal secret‑management API for export presets in a future Godot release?