chef-provisioning | creating machines and infrastructures | Infrastructure Automation library

by chef-boneyard Ruby Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | chef-provisioning Summary

chef-provisioning is a Ruby library typically used in Devops, Infrastructure Automation, Ansible, Terraform, Chef applications. chef-provisioning has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

chef provisioning was officially end-of-life on august 31, 2019 and is no longer included with chef dk. the chef provisioning source code and drivers have been moved into the chef-boneyard organization. if you are a current user of chef provisioning, please contact your chef customer success manager or account representative to review your options. chef provisioning is a cookbook and recipe based approach for managing your infrastructure. users can codify their infrastructure and use chef to converge their infrastructure to the desired state. it has a plugin model (called drivers) to manage different infrastructures, including aws, azure and fog. chef provisioning is maintained according to the [chef maintenance policy] chef provisioning is a good fit for people who use or want to use the chef ecosystem to manage their infrastructure. infrastructure is represented as chef resources and managed in chef recipes and cookbooks. these recipes run on a provisioner node and attempt to converge the infrastructure idempotently. the aws driver is the most used, the most tested and

Support

Quality

Security

License

Reuse

Support

chef-provisioning has a low active ecosystem.

It has 533 star(s) with 173 fork(s). There are 113 watchers for this library.

It had no major release in the last 6 months.

There are 124 open issues and 236 have been closed. On average issues are closed in 463 days. There are 10 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of chef-provisioning is current.

Quality

chef-provisioning has 0 bugs and 15 code smells.

Security

chef-provisioning has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

chef-provisioning code analysis shows 0 unresolved vulnerabilities.

There are 1 security hotspots that need review.

License

chef-provisioning is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

chef-provisioning releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

chef-provisioning saves you 1556 person hours of effort in developing the same functionality from scratch.

It has 3462 lines of code, 324 functions and 57 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of chef-provisioning

Get all kandi verified functions for this library.

chef-provisioning Key Features

No Key Features are available at this moment for chef-provisioning.

chef-provisioning Examples and Code Snippets

No Code Snippets are available at this moment for chef-provisioning.

Community Discussions

Trending Discussions on chef-provisioning

Chef provisioner in terraform hangs when provisioning more than one resource

QUESTION

Chef provisioner in terraform hangs when provisioning more than one resource

Asked 2019-Sep-19 at 20:34

When using Terraform to provision multiple machines, and the Terraform Chef provisioner to configure the machine, I am only able to get it work if only one "resource" is being cheffed in the Terraform run. Everything works perfectly when only one VM is targeted. When more than one resource is provisioned, the chef run will hang at the Creating configuration files... step.

I have tried using modules, provisioning inside each resource, and most recently using null_resources to provision the vm resources after they've been created. (The null_resource has proven very useful, as it allows me to iterate on the chef run quickly without having to re-spin the VM resource every time, as I did when the provisioner was inside the resource block.)

This happened on TF 0.11, and continues in v0.12:

...

ANSWER

Answered 2019-Sep-19 at 20:34

It looks like, for now at least, we have to downgrade to v0.11 to get multiple provision runs to work. Please see this thread: Terraform stucks when instance_count is more than 2 while using remote-exec provisioner

Source https://stackoverflow.com/questions/57929171

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install chef-provisioning

You can download it from GitHub.
On a UNIX-like operating system, using your system’s package manager is easiest. However, the packaged Ruby version may not be the newest one. There is also an installer for Windows. Managers help you to switch between multiple Ruby versions on your system. Installers can be used to install a specific or multiple Ruby versions. Please refer ruby-lang.org for more information.