Adoptable Cookbooks List

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.

netscaler cookbook

This has been written so that adding a missing NetScaler resource should be easy.

Creating a new resource

All resources should have required attributes: hostname, username, password, and the resource name

All other attributes (payload for rest call) should default to nil.

Use http://<netscaler_ip>/nitro/v1/config/<resource_name> to see available payload options.

Creating a new provider

Actions supported:

:create - calls create_resource

:delete - calls delete_resource

:bind - calls bind_resource

Attributes in the payload should be passed in as a hash

Add new row in payload_filter.rb for @@attribute_list_by_resource. The array should contain keys from the payload that can not be updated via the Nitro Api.

resource_type should be the the feature that you're manipulating (ie server, lbvserver, etc)

resource_id should be set to the key of the resource (ie name, servicegroupname, etc)

Be carefull of chef reserved words. If you look at the netscaler_server resource/provider
you'll see I use the payload key as my attribute names for everthing except for servername which
doesn't exist as a key for the server resource type. The key in the options hash is still 'name'
though. The options hash key has to match the netscaler payload key.