Skip to content

Cleanup: find a better way to handle retryable errors #174

@BlaineEXE

Description

@BlaineEXE

Enhancement

Why is this needed?:

Code cleanup and consistency

Describe the solution you'd like in detail:

Some options:

  1. Find a way to use errors.Is() with a custom COSI retryable error type
  2. Use github.com/siderolabs/gen xerror tagging
  3. Keep current code?
  4. Something else?

Describe alternatives you've considered:

See above and below

Additional context:

Original discussion: #170 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    api/v1alpha2Issue reported against or feature request for v1alpha2 APIkind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions