looks great
Closed this issue · 6 comments
Aldrin:
finally, I went throuhg your code:
https://github.com/ingenieux/beanstalker/tree/master/beanstalk-maven-plugin
looks great! you even have unit tests :-)
thank you;
Andrei.
Yes, I'm thinking about enabling it conditionally given the presence of keys. Testing isn't a very beautiful scenario for cleaning up.
Listen Andrei, can you research some ideas on how to improve testing?
re: "conditionally given the presence of keys"
I think this is a correct approach;
I also suggest to invent some naming convention
so people like me can use aws iam to setup policy
that would allow to run beanstalker tests w/o fear
it would break something else
re: "some ideas on how to improve testing"
I am using invoker
http://maven.apache.org/plugins/maven-invoker-plugin/
here are bunch of examples
http://duns.github.com/maven-nar-plugin/
https://github.com/duns/maven-nar-plugin/tree/master/src/it
Oh, IAM. Which tools do you recommend? Its console is simply a PITA to deal with
I made bunch of bash scripts around this:
http://aws.amazon.com/developertools/AWS-Identity-and-Access-Management/4143
Great.
Well, I will close for now. I am concerned about having dual places to keep code, issues and stuff, but given the feedback, even if I keep the source on bitbucket (I am mostly a mercurial user), perhaps it is a good idea to keep issues and flow on github.
A new lesson was learned yesterday: You're not going anywhere if you're using IAM keys. Who could imagine that?
re: "iam keys" its a temp problem. they will enable to use it later; it might take a while; amazon is very slow moving godzilla;