bullhorn / bullhorn-cli Goto Github PK

Can you provide an example value?

And an example config set command please.

I think bullhorn typings generate should work out of the box with no config.

Here's the error I got: error: ENOENT: no such file or directory, open './typings/index.ts'

Workaround: touch ./typings/index.ts

As a feature request, it would be nice to set a logging level for the Bullhorn CLI. Specifically for the extensions install command, which pumps out the JSON file that it's going to POST to bullhorn, as well as the extension object that results from that POST. This is usually needlessly verbose, and it owuld be nice to be able to set a logging level that simply tells me the steps that the CLI is going through

There's two forms of logging in that I can see from bullhorn.js: providing username and password from the terminal, and being prompted for username and password to be sent through to the login function.

When prompted, I see the request made, the .bullhorn/credentials file created with credential information, but nothing seems to happen afterwards (no green Authorization Complete message). When providing the credentials from command arguments, bullhorn auth login --username <uname> --password <pass>, things work as expected.

Possibly related to #16 (which as been accepted but not merged in?)

When attempting to log in via bullhorn auth login and providing credentials or bullhorn auth --username <user> --password <password> an error is thrown.

TypeError: Cannot read property 'find' of undefined

In
commands/extract-extension.js

the function 'cleanUpScriptString' doesn't properly replace the opening 'function {' and closing bracket ('}'). Suggest we simplify the regex to instead only replace the opening part with empty string, and then in a second replace call deal with the closing bracket. Currently we match the whole function and replace it with the body, and I believe the negative lookahead we're using doesn't work

Hi team,

bullhorn-cli can only save 1 login at a time to my knowledge. This poses difficulty for our team, since we have both a production and a non production environment set up. To access the non-production environment and issue commands against it, we have to login with the same username but append an .npe to it.

It would be nice to be able to login to multiple accounts. bullhorn auth login could be for a 'default' profile, while bullhorn auth login <name> could be for a named profile. To issue commands with something other than the default, bullhorn --auth=<name>extensions list could be used.

What are the chances of something like this being implemented?

We are using extension configuration starter kit this kit working on basis of bullhorn cli, using this kit we deploy all extensions to bullhorn rest API, in that kit there is one file extension.json, in that file for field interactions if multiple interactions in same entity we can use ** to deploy all interactions no need to specify every interaction path, same way in page Interactions should be do, but it's not working like that, we need to give specify path then only it was working, this is not required functionality. The mistake happened in the Bullhorn cli they passed wrong variable in extract-extension.js in Line no:75
let interactionConfig = require(path.join(process.cwd(), interaction)).default;
This should be Like this
let interactionConfig = require(path.join(process.cwd(), file)).default;

they passed wrong variable it's not interaction it should be file variable, we tested it by changing locally it worked fine.

Thank you
Kethan Vemuri
[email protected]