Follow-up from "Add support for steps to AI catalog flow update GraphQL mutation"
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The following discussions from !200882 (merged) should be addressed:
-
@.luke started a discussion: (+2 comments) Suggestion (not blocking)
I've just set Jaydip's MR !200967 (merged) to merge, which moves it there, so this could be a quick follow-up.
-
Lee mentioned !200882 (comment 2689020240): I've added that in, but it does leave me with a question about how we're surfacing this error and if we should be handling/bubbling it up as a
raise_resource_not_available_error.The good thing is, we don't differentiate between no permission vs non-existing.
Ideally i'd like to move that to a follow-up though if you're OK with that (we're being consistent with the create mutation.