by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Karl Skidmore
@karlskidmore_twitter
aws-cdk or awslabs/aws-cdk chatroom?

@mattbucci did you progress on your merge of @cplee's change to a local fork? Any problems?

@f00bar I agree, I've added a jira on myself to learn and migrate to CDK... I just don't want the pressure of dates, so if I can hedge by prolonging the ability to use mu that would be great. So if @mattbucci doesn't go first then I might give the local fork approach a go myself.

Karl Skidmore
@karlskidmore_twitter
Apparently CDK has python support in GA too!
f00bar
@f00bar
@karlskidmore_twitter awslabs/aws-cdk chatroom
Karl Skidmore
@karlskidmore_twitter
@mattbucci @f00bar @admons Saw this, thought you might find it interesting: https://garbe.io/blog/2019/09/11/hey-cdk-how-to-migrate/
Admon
@admons
It is, very interesting :)
Let's sync the moment one of us start to work on this
Karl Skidmore
@karlskidmore_twitter
@mattbucci @f00bar @admons Did any of you attempt to build mu from source yet? I'm giving it a go this week as I feel I need to hedge what could be a quick fix against a CDK learning curve.
Admon
@admons
I don’t
Karl Skidmore
@karlskidmore_twitter
@mattbucci @f00bar @admons I opted-in to the new ARN format at Root account level (affects all IAM + Roles) and then undeployed / redeployed my container services via mu command line, then tried the same with a change to repo triggering the pipeline and redeploying the containers. Er.... I didn't have a problem. This begs the question: what was the problem that the patch to mu was supposed to fix?
That's mu version 1.5.10
I'm using Fargate only, so don't know if the problem was an ECS on EC2 related thing.
Incidentally, in another AWS account (for testing), I built and patched the latest version of mu (including all the latest commits not already part of a release -- I reviewed them all, they looked useful to have, so just took them all, including cplee's patch for the ARN problem) and then made my own release version 1.5.12.
Karl Skidmore
@karlskidmore_twitter
I used my v1.5.12 to bring up my stack and it was fine. But.... as I didn't experience any post-opted-in problems using 1.5.10 then I'm wondering if I've been worrying for now reason.
Unless of course I have missed something obvious.
BTW, feel free to download v1.5.12 from here: https://mu-staging-907370165262.s3.amazonaws.com
Karl Skidmore
@karlskidmore_twitter
You can also refer to this binary from your mu yaml file in the pipeline section like this:
  pipeline:
    muBaseurl: https://mu-staging-907370165262.s3.amazonaws.com
    source:
      branch: develop
    build:
      image: aws/codebuild/docker:18.09.0
    production:
      disabled: true
If you're wondering why I tried this out instead of just going over to CDK.... I didn't want a looming opt-in deadline ruining Xmas and I want to learn CDK at my leisure :-)
Karl Skidmore
@karlskidmore_twitter
Forked repo with release assets here: https://github.com/Raremark/mu/releases
Matthew Bucci
@mattbucci
@karlskidmore_twitter this is great news, thank you for digging into this
I've been super swamped and was very thankful to the arn deadline wasn't official, but It did still have me worried
Arsalan Ahmad
@ArsalanDotMe
Hi, is there a way to remove resources created for a single pipeline? I already know about mu purge but I don't want to delete all resources that mu created. I just want to remove resources for a single pipeline.
Karl Skidmore
@karlskidmore_twitter
@arsalandotme Maybe mu pipeline term will do what you're after?
craig t smith
@craigtsmith
Anyone else noticed mu template validation errors recently - all pipelines I deployed with mu have started to fail with various template validation errors, it almost seem as though mu isn't merging extensions in correctly in the pipeline, whereas locally it does, have tried spinning up a new AWS Account and provisioning everything from scratch with the same results.
craig t smith
@craigtsmith
Hmmmm it seems to be with declaring extensions as URLs - if include the extension code locally to the project mu has no problems when running in pipeline!
f00bar
@f00bar
hey any news on mu-compatability with AWS post 2020?
f00bar
@f00bar
I haven't tried modifying the original package
Karl Skidmore
@karlskidmore_twitter
@craigtsmith FYI, I think I am experiencing the same problem. It started on the 13th as far as I can tell (I've been off ill, so only facing this now). Digging into it now. Did you get to a resolution?
Karl Skidmore
@karlskidmore_twitter
@craigtsmith BTW, for me the problem surfaces trying to pull down the cloudfront extension from Stelligent's repo. It seems intermittent when running from the command line. Still digging....
craig t smith
@craigtsmith
@karlskidmore_twitter same behaviour (intermittent + downloading extensions) I ended up including all extension code into the target repos and referencing locally, not ideal but it saved me an absolute nightmare. Like you I'm now exploring CDK instead. My gut feeling is the container used to build whatever has some updated or incompatible dependency or some other issue - only seems to be an issue when mu downloads extensions.
Karl Skidmore
@karlskidmore_twitter
@craigtsmith Thanks for the further info. FYI, I am repeatedly running mu env up acceptance from the command line (not even the pipeline) and some times it works, some times not (so possibly not related to any build container changes, etc). Like you, I will try bringing the extensions into the main repo just so I can move forward.
Karl Skidmore
@karlskidmore_twitter
mu-codecommit - AWS Cloud9 2020-01-20 18-06-47.png
craig t smith
@craigtsmith
Yeah I had inconsistent results running commands locally, but inlining the extensions has got everything ticking over again nicely.
Karl Skidmore
@karlskidmore_twitter
👍
How are you referencing the extension locally? i.e. from the yaml file.
craig t smith
@craigtsmith
I have a folder called mu and just reference like so: ./mu/extension-name
Karl Skidmore
@karlskidmore_twitter
like this? ' - url: ./mu/ext...'
craig t smith
@craigtsmith
yep
Karl Skidmore
@karlskidmore_twitter
👍
Mart Lumeste
@lumeste
guys, can I change service deployment Strategy? just changing mu.yml config doesn’t seem to do the trick
Karl Skidmore
@karlskidmore_twitter
Hi @lumeste I've never changed it from default. Searching the mu repo I see this: https://github.com/stelligent/mu/issues/251#issuecomment-358754597
image.png
And this open issue: stelligent/mu#83
CodeDeploy has all sorts of funky deployment methods now.... even more reason to hurry the migration to CDK
And when you have..... share the snippets with the few remaining people with a pulse in this Gitter channel ;-)
Karl Skidmore
@karlskidmore_twitter
@lumeste @f00bar @mattbucci - In case you missed it: https://stelligent.github.io/mutato/#/
Karl Skidmore
@karlskidmore_twitter
f00bar
@f00bar
@karlskidmore_twitter thanks for this
we moved away from mu to bref and serverless
but mutato looks like the logical next step
Michael Neil
@mneil
Thank you everyone for your support and usage. I'm officially announcing that Mu is no longer maintained https://github.com/stelligent/mu#deprecation-notice