#8680 Importing a Postman environment fails when a variable has no "enabled" field

Internal - [BRU-3960]

I have checked the following:

I have searched existing issues and found nothing related to my issue.

This bug is:

making Bruno unusable for me
slowing me down but I'm able to continue working
annoying
this feature was working in a previous version but is broken in the current release.

Bruno version

3.5.3

Operating System

macOS 26.4.1 (25E253)

Describe the bug

Importing Postman environments as Global environments fails with:

variables[12].enabled must be defined
An error occurred while importing the environment(s)

The import aborts and no environments are created after that error.

The root cause is that Postman omits the enabled field on some environment variables (or sets it to null). Bruno's converter passes that value straight through, producing enabled: undefined, which then fails the environment schema's enabled: Yup.boolean().defined() validation on the global-environment save path.

Importing the same files at the collection level appears to work, because that path doesn't run the same schema validation — so the behavior is inconsistent between global and collection imports.

Steps to reproduce

Create a Postman environment containing a variable with no enabled key, e.g.:

{
  "id": "some-id",
  "name": "My Environment",
  "values": [
    { "key": "api_url", "value": "http://localhost:8080", "enabled": true },
    { "key": "gymfinder-backend-url", "value": "https://example.com", "type": "default" }
  ]
}

(the second variable has no enabled field — exactly how Postman exports some variables)

In Bruno, open Global Environments → Import.
Select the JSON file.
Import fails with variables[N].enabled must be defined.

Collection to reproduce

Minimal JSON above; happy to attach a full Postman export if useful.

Screenshots/Live demo link

Screenshot of the error toast.

https://github.com/user-attachments/assets/a7925064-f0a0-428c-a971-631dc8e8c2ec

Video of the error toast.