-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(wip): Do not allow template flows to be deleted / archived #4234
base: main
Are you sure you want to change the base?
Conversation
🤖 Hasura Change Summary compared a subset of table metadata including permissions: Updated Tables (1)
|
d74ce13
to
9de2b6f
Compare
filter: | ||
deleted_at: | ||
_is_null: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This repeated pattern means that archived flows cannot be selected.
hasura.planx.uk/metadata/tables.yaml
Outdated
check: | ||
_and: | ||
- deleted_at: | ||
_is_null: false | ||
- templated_flows: | ||
id: | ||
_is_null: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This repeated pattern is a post-update check which ensures that flows cannot be archived if they have associated templated flows derived from them.
9532b5b
to
db405ff
Compare
db405ff
to
b457494
Compare
What does this PR do?
flows.deleted_at
column in order to allow a soft delete patternPermissions
flows
tableflows.deleted_at
column (within the parameters of their current permission levels)flows.deleted_at
) for template flowsSome of this is pretty tricky to understand via the
tables.yaml
and took a bit of trial and error to figure out. Some e2e test coverage is needed here to explain this and act as a guard rail for future changes. I'm planning on introducing this in a future PR so that I'm not holding up the "archive flows" ticket @RODO94 will be shortly working on.