Add bucket configuration to Tarbell configure about tarbell HOT 4 CLOSED

I'd say a first pass at this task is done. A few ideas came out of working through this...

• It might be nice to have a tarbell configure s3 command that walks through configuring s3 buckets only.
• How can we ease the transition for folks upgrading from and older version of Tarbell? Attempting to use an older config with these changes will break the Tarbell publish process.

Any others?

from tarbell.

Is there a way to detect an older config and prompt to upgrade?
On Dec 8, 2013 8:56 AM, "Ryan Nagle" [email protected] wrote:

I'd say a first pass at this task is done. A few ideas came out of working
through this...

• It might be nice to have a tarbell configure s3 command that walks
  through configuring s3 buckets only.
• How can we ease the transition for folks upgrading from and older
  version of Tarbell? Attempting to use an older config with these changes
  will break the Tarbell publish process.

Any others?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-30083120
.

from tarbell.

I finally got a chance to look at this. Nice work! I have a concern, though: We need to keep s3 creds out of tarbell_config.py. I think the config file needs to somehow account for this, so that it keys off the bucket name:

default_s3_key_id: <DEFAULTKEYID>
default_s3_access_key: <DEFAULTACCESSKEY>
s3_creds:
  myspecialapp.chicagotribune.com:
    access_key_id: <KEYID>
    secret_access_key: <SECRETKEY>
default_buckets:
   production: s3://apps.chicagotribune.com/

What do you think? The primary need is to keep secrets out of Tarbell project files so they can be readily released as open source projects.

from tarbell.

Finally fixed, with an upgrade message for folks on beta2 and below.

from tarbell.