Skip to content
This repository was archived by the owner on Jan 13, 2021. It is now read-only.
This repository was archived by the owner on Jan 13, 2021. It is now read-only.

Rework error/status reporting for resources #276

@ash2k

Description

@ash2k

Currently some things that aren't error are propagated as if they are within the code. For example, if an object, described in a bundle, exists but is marked for deletion that is reported as a terminal error in the resource's status. This is not an error, this should be reflected as "in progress" situation. There are more things like that. In general, more things should be propagated as just information about a resource, not as an error return value. Error return values should be used for true errors like unexpected failures, I/O failures, so on.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions