Affected Puppet, Ruby, OS and module versions/distributions

• Puppet:all
• Ruby:all
• Distribution:all
• Module version: v0.15.0

How to reproduce (e.g Puppet code you use)

nginx::resource::upstream { $title:
  sticky  => {
    'cookie' => {
      'name' => 'srv_id',
      'expires' => '7d',
      'domain' => 'example.com', 
      'path' => '/'
    }
  },
  members  => $members,
}

What are you seeing

code above results in an incorrect sticky directive in upstream.conf:

sticky cookie name=srv_id expires=7d domain=example.com path=/

and a Set-Cookie response header:

Set-Cookie: name=srv_id=e4000322f27372a178fcc291d1178b37; expires=...

This will generally not be noticed from a functional point of view, but the name of the cookie is not as expected.

What behaviour did you expect instead

sticky directive in upstream.conf:

sticky cookie srv_id expires=7d domain=example.com path=/

and a Set-Cookie response header:

Set-Cookie: srv_id=e4000322f27372a178fcc291d1178b37; expires=...

Any additional information you'd like to impart

Syntax for the sticky directive in the nginx documentation:

sticky   cookie name   [expires=time]  [domain=domain]  [httponly]  [secure]  [path=path];

The first parameter sets the name of the cookie to be set or inspected.