Skip to content

Resolve Environment Variable within Variable #5791

@rajjaiswalsaumya

Description

@rajjaiswalsaumya

I have checked the following:

  • I've searched existing issues and found nothing related to my issue.

This feature

  • blocks me from using Bruno
  • would improve my quality of life in Bruno
  • is something I've never seen an API client do before

Describe the feature you want to add, and how it would change your usage of Bruno

I used to use variable within variable in Postman.
E.g. my variable set in global var say env=dev
Then the variable environment set as {{server_{{env}}_url}} should become {{server_dev_url}}
and resolve to the variable sever_dev_url set it the globals.

Why whis is required ?
I set the env from auth api, and using scripts update the global variable. This helps me to change variables directly from the request rather going in vars everytime alsong with all the postman request can remain same without modication of headers. Only Auth API sets the vars and ensures I am using correct vars rather than duplicating same API for each env.

The same feature is available in Postman too.

Mockups or Images of the feature

No mocksup required as vars within vars is just curly braces within vars. E.g environment={{server_{{env}}_url}} where environment is a variable having env as variable

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions