$fh.sec api returns reversed objects
Issue
Currently, the policy of returning objects from mBaaS API calls is to return them in order of err, result. At the moment, $fh.sec returns them in the other way around. i.e. the docs for $fh.sec give an example where (err, result) is returned ...
$fh.sec({
"act": 'encrypt',
"params": {
"algorithm": "AES", // mode : CBC, padding: PKCS#5
"plaintext": "Need more starting pages",
"key": secretkey,
"iv": iv
}
}, function (err, result) {
if (err) {
return console.log("Encryption failed: " + err);
}
return console.log("Encrypted data is " + result.ciphertext);
});
... where in actual fact it is (result,err) ...
$fh.sec({
"act": 'encrypt',
"params": {
"algorithm": "AES", // mode : CBC, padding: PKCS#5
"plaintext": "Need more starting pages",
"key": secretkey,
"iv": iv
}
}, function (result, err) {
if (err) {
return console.log("Encryption failed: " + err);
}
return console.log("Encrypted data is " + result.ciphertext);
});
This results in the error object being populated even for a successful call so it appears to return an error.
Environment
All FH3 environments.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.