We are putting together plans for future changes. We obviously depend on all of you to take part in the planning for the future of goamz and execution of the plans. Other than the regulare 'issues' and 'pull requests' please also have a look at TODO.md.
It is inevitable that there will be backward incompatible changes. Please subscribe to the google group to get all the news (it will only be used for announcements, all the technical discussions will happen on github).
Google group: https://groups.google.com/forum/#!forum/goamz-announcements
The goamz package enables Go programs to interact with Amazon Web Services.
This is a fork of the version developed within Canonical with additional functionality and services from a number of contributors!
The API of AWS is very comprehensive, though, and goamz doesn't even scratch the surface of it. That said, it's fairly well tested, and is the foundation in which further calls can easily be integrated. We'll continue extending the API as necessary - Pull Requests are very welcome!
The following packages are available at the moment:
github.com/crowdmob/goamz/aws
github.com/crowdmob/goamz/cloudwatch
github.com/crowdmob/goamz/dynamodb
github.com/crowdmob/goamz/ec2
github.com/crowdmob/goamz/elb
github.com/crowdmob/goamz/iam
github.com/crowdmob/goamz/kinesis
github.com/crowdmob/goamz/s3
github.com/crowdmob/goamz/sqs
github.com/crowdmob/goamz/sns
github.com/crowdmob/goamz/exp/mturk
github.com/crowdmob/goamz/exp/sdb
Packages under exp/ are still in an experimental or unfinished/unpolished state.
The API documentation is currently available at:
http://godoc.org/github.com/crowdmob/goamz
Just use go get with any of the available packages. For example:
$ go get github.com/crowdmob/goamz/ec2$ go get github.com/crowdmob/goamz/s3
To run tests, first install gocheck with:
$ go get launchpad.net/gocheck
Then run go test as usual:
$ go test github.com/crowdmob/goamz/...
Note: running all tests with the command go test ./... will currently fail as tests do not tear down their HTTP listeners.
If you want to run integration tests (costs money), set up the EC2 environment variables as usual, and run:
$ gotest -i