by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Mika Fonsén
    @mfonsen
    As mentioned in issues, I was able to take first project to production. Thank you very much. Everyone involved were delighted how easy it was and how many improvements there were over earlier Sceptre.
    I created some issues, but there were many other observervations. Maybe I'll write some down here
    It seems like Takomo fails deleting a stack that has termination protection set. Haven't had time to reproduce.
    Would be nice if there were an option that would return 0 if no changes are needed to stacks and 1 if Takomo would change something. In essence this would be the same as answering yes to first question and then failing if there are subsequent prompts
    1 reply
    Seems like Takomo retry gets stuck if credentials expire along during deployment
    Mika Fonsén
    @mfonsen
    I was planning to write something about how to migrate from Sceptre to Takomo. It wouldn't be perfect as there are so many ways how to use Takomo. I wonder it would make sense to create a documentation PR on this?
    Henri Meltaus
    @hmeltaus
    Hi, I'm really glad to hear that you've been able to complete some migrations already. Lots of improvements are still needed as you have noticed, especially error handling isn't perfect. I'll try to fix any issues you find and also implement new features, just keep 'em coming =) Documentation PRs are welcome. I've just recently switched from VuePress to Docusaurus. The current docs are in this repo https://github.com/takomo-io/takomo-docs .
    Henri Meltaus
    @hmeltaus
    regarding deleting stacks that have deletion protection on. Currently there's no support to enable/disable deletion protection. So, when Takomo fails to delete a stack with deletion protection on, it works as expected. I created a new issue to add support for this takomo-io/takomo#86
    Mika Fonsén
    @mfonsen
    It would be quite enough if the error message would indicate that deletion cant’t be done due to protection. It was really easy to use command hook with aws cli to implement the manipulation part. Or to create a custom hook. Anyway, a really minor issue
    I’ll take a look at the migration docs PR at some point.
    Mika Fonsén
    @mfonsen
    Thank you for all those improvements recently merged. I’ll try to upgrade to 1.5.0 once it’s out. Everything seems to be running nicely atm
    Henri Meltaus
    @hmeltaus
    ok, I'll do the releases tonight
    Mika Fonsén
    @mfonsen
    Maybe I could tag a PR with #assertnochanges to ensure that for example a Takomo upgrade does not change the stacks. Or some other refactoring. And the same from my own machine if necessary
    Or the recently done migration from Sceptre to Takomo. Nothing was supposed to be changes. On CI I had to use —yes which could have changed something
    If you use —yes and cloud side SAM Takomo always reports updates complete even though nothing was changed. This is probably a Cloudformation feature
    Henri Meltaus
    @hmeltaus
    ok, I'll look into this