Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Discuss: How should we convey that child resources failed to get created? #67

Closed
everettraven opened this issue May 18, 2023 · 1 comment
Closed

Discuss: How should we convey that child resources failed to get created? #67

everettraven opened this issue May 18, 2023 · 1 comment

Comments

@everettraven
Copy link
Collaborator

As a follow up to #65 and based on #65 (comment) we should be cautious of overloading the meaning of the UnpackFailing status. Some things to discuss:

  • Is it reasonable to use the UnpackFailing status to represent failure to create child resources?
  • What alternative status should be used to represent this failure?
@everettraven everettraven mentioned this issue May 18, 2023
Merged
@everettraven
Copy link
Collaborator Author

Closing this issue as this is likely obsolete due to the new storage and serving mechanism being introduced with the completion of #139 which will no longer have child CRs that are created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@everettraven