Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
itlearn360
@itlearn360
mu-pipeline-sample-service: Pipeline (AWS::CodePipeline::Pipeline) CREATE_FAILED 1 validation error detected: Value at 'pipeline.stages.1.member.actions.1.member.configuration' failed to satisfy constraint: Map value must satisfy constraint: [Member must have length less than or equal to 1000, Member must have length greater than or equal to 1] (Service: AWSCodePipeline; Status Code: 400; Error Code: ValidationException; Request ID: b6b106d0-4ff4-4e6a-8c8d-075127ca2846)
Karl Skidmore
@karlskidmore_twitter
@itlearn360 Not seen this before. Try mu validate command to see if it detects anything maybe.
Matthew Bucci
@mattbucci
So with the ARN change looming and no response from stilligent has anyone switched to a custom fork?
Karl Skidmore
@karlskidmore_twitter
Judged on diminishing activity in this Gitter, I'd say that only @mattbucci (you) + @f00bar + @admons and I myself are persisting with mu. Even the ECS Workshop site made by @brentley has removed all references to mu (and he's not said why -- I asked twice). As we know the repo went to sleep ages ago, and looking here http://gitpop2.herokuapp.com/stelligent/mu you can see that there is no activity on any of the forks.
So.... what to do? I may try to merge the ARN fix from develop to master in my own fork to hedge risk in the short term, but I guess I will also be looking for alternative IaC frameworks. Indeed, going forward I need to avoid anything that looks like it might go to sleep again!!
f00bar
@f00bar
@karlskidmore_twitter any updates on whether AWS is sticking with the end of year deadline for the new ARN format ?
is the deadline really getting pushed down the road or it's been confirmed ?
Karl Skidmore
@karlskidmore_twitter
I'll ask again
You'll need your own Terraform stuff to set up the rest of the stack though which is a bit annoying to set up
For my use case I really need the auto scaling to work
I'm gonna spin up a new test environment in another region today, opt into new arn, see what breaks, then try to upgrade the environment using my own mu fork
I don't think I can move to a new solution by end of year
Karl Skidmore
@karlskidmore_twitter
In your fork did you just merge @cplee's ARN fix from develop to master or are you going for the latest development branch?
Matthew Bucci
@mattbucci
I'm only going to merge cplee's Arn fix
Admon
@admons
Yeah, I agree that this is the best way to go
A quick way to test it can be with the dry-run option, as mu is stateless and all it does is generate CFN files and deploy it
just run all commands locally with both versions and compare the result, something like that should work:
original-mu -e mu.yml -d -O /tmp/before env up ENV
original-mu -e mu.yml -d -O /tmp/before service deploy ENV
original-mu -e mu.yml -d -O /tmp/before pipeline up
new-mu -e mu.yml -d -O /tmp/after env up ENV
new-mu -e mu.yml -d -O /tmp/after service deploy ENV
new-mu -e mu.yml -d -O /tmp/after pipeline up
Karl Skidmore
@karlskidmore_twitter
image.png
@f00bar FYI....
Admon
@admons
Great!
f00bar
@f00bar
@karlskidmore_twitter thanks for that
sounds like there would be eventually a deadline so if I anyone has the time to fork mu and spawn it as community-supported development would be awesome
it's a still a good news for us though
: ))
if we can't jump start mu updates
eventually we'll have to migrate to CDK
I spoke with a AWS guy in cloud conference in Sofia last week - he said everyone is using AWS cdk
they are adding language support
f00bar
@f00bar
@karlskidmore_twitter I'm actually in the aws-cdk chatroom on gitter
it's pretty active
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