This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-16
Channels
- # 100-days-of-code (1)
- # announcements (1)
- # beginners (93)
- # boot (46)
- # cider (40)
- # cljdoc (4)
- # cljs-dev (7)
- # clojure (78)
- # clojure-conj (12)
- # clojure-dev (17)
- # clojure-italy (5)
- # clojure-nl (10)
- # clojure-spec (34)
- # clojure-uk (36)
- # clojurescript (56)
- # code-reviews (6)
- # core-async (31)
- # cursive (12)
- # datascript (9)
- # datomic (19)
- # devops (2)
- # editors (3)
- # emacs (6)
- # events (2)
- # figwheel (1)
- # figwheel-main (11)
- # fulcro (59)
- # graphql (10)
- # hyperfiddle (3)
- # keechma (5)
- # leiningen (26)
- # luminus (1)
- # nrepl (5)
- # re-frame (5)
- # reitit (10)
- # shadow-cljs (64)
- # spacemacs (29)
- # tools-deps (6)
- # uncomplicate (8)
- # vim (2)
- # yada (4)
if we would like to automatically push and deploy some of our branches to datomic cloud ions through CodePipeline/CodeBuild. What exact permissions does the codebuild instance profile need for being able to e.g. download the ions dependencies from the datomic maven S3 bucket? Also, I don't see any documentation on what is needed for pushing to codedeploy. Currently everything is happening as an admin user from a dev machine. Or is there a better way to setup CI for your ions?
My company has the exact same questions as @stijn. We are very interested in hearing about the best practices for CI/CD with Ions. After digging last night I found the top level codepipeline page seems to have my Ions application registered so maybe there is just manual exploration to be done?
@stijn Not sure what exactly is needed, but as a first step you could have a permission that is allowed to forward the admin role to codebuild. This will not give the admin permission to the dev machine
Here is more background https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html
We just saw a blip when deploying an ion:
ERROR, :message cryo is not a recognized vendor code (Service: AWSResourceGroupsTaggingAPI; Status Code: 400; Error Code: InvalidParameterException
There's no reference to cryo
in our code. We saw it happen from two different remote laptops in two different states (MN and TN). Retrying the same deploy a few minutes later succeeded just fine. Any ideas? (I'm stepping away from my machine for a while, so won't be following up immediately, but happy to do so when I get back.)@grzm I ran into this last night on a different project, thought it was just a blip.
I am going to log a case to AWS since you’ve both seen this. I’d like to see if they can track this down or provide any clues on what is unavailable.
@U09R86PA4 multiple peers each with their own valcache. I’ll look to add that to the docs, but sharing is not supported.
That’s too bad. Having shared big Valcache on a dev laptop (which is often multiprocess but same small set of remote txors) is the best use case I see. I run memcached for this now; shared Valcache would be much bigger, persist across reboots, and free up the ram now used for memcached
@U09R86PA4 You can’t use Valcache and memcached together. Its one or the other. The tradeoffs are discussed here http://staging.docs.datomic.com/on-prem/valcache.html#vs-memcached