sgentle / chef-node Goto Github PK

View Code? Open in Web Editor NEW

26.0 26.0 16.0 238 KB

Chef API client for nodejs

JavaScript 100.00%

chef-node's People

Contributors

Stargazers

Watchers

Forkers

ajburton dlasky mzgoddard smith merqlove cthayer mlabieniec spuder mcanthony iwtsolutions bruce-one adammcchesney tissuematter

chef-node's Issues

Support 0.12 once released

As pointed out in #10 support of ursa is currently up in the air, but there is talk about it changing hands and getting updated. We should check into it's status once 0.12 lands to see if it makes sense to continue using it.

~~If that doesn't pan out, we can port the small portion of native code we care about directly into chef-node.~~

~~Node 0.12 released~~
- ~~Support for ursa has been resumed~~
  - ~~Update dependency version~~
- ~~ursa still looks pretty dead~~
  - ~~Port setPrivateKeyPem and privateEncrypt native methods~~
- ~~Release new version~~

which api to use

Which api can be used to communicate between node.js application and chef server to create the databag item through api and then run chef client via node.js application.

I want to create a chef vault item using the chef api from my node.js application. is there any api to do so.?

Running chef client from nodejs application

Is it possible to run chef client from node.js application.

Is the latest release (v0.3.1) stable and complete ?

Hi @sgentle,

I'am really interested into using your node REST handler module for the Chef REST API !
But before I would want to know some details about the state of the module:

Is the latest release (v0.3.1) stable and complete ?
In other words, do you recommend this node module to be use applications in production ?
Or is there some known issues or soft/hard limitations to know before investing to this solution ?

Thanks for your great work and by advance, thanks for your additional informations.

Rémi Becheras.

Question - Can chef-node follow redirects?

I'm trying to get this module up and running, and it works great for fetching data, however when I try and push data, I get the following error.

<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>openresty/1.7.10.1</center>
</body>
</html>

Here is my index.js

var express = require('express');
var router = express.Router();

router.post('/foobar', function(req,res) {
  var client = req.client;
  client.get('/nodes/foo',function(err,res,body){
    body.run_list.push('role[fooy]');
    client.post('/nodes/foo',body,function(err,res,body){
      console.log(err ? err : body);
    });
  });
});

Does this module natively follow 301 redirects? I've been trying to use this workaround with no luck.
http://stackoverflow.com/a/13390241/1626687

Are there any other examples out there that show the proper way to post data?

Express 4
Node 0.12.4
OSX

Options at inititialize

I think in function Chef must be not required parameter(hash) in which we can put options like:

request method options ( i need it because of self-signed cert)
Chef version for header
...

sgentle / chef-node Goto Github PK

chef-node's People

Contributors

Stargazers

Watchers

Forkers

chef-node's Issues

Support 0.12 once released

which api to use

Running chef client from nodejs application

Is the latest release (v0.3.1) stable and complete ?

Question - Can chef-node follow redirects?

Options at inititialize

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Jobs