Bruno CLI variable interpolation in the URL is not working

[Agagnier35]

I have checked the following:

• [X] I use the newest version of bruno.
• [X] I've searched existing issues and found nothing related to my issue.

Describe the bug

The variable interpolation of the URL field is partially working when using the CLI. It always work in the UI though.

Type of variable tested as not working:

• Request Variable
• Folder Variable
• Collection Variable

Type of variable tested as working:

• Environment Variable

Bruno CLI version: 1.34.1, but I noticed the issue was already happening in 1.28.0 Bruno UI version: 1.34.2

.bru file to reproduce the bug

meta { name: A sample request with a variable in the URL type: http seq: 1 }

get { url: {{host}}/resource/{{id}} body: none }

vars:pre-request { id: 46345080-3b96-45f0-a3df-d26932233473 }

assert { res.status: eq 200 }

Screenshots/Live demo link

when running with the JSON output you can notice that the "results.request.url" field has the variable template still present.

In the provided bru, if the host is an env variable, and the id a request variable, you would notice that the host would be interpolated properly in the results JSON but the ID would still be the template with the {{}}

[ganesh-bruno]

Hi @Agagnier35,

Thank you for reporting this issue.

Currently, we support all levels of variables in the GUI app, but only a few are supported in the CLI. We're working on adding support for all variable types in the CLI as well.

[Agagnier35]

Hello, I've kept experimenting to try and find a solution to this issue.

This issue seems to also include pre-request scripts (a simple console.log can prove they are not run in the CLI), and the variable interpolation is straight up not working anywhere except for environment variables.

It seems this PR might be the solution to this issue: https://github.com/usebruno/bruno/pull/3186

IMO, making sure the CLI has the same core as the UI should be a bigger priority for your team. These basic features has not been working since 1.28 (they were working before, I had to upgrade due to the breaking changes made to the variables in the UI)