Skip to content

Support Forward Only #12

@eakmanrq

Description

@eakmanrq

General use case: I am making a change to a model and have that change take effect starting at a specific date or starting at the date that I merged my model into main. This should apply to the model I am directly changing and then also downstream models affected if I want it to. I want to be able to validate this change prior to going to prod and leverage my existing CI/CD flow. Once merged I expect that this change to be properly rebased into other environments.

What we identified as new features we need to support his:

  • Need: Breaking/Non-Breaking restatement (meaning restate children or don’t restate children)
  • Need: A way to label a breaking/non-breaking as “temporary” that needs to be converted to forward only once going to prod
    • Question: How does this work outside of CI/CD?
  • Need: A way to ensure that all forward only changes invalidate the target snapshot version
  • Needed to ensure data accuracy: A way to block parallel restatements on a single version of a snapshot
  • Want: Notify owners of environments that they have been invalidated once the merge to main happens

Metadata

Metadata

Assignees

No one assigned

    Labels

    FeatureAdds new functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions