Hi,
Thanks for the advices! The HIDDEN status looks better for me as it
completely hides the resource from the user and it won't be included in
the documentation, but using this to status to mark the implementation
of the resource incomplete feels like a misuse of this status.
So I believe,
>
> I also remember that Heat has smth like 'hidden' in resource plugin
> declaration. Usually it is used to hide deprecated resource types so that
> new stacks with those can not be created but old ones can be at least
> deleted. May be you could use that flag while developing until you think
>
Hi Norbert,
my biggest concern with the workflow you've shown is that in the meantime
it would be possible to create undeletable stacks / stacks that leave
resources behind after being deleted. As the biggest challenge is usually
in updates (if it is not UpdateReplace) I'd suggest implementing
