Import and export variables

1. 1

   On the project matrix, click `Importar variáveis` (Import variables).

   The wizard opens in two steps.

2. 2

   On the `Conteúdo` (Content) step: provide the text and check the `Ambientes de destino` (Target environments).

   Drag a file, pick one, or paste the text (1 MiB limit). Each target environment has the só as chaves (valor vazio) (keys only, empty value) switch, which seeds the structure without copying values — useful to create production gaps from dev.

3. 3

   Click `Pré-visualizar` (Preview) and review the table.

   The raw text goes to the server, whose hardened parser (multiline PEM, comments, quotes, BOM, CRLF, duplicates) is the source of truth. The table shows, per key and per environment, the nova (new), muda (changes), or igual (same) badge, plus parser warnings, and lets you exclude rows. Nothing is written in this step.

4. 4

   Click `Importar N chave(s)` (Import N key(s)).

   result

   The keys are written to the checked environments and the matrix reflects the result.

Exportar variáveis (Export variables) downloads a whole environment as .env, JSON, YAML, or Docker (--env-file). The download comes out in clear text and is audited — a line in the project history listing the exported keys.

• The .env export escapes newlines and tabs inside quotes, so a reimported export is byte-faithful — PEM keys and tokens with CRLF survive the round trip.
• The Docker format cannot represent newlines: if any value is multiline, the server refuses the export naming the keys, instead of emitting a broken file. Use .env or JSON in those cases.

• Comments on batch write: a key with no new comment keeps the stored comment; a comment identical to the stored one counts as same (resubmitting the same form does not create a version); an empty string clears the comment.