What is equal Bruno command or option for pm.sendRequest with call back?

[KaliswaranNachimuthu]

I am trying to find options for pm.sentRequest with callback. I am not finding exact info on the discussion or issues. I use the below script in postman pre request script to send the request and get the required data for the current script. However, I am not finding this option in Bruno.

const getRequestUrl = ${pm.environment.get(
"applicationDomain"
)}/api/${pm.environment.get("API_VERSION")}/accounts/`;

const accountRequest = {
url: getRequestUrl,
method: "GET",
};

const setCSRFToken = (headers) => {
const cookieHeader = headers.filter((h) => {
return h.key === "Set-Cookie" && h.value.startsWith("x-TOKEN");
});
const ca = cookieHeader[0].value.split(";");
pm.environment.set("CookieToken", ca[0].substring(11));
};

pm.sendRequest(accountRequest, function (err, firstResponse) {
setCSRFToken(firstResponse.headers);
const body = firstResponse.json();
const assetAccounts = body.assetAccounts.assetAccount.map((a) => {return {...a.accountId, id: a.id}});
const liabilityAccounts = body.liabilityAccounts.liabilityAccount.map(
(l) => {return {...l.accountId, id: l.id}}
);

const accounts = [...assetAccounts, ...liabilityAccounts];

pm.environment.set("accounts", JSON.stringify(accounts));

pm.environment.set("accountHistoryNextIndex", 0);
pm.environment.set("accountDetailsNextIndex", 0);
pm.environment.set("accountId", accounts[0].id);
});
`

[Its-treason]

Bruno's bru.sendRequest methods does not accept a callback function. But there is also no need for it, you can just use await instead. For example:

try {
  const data = await bru.sendRequest('my-request');
  console.info(data);
  // Do something with the data like
} catch (error) {
  console.error(error);
}

[KaliswaranNachimuthu]

We need callback for us. Most of our existing Postman request uses callback. We are not able to find alternative to it to do/migration in Bruno.

[anusree-bruno]

This PR will add that #3845

[KaliswaranNachimuthu]

What is the tentative release date for this feature PR?

[anusree-bruno]

We've expedited the priority on this, and the team is actively working on it. We'll share an update on the progress within the next week.

As for the delivery timeline, we're tentatively targeting the mid of June. That said, we expect to have a nightly build available much earlier for testing.

[rsuplido]

So how does the new bru.sendRequest callback work? What is the best way to set a variable with the request response?

console.log works but setting a global variable in the callback does not work:

bru.sendRequest({
  method: 'POST',
  url: 'https://postman-echo.com/post',
  data: {"hello": "world"}
}, function (err, res) {
  if (err) {
    console.error('Error:', err);
    return;
  }
  console.log(res.data.data.hello);  // works
  bru.setGlobalEnvVar('gTest', res.data.data.hello); // does not work
});

workaround is to await (Postman does not require it):

await bru.sendRequest({
  method: 'POST',
  url: 'https://postman-echo.com/post',
  data: {"hello": "world"}
}, function (err, res) {
  if (err) {
    console.error('Error:', err);
    return;
  }
  console.log(res.data.data.hello);  // works
  bru.setGlobalEnvVar('gTest', res.data.data.hello); // works
});

or is it better just to forego callback?

const rs = await bru.sendRequest({
  method: 'POST',
  url: 'https://postman-echo.com/post',
  data: {"hello": "world"}
});

console.log(rs.data.data.hello);  // works
bru.setGlobalEnvVar('gTest', rs.data.data.hello); // works

[rsuplido]

Thanks for the explanation. It might be best to include or mention await in the documentation when callback is used. Folks who are used to Postman’s pm.sendRequest need to know that it’s not 1:1 conversion.

I see sendRequest being used to get an OAuth access_token, and most of the time, the callback form is used and the access token gets assigned to a variable. Does the Postman to Bruno code conversion add the await automatically?

[anusree-bruno]

We're currently updating our documentation — this PR adds those changes: https://github.com/usebruno/bruno-docs/pull/391/files. Also, when importing from Postman, pm.sendRequest is automatically translated to await bru.sendRequest.

[rsuplido]

Just noticed the bru.sendRequest bug fix on v2.7.0: "Set default proxy value as false for bru.sendRequest Axios request config"

What does this mean? Will it use or not use the global or collection proxy setting by default? How can we update this setting to true, and is there a way to specify a custom proxy like axios?

Also, is there an option or workaround to set https.Agent({rejectUnauthorized: false}) to ignore self-signed certs?

[rsuplido]

@anusree-bruno care to reply on the above? Thanks.

[anusree-bruno]

@rsuplido

Will it use global or collection proxy settings by default?

No, it won't use the app/system proxy by default. bru.sendRequest sets the default proxy to false, meaning global or collection proxy settings are ignored unless explicitly configured.

How can we update this setting to true, and is there a way to specify a custom proxy like Axios?

Yes. According to Axios config documentation, you can define custom proxy settings like this:

try {
  const response = await bru.sendRequest({
    method: 'POST',
    url: 'https://echo.usebruno.com',
    data: 'ping',
    proxy: {
      protocol: 'https',
      host: '127.0.0.1',
      port: 9000,
      auth: {
        username: 'mikeymike',
        password: 'rapunz3l'
      }
    }
  });
  console.log({ response });
} catch (error) {
  console.log({ error });
}

Is there an option or workaround to ignore self-signed certificates using https.Agent({ rejectUnauthorized: false })?

Yes. Custom HTTP/HTTPS agents can be used, but this only works in dev mode:

const http = require('node:http');
const https = require('node:https');

try {
  const response = await bru.sendRequest({
    method: 'POST',
    url: 'https://echo.usebruno.com',
    data: 'ping',
    httpAgent: new http.Agent({ keepAlive: false }),
    httpsAgent: new https.Agent({ keepAlive: false })
  });
  console.log({ response });
} catch (error) {
  console.log({ error });
}

This enables local development scenarios involving self-signed certs.