[ckan-dev] linking data in private S3 buckets

Wed Feb 19 14:37:51 UTC 2014

Nigel,

This seems like a big functionality change for a  ‘minor’ release.  I don’t want to question this specific case, but I think that it is useful for the developers to think about their strategy for adding and changing functionality and how that affects maintainability for the user community.

One cool thing about CKAN is that it is a healthy project.  Quite a few committers, frequent commits and new features.  The flip side is that some of these new features and fixes are not backwards-compatible between minor versions.  This makes it difficult for people who are implementing big enterprise systems based on CKAN, particularly the organizations that we really want to see sharing their data, governments. Somewhere in there is a balance.

CKAN is gaining significant market share in the open data space, and that is great.  If people decide that it is too hard to maintain an instance because minor version upgrades break their install, I expect to see fewer people choosing CKAN for their new projects.

Don’t get me wrong.  I like CKAN and we are happy that it is there for us to use in our project.  I just want to suggest that more thought and communication is put into when major and breaking changes are released.  (The publishing of the weekly meeting notes is a great start.)

Thanks,

David.

From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org] On Behalf Of Nigel Babu
Sent: Wednesday, February 19, 2014 4:20 AM
To: CKAN Development Discussions
Subject: Re: [ckan-dev] linking data in private S3 buckets

Hello Ivan,
On ckan 2.2 and above, we removed the support for external filestores. Only local filestores are supported. The old implementation was causing more trouble than it's worth. We will, in the future, build an interface for extensions to support multiple external filestores.

Nigel Babu

Developer  |  @nigelbabu<https://twitter.com/nigelbabu>

The Open Knowledge Foundation<http://okfn.org/>

Empowering through Open Knowledge

http://okfn.org/  |  @okfn<http://twitter.com/OKFN>  |  OKF on Facebook<https://www.facebook.com/OKFNetwork>  |  Blog<http://blog.okfn.org/>  |  Newsletter<http://okfn.org/about/newsletter>

CKAN | http://ckan.org/ | @CKANproject<http://twitter.com/CKANproject> | the world’s leading open-source data portal platform

On 12 February 2014 21:06, Ivan <vanzaj at gmail.com<mailto:vanzaj at gmail.com>> wrote:
Hello,

Sorry if I'm missing something obvious. I can't find any info in the docs, wikis, github issues, or elsewhere.
Is there a way to create a private dataset linked to a file stored in a private S3 bucket?

I have ofs.aws_access_key_id, and ofs.aws_secret_access_key in my <deploy>.ini, but it doesn't seem to be enough (i know it's not an auth issue as s3cmd with the same keys from the same host works fine). This is on ckan 2.3a.

thanks,
Ivan

_______________________________________________
ckan-dev mailing list
ckan-dev at lists.okfn.org<mailto:ckan-dev at lists.okfn.org>
https://lists.okfn.org/mailman/listinfo/ckan-dev
Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140219/8e588509/attachment-0003.html>