nodejitsu/node-cloudfiles — Issue #18: createContainer with String on existing cdnEnabled container
Author: rtgibbons
Created: 2011-11-16 23:33:20+00:00
State: open

creating a container with just a string works. But if it already Exists and is cdnEnabled, it doesn't grab the cdnUri. See this commit for the test https://github.com/rtgibbons/node-cloudfiles/commit/de35b538c2b485a37ab12ea6ed64dcd6c365620f , here is the object it produces

````js
{ files: [],
client:
{ config:
{ auth: [Object],
serverUrl: 'https://servers.api.rackspacecloud.com/v1.0/520732',
storageUrl: 'https://storage101.ord1.clouddrive.com/v1/MossoCloudFS_7bd8d9dd-cacd-4f6f-8620-5f3cc3bc312b',
cdnUrl: 'https://cdn2.clouddrive.com/v1/MossoCloudFS_7bd8d9dd-cacd-4f6f-8620-5f3cc3bc312b',
authToken: '33859a6e-9e89-4b2d-9265-cabd54cfe874',
storageToken: '33859a6e-9e89-4b2d-9265-cabd54cfe874' },
authorized: true },
name: undefined,
cdnEnabled: false,
cdnUri: undefined,
cdnSslUri: undefined,
ttl: undefined,
logRetention: undefined,
count: 0,
bytes: 0 }
````

Don't have time to explore the fix, just documenting the bug. Once we get this software pushed this week I'll try to come back and revisit