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.

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

Show actual log during custom wait rule if asked specifically #1038

Merged
merged 1 commit into from
Dec 9, 2024

Conversation

rohitagg2020
Copy link
Contributor

Show actual log during custom wait rule if asked specifically

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?


Additional Notes for your reviewer:

Review Checklist:
  • Follows the developer guidelines
  • Relevant tests are added or updated
  • Relevant docs in this repo added or updated
  • Relevant carvel.dev docs added or updated in a separate PR and there's
    a link to that PR
  • Code is at least as readable and maintainable as it was before this
    change

Additional documentation e.g., Proposal, usage docs, etc.:


pkg/kapp/resourcesmisc/custom_waiting_resource.go Outdated Show resolved Hide resolved
pkg/kapp/resourcesmisc/custom_waiting_resource.go Outdated Show resolved Hide resolved
@@ -57,6 +57,7 @@ type WaitRuleConditionMatcher struct {
SupportsObservedGeneration bool
UnblockChanges bool
Timeout string
ShowActualMessage bool

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: ShowActualMessage -> ShouldDisplayActualMessage

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am ok with anything. However ShouldDisplayActualMessage seems a bit long.

@rohitagg2020 rohitagg2020 force-pushed the add-actual-log branch 2 times, most recently from b21758e to ac0ceea Compare December 8, 2024 06:42
@@ -131,6 +131,7 @@ func (s CustomWaitingResource) IsDoneApplying() DoneApplyState {
}

unblockChangeMsg := ""
actualMsg := "No failing or successful conditions found"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just message instead of actualMsg?
We are assigning the variable with a custom message which indicated that it is just not "actual" 🤔

@rohitagg2020 rohitagg2020 merged commit dc144aa into carvel-dev:develop Dec 9, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants