Git Product home page Git Product logo

Comments (8)

github-actions avatar github-actions commented on September 24, 2024

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-dynamodb-table.

brianmaresca avatar brianmaresca commented on September 24, 2024

has this request even been seen by anyone? please let me know if my request is not clear or incomplete. I think all that this would require is more conditional dynamo table resource blocks that ignore replica changes based on a new input variable. i can create a PR of my own if necessary but i'm weary of that being ignored as well

from terraform-aws-dynamodb-table.

github-actions avatar github-actions commented on September 24, 2024

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-dynamodb-table.

github-actions avatar github-actions commented on September 24, 2024

This issue was automatically closed because of stale in 10 days

from terraform-aws-dynamodb-table.

brianmaresca avatar brianmaresca commented on September 24, 2024

welp i guess Issues filed in this repo are completely ignored, good thing i didn't waste my time drafting a PR

from terraform-aws-dynamodb-table.

antonbabenko avatar antonbabenko commented on September 24, 2024

@brianmaresca Sorry for the delay and for ignoring this issue. The root problem with this specific issue and with similar in other repositories is that the proposed solutions are not doable, because we can't use variables inside of the lifecycle block in Terraform and control that some changes should be ignored and some not.

Not everybody will want to have to ignore changes in replica, am I right?

from terraform-aws-dynamodb-table.

brianmaresca avatar brianmaresca commented on September 24, 2024

@antonbabenko thank you for responding! apologies for my snarky comment.

i understand variables can't be used in lifecycle blocks, but i still think there is a doable workaround. i would think a variable such as ignore_changes_replica could drive this, exactly like how ignore_changes_global_secondary_index will create a resource that ignores gsi changes. (#72)

from terraform-aws-dynamodb-table.

github-actions avatar github-actions commented on September 24, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

from terraform-aws-dynamodb-table.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.