Skip to content
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.

Improve the UX for Bundles that reference a non-existent unique provisioner ID #182

Open
timflannagan opened this issue Mar 29, 2022 · 2 comments
Open

Improve the UX for Bundles that reference a non-existent unique provisioner ID #182

timflannagan opened this issue Mar 29, 2022 · 2 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
backlog

Comments

@timflannagan
Copy link
Contributor

Summary: Bundles that reference an invalid, or a non-existent unique provisioner ID result in the Bundle resource not being reconciled by any of the provisioner(s) installed on-cluster, and there aren't any hints (e.g. events/status conditions/etc.) that get surfaced to the user.
@timflannagan timflannagan added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Mar 29, 2022
@timflannagan timflannagan added this to the backlog milestone Mar 29, 2022
@exdx
Copy link
Member

exdx commented Mar 31, 2022

This represents a UX gap but it's not clear it's required for the MVP.

@timflannagan timflannagan modified the milestones: backlog, v0.6.0 May 6, 2022
@timflannagan timflannagan modified the milestones: v0.6.0, backlog Jun 6, 2022
@github-actions
Copy link

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 13, 2022
@tylerslaton tylerslaton added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
backlog
Development

No branches or pull requests
3 participants
@timflannagan @exdx @tylerslaton