Set the Bruno environment variable using javascript snippet given in documentation is not working.

[cyrilgeorge153]

Documentation link: https://docs.usebruno.com/scripting/javascript-reference.html#setenvvar Request details and script used is given below in the screenshot: After sending reuest, environment section is as follows:

[n00o]

I think the issue is that you create your onResponse function but never actually call it. A much simpler solution would be not to include a function and do something like this:

let data = res.getBody();
bru.setEnvVar("access_token",data.token);

If you still want it then make sure to call your function at the end like this:

onResponse(res);

The documentation should probably include the actual calling of the function so people can copy and paste code to test out the results.

[cyrilgeorge153]

@n00o Above code is not working for me.

[n00o]

It appears that {{access_token}} can't be interpolated by Bruno when it is inside of a Script section. Further confirmation of this can be found inside of the Timeline tab as it won't show the right value for the Authorization Header. To be able to reference a environment variable inside of a Script section use:

req.setHeader("Authorization",`Bearer ${bru.getEnvVar("access_token")}`);

If you would like to use less code then go to the Auth tab in the request, pick Bearer Token, and then include {{access_token}}.

I can understand not including the capability for environment/collection variables interpolation inside of scripts since you can already access them with functions but it should at least not color values of {{variables}} so that it is more clear that they don't work.

[cyrilgeorge153]

@n00o I checked with Auth tab already but it was not working. Please check the screenshots.

when env variable used in Auth tab when token value directly used in Auth tab

Seems like variable usage not working in Auth tab for Bearer token

[n00o]

I just tested this and found out that setEnvVar() only overrides values but doesn't create them. This should definitely be fixed so that it adds them too. Here are the ways you can get around it for now:

Method 1

The Vars tab inside of the Request tab allows you to make collection variables (not environment variables) so you could go there for Request 1 and put in: Name: access_token Value:res.body.access_token

Method 2

Alternatively you can create the environment variable access_token and leave it blank, having Request 1 always override it each time your Bearer token expires.

Method 3

Use collection variables in Request 1 post-script tab instead and make it look something like this:

let body = res.getBody();
bru.setVar("access_token",body.token);

(more info here: https://docs.usebruno.com/scripting/javascript-reference.html#setvar) The annoying thing with this method is that changing environments will break your {{access_token}} making it useless for that environment.

[cyrilgeorge153]

@n00o Thanks for sharing the 3 methods in a detailed way. I have used these methods already. I was trying to set the Bruno environment variable using javascript snippet as it was it was given in the documentation. Hope this issue will be fixed in upcoming versions.

[peauc]

@cyrilgeorge153 I have observed that if you have collection level auth it can break request level auth, is that your case?

[cyrilgeorge153]

@peauc It is not my case. I was trying to create a environment variable using below code. let data = res.getBody(); bru.setEnvVar("access_token",data.token); I was expecting the access_token variable to be created in environment once the environment is selected from UI but it was not getting created. Work around for this was method 2 mentioned above by @n00o . But actually a environment variable has to get created but not working that way.

[andrea-merli]

I've made a similar test but mayme i'm doing something wrong using req.setHeader("Authorization",Bearer ${bru.getEnvVar("token")}); in prerequest script works, but setting {{token}} as bearer auth tab leads to this strange call

GET http://app.tecno.test/rest/all/V1/store/storeViews accept: application/json authorization: Bearer bru.getEnvVar("token");

so {{token}} gets transformed in Bearer bru.getEnvVar("token");

[helloanoop]

This has been fixed in v1.3.0

@cyrilgeorge153 Can you test and check if the issue is solved ?

[andrea-merli]

Sorry i'd just installed from brew and it was still 1.2.0. Now the situation has changed but still doesn't work {{token}} as an env variable doesn't get replaced the value in auth tab

[cyrilgeorge153]

It is working for me in 1.3.0 version. Verified in Ubuntu 22.04 . Used snap package. let data = res.getBody(); bru.setEnvVar("access_token",data.token); Above lines have created access_token environment variable I am able to access the access token value in Auth tab

req.setHeader("Authorization", "Bearer {{access_token}}"); Above line is also working

[cyrilgeorge153]

@helloanoop In windows also it is working

But getting environment variable using getEnvVar is not working. Hope i am doing it in right way.

[andrea-merli]

I've made another test, always 1.3.0 on mac os x 13.5.1 (22G90)

SetVar works

SetEnvVar doesn't work

I make e getToken request, and try to use the resulting token in subsequent request.

I think is because collection var takes precedence on env var

is there a way to access specifically env var if there is a name collision with collection var? I see that i cannot yet delete a collection var from UI, but is it possible via code?

[cyrilgeorge153]

@andrea-merli try this: let token = bru.getEnvVar("access_token"); But for me it does not work for some reason. Official Doc:https://docs.usebruno.com/scripting/javascript-reference.html#getenvvar

[andrea-merli]

tried this let token = bru.getEnvVar("token"); console.log(token); it works

I just cannot access it from the auth panel with interpolation -> {{token}}

[andrea-merli]

I managed to access {{token}} in auth panel as an env variable by unsetting the collection token variable via pre request js

delete bru.collectionVariables.token; but is't tricky and undocumented.

I understand that collection variables take precedence on env ones, but I think there should be a way to access directly env variables something like {{env.token}}

Summary

• if the same variable name is used for env and collection collection takes precedence (OK)
• if I change my mind and i decide to switch from collection to env variable i cannot access the env variable from auth panel, since it will be masked by the collection variable.
• once i delete (delete bru.collectionVariables.token;) the collection variable the env variable is accessible.

Solution proposal

• a syntax to allow accessing the desired scope variable. {{variable}} -> accesses collection variable falls back to env variable (Like now -> OK) {{collection.variable}} -> accesses directly the collection variable {{env.variable}} -> accesses directly the env variable

• a method to unset variables bru.unsVar('variable') equivalent to delete bru.collectionVariables.token; bru.unsEnvVar('variable') equivalent to delete bru.envVariables.token;

[cyrilgeorge153]

@andrea-merli If same variable is used in collection and environment say eg base_url. In this case if environment is selected in UI, then the precedence should be for environment variable. If no environment is selected then the collection variable value should be taken. I think this is how postman works.

[andrea-merli]

@cyrilgeorge153 Thank you for your input! I've conducted some tests, and I appreciate your clarification. I did find it a bit confusing when switching from saving the variable in the collection to the environment, as the old variable seems to take precedence. I observed that I couldn't access the environment variable until I deleted the collection one. Now that I understand how to make it work, I'm grateful for the insights, though it did take me some time to grasp the concept.

I still believe that my initial suggestion holds some value and could potentially be considered as an improvement :-) and I'm eager to collaborate further on refining this approach.

