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

Difference between HasValidBundle and InvalidBundleContent? #518

Closed
joelanford opened this issue Aug 22, 2022 · 4 comments · Fixed by #520
Closed

Difference between HasValidBundle and InvalidBundleContent? #518

joelanford opened this issue Aug 22, 2022 · 4 comments · Fixed by #520
Assignees
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@joelanford
Copy link
Member

I see that our plain and helm provisioners use both HasValidBundle and InvalidBundleContent condition types. At a glance these seem duplicative, which could cause UX confusion.

I propose that we remove InvalidBundleContent and use HasValidBundle == "False" in its place.

@timflannagan
Copy link
Contributor

Do we need multiple bundle conditions at the BD controller level? Can we have a single Unpacked condition, and derive any validation or unpack failures there?

@joelanford
Copy link
Member Author

Yeah, that's essentially what I'm saying. If there's a better name than HasValidBundle, we can change that too. For this issue I was primarily focused on "let's have one rather than two", and less on "what should the name of the one be".

@timflannagan
Copy link
Contributor

Works for me. This would be a welcomed change from my perspective, and should help reduce the complexity in our BD controllers. We can tentatively slate this for next release.

@timflannagan timflannagan added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 22, 2022
@joelanford joelanford added this to the v0.10.0 milestone Aug 22, 2022
@timflannagan
Copy link
Contributor

Related to #333 and #331. The first issue looks like a potential duplicate of this one?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants