feat: #381

[ghost]

#381

Set headers:

client.createContainer({
  name: 'test-container',
  headers: {
    'X-Container-Read': '.r:*'
  }
}, function() {});

Update headers:

client.updateContainerHeaders(container, {
  'X-Container-Read': '.r:*'
}, function() {});

Remove headers:

client.updateContainerHeaders(container, {
  'X-Remove-Container-Read': '.r:*'
}, function() {});

[coveralls]

Coverage increased (+0.02%) when pulling e159ea3 on kfll:swift-container-acl into e12b251 on pkgcloud:master.

[kenperkins]

This appears to allow passing arbitrary headers to createContainer? If so, that should be added in the documentation at https://github.com/pkgcloud/pkgcloud/pull/385/files#diff-c4a3a7c9ff3534d7a13bcb9345003bc3L92, as well as in the documentation.

[kenperkins]

I'm excited about the contribution. One question I have is should we sanitize the inbound headers?

[ghost]

Sanitization at client is not neccessary, as the backend will tell if a header is allowed or disallowed.

[coveralls]

Coverage decreased (-0.01%) when pulling 19558a2 on kfll:swift-container-acl into e12b251 on pkgcloud:master.

[coveralls]

Coverage decreased (-0.05%) when pulling a7a8282 on kfll:swift-container-acl into e12b251 on pkgcloud:master.

[coveralls]

Coverage decreased (-0.05%) when pulling 73abba0 on kfll:swift-container-acl into e12b251 on pkgcloud:master.

[meteormatt]

response headers should be request headers

[coveralls]

Coverage decreased (-0.05%) when pulling 315b12b on kfll:swift-container-acl into e12b251 on pkgcloud:master.

[meteormatt]

I have test it is OK.

Remove headers:

client.removeContainerHeaders(container, {
  'X-Remove-Container-Read': '.r:*'
}, function() {});