[technodrome]

Still broken in 1.18.1 https://github.com/usebruno/bruno/issues/2358#issuecomment-2147874883

[grtessman]

@andrea-merli

• bru.unsVar('variable') equivalent to delete bru.collectionVariables.token; bru.unsEnvVar('variable') equivalent to delete bru.envVariables.token;

My 2 cents: Why not use unsetVar and unsetEnvVar? I don't get the point of trying to save 2 spaces over being more intuitive.

And for me, setEnvVar seems to work within bruno cli in Gitlab but both the collection variable and setVar does not work.

[eyalyoli]

this my auth script on the collection level in pre-req and the token set on the collection level under auth with auth inherit per req

const axios = require('axios');
const url = require('url');

const tokenEndpoint = bru.getEnvVar('HOSTNAME') + '/token-generate';
const clientId = bru.getEnvVar('CLIENT_ID');
const clientSecret = bru.getEnvVar('CLIENT_SECRET');

// Function to generate the token
async function getAccessToken() {
  try {
    const response = await axios.post(tokenEndpoint, 
      {
        'clientId': clientId,
        'clientSecret': clientSecret
      },
      {
        headers: {
          'Content-Type': 'application/json'
        }
      }
    );

    if (response.data && response.data.token) {
      // Set the access token as an environment variable
      bru.setEnvVar('token', response.data.token);
      console.log('Access token retrieved successfully');
    } else {
      console.error('Failed to retrieve access token');
    }
  } catch (error) {
    console.error('Error retrieving access token:', error.message);
  }
}

// Call the function to get the access token
await getAccessToken();

also set "token" in env vars as empty and it should work on bruno v1.21 (tested on Mac)

[cbolivar-neostella]

I solved the issue using a test script. There is something weird since it doesn't create any variable in collection but you can get the value using {{access_token}} reference.

test("Auth", function() {
  let data = res.getBody();
  let token = bru.setVar("access_token", data.access_token);
});

[Tarikul-Islam]

Hi @all I solved the issue using a test script.

test("Status code is 200", function() { let data = res.getBody(); let token = bru.setEnvVar("access_token", data.access_token); });

[goevexx]

The test script workaround still works. The actual problem does not seem to have been solved yet in version 2.9.1. Setting any variable in post request script doesn't persist. Running it in tests tab it can persist vars, env vars and global env vars after first call.

[danielatsellhub]

I can confirm that setVar is not working for me nor setEnvVar in post request scripts. Using the Vars tab from the request does work though

[macropay-solutions]

@danielatsellhub We also can't make it populate in the global environment.

UPDATE:

Working like this bru.setGlobalEnvVar("access_token", res.getBody().access_token); source https://stackoverflow.com/a/79755281

[vishalnandagopal]

setEnvVar is not working for me in postrequest script when the global env var is already present. It is working in pre request script.