Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status

The dynect cookbook has been deprecated

Author provided reason for deprecation:

The dynect cookbook has been deprecated and is no longer being maintained by its authors. Use of the dynect cookbook is no longer recommended.

RSS

dynect (16) Versions 3.0.0

LWRP for managing DNS records with Dynect's REST API

Policyfile
Berkshelf
Knife
cookbook 'dynect', '~> 3.0.0', :supermarket
cookbook 'dynect', '~> 3.0.0'
knife supermarket install dynect
knife supermarket download dynect
README
Dependencies
Changelog
Quality 33%

dynect Cookbook

Build Status Cookbook Version

Automatically configures system DNS using Dyn's API.

Requirements

Platforms

  • All platforms supported by Chef

Chef

  • Chef 12.7+

Cookbooks

  • none

A Dynect account.

The dynect_rest gem. The dynect::default recipe installs this gem from http://rubygems.org

Attributes

The following attributes need to be set for the cookbook to function. Note: These are rather sensitive attributes so it's advised that you store these in a secure location such as an encrypted databag and set them via a wrapper cookbook.

  • node['dynect']['customer'] - Customer ID
  • node['dynect']['username'] - Username
  • node['dynect']['password'] - Password
  • node['dynect']['zone']- Zone
  • node['dynect']['domain'] - Domain

EC2 specific attributes:

  • node['dynect']['ec2']['type'] - type of system, web, db, etc. Default is 'ec2'.
  • node['dynect']['ec2']['env'] - logical application environment the system is in. Default is 'prod'.

Resources

rr

DNS Resource Record.

Actions:

Applies to the DNS record being managed.

  • :create
  • :replace
  • :update
  • :delete

Properties:

  • record_type - DNS record type (CNAME, A, etc)
  • rdata - record data, see the Dyn API documentation.
  • ttl - time to live in seconds
  • fqdn - fully qualified domain name
  • username - dyn username
  • password - dyn password
  • customer - dyn customer id
  • zone - DNS zone

None of the properties have default values.

Example:

dynect_rr "webprod" do
    record_type "A"
    rdata({"address" => "10.1.1.10"})
    fqdn "webprod.#{node['dynect']['domain']}"
    customer node['dynect']['customer']
    username node['dynect']['username']
    password node['dynect']['password']
    zone     node['dynect']['zone']
end

Recipes

This cookbook provides the following recipes.

default

The default recipe installs Adam Jacob's dynect_rest gem during the Chef run's compile time to ensure it is available in the same run as utilizing the dynect_rr resource/provider.

ec2

Only use this recipe on Amazon AWS EC2 hosts!

The dynect::ec2 recipe provides an example of working with the Dyn API with EC2 instances. It creates CNAME records based on the EC2 instance ID (node['ec2']['instance_id']), and a constructed hostname from the dynect.ec2 attributes.

The recipe also edits /etc/resolv.conf to search compute-1.internal and the dynect.domain and use dynect.domain as the default domain, and it will set the nodes hostname per the DNS settings.

a_record

The dynect::a_record recipe will create an A record for the node using the detected hostname and IP address from ohai.

Further Reading

Information on the Dynect API:

Dynect REST Ruby Library:

Maintainers

This cookbook is maintained by Chef's Community Cookbook Engineering team. Our goal is to improve cookbook quality and to aid the community in contributing to cookbooks. To learn more about our team, process, and design goals see our team documentation. To learn more about contributing to cookbooks like this see our contributing documentation, or if you have general questions about this cookbook come chat with us in #cookbok-engineering on the Chef Community Slack

License

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

build-essential >= 5.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

dynect

This file is used to list changes made in each version of the dynect cookbook.

3.0.0 (2018-06-11)

  • Convert the resource to a custom resource which raises the minimum supported Chef release to 12.7

2.2.0 (2018-05-14)

  • Use Bento slugs in Kitchen
  • More cleanup of the maintainer files
  • Use dokken images and fix suites
  • Require build-essential 5.0 and use the resource directly

2.1.0 (2017-07-09)

  • Remove chef 11 compatibility in chef_gem
  • Update apache2 license string
  • Add various platforms to the metadata
  • Use converge_by and load current_resource properly
  • Testing updates
  • Update maintainers docs
  • Dont' fail to parse metadata on older chef client releases
  • Make sure we have build-essential installed at compile_time by setting the compile time attribute in the build-essential cookbook

2.0.0 (2016-09-08)

  • Require Chef 12

1.1.0 (2016-08-30)

  • Use build-essential to make sure the gem can compile in the default recipe
  • Disable compile-time installation of the gem in the default recipe

v1.0.11 (2016-03-15)

  • Improved documentation for setting attributes. Added recommendation for setting attributes in a secure fashion via a wrapper cookbook
  • Added a .foodcritic file to exclude FC059 for now
  • Added long_description to the metadata
  • Added additional Chefspec testing
  • Updated Rubocop config to 0.38 format
  • Updated testing deps and removed cloud deps

v1.0.10 (2015-10-20)

  • Updated the requirements section of the readme to make the minimum supported Chef release 11 not 0.8
  • Improved readme formatting
  • Added gitignore file
  • Added chefignore file
  • Added Chef standard rubocop config
  • Added Travis CI testing
  • Added Berksfile
  • Added Gemfile with testing deps
  • Updated testing and contributing docs
  • Added maintainers.md and maintainers.toml files
  • Added travis and cookbook version badges to the readme
  • Added a Rakefile for simplified testing
  • Added source_url and issues_url to the metadata
  • Added basic convergence Chefspec
  • Resolved Rubocop warnings

v1.0.9 (2015-02-18)

  • Reverting chef_gem compile_time work

v1.0.8 (2015-02-18)

  • Fixing chef_gem with Chef::Resource::ChefGem.method_defined?(:compile_time)

v1.0.7 (2015-02-18)

  • Fixing chef_gem for Chef below 12.1.0

v1.0.6 (2015-02-17)

  • Being explicit about usage of the chef_gem's compile_time property.
  • Eliminating future deprecation warnings in Chef 12.1.0.

v1.0.4

  • [COOK-2382]: dynect: foodcritic style change

v1.0.2

  • [COOK-2381] - dynect: /etc/hosts entry does not get updated on
  • Amazon Linux due to regex mismatch

v1.0.0

  • [COOK-1958] - use chef_gem for runtime gem requirement

Collaborator Number Metric
            

3.0.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

3.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

3.0.0 passed this metric

No Binaries Metric
            

3.0.0 passed this metric

Testing File Metric
            

3.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

3.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number