Skip to content

Conversation

@abhijith-darshan
Copy link
Contributor

Description

Catalog should retain secret error while applying GitRepository resource.

If there is an error checking the existence of .spec.sources[*].secretName Secret then it should be reflected in the inventory message for GitRepository.

What type of PR is this? (check all applicable)

  • 🍕 Feature
  • 🐛 Bug Fix
  • 📝 Documentation Update
  • 🎨 Style
  • 🧑‍💻 Code Refactor
  • 🔥 Performance Improvements
  • ✅ Test
  • 🤖 Build
  • 🔁 CI
  • 📦 Chore (Release)
  • ⏩ Revert

Added tests?

  • 👍 yes
  • 🙅 no, because they aren't needed
  • 🙋 no, because I need help
  • Separate ticket for tests # (issue/pr)

Added to documentation?

  • 📜 README.md
  • 🤝 Documentation pages updated
  • 🙅 no documentation needed
  • (if applicable) generated OpenAPI docs for CRD changes

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • New and existing unit tests pass locally with my changes

@abhijith-darshan abhijith-darshan marked this pull request as ready for review November 5, 2025 12:16
@abhijith-darshan abhijith-darshan requested a review from a team as a code owner November 5, 2025 12:16
if secretErr != nil {
msg = msg + "; " + secretErr.Error()
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

If this is done inside the objectReadiness method, it would avoid the missing error checks from below.

Signed-off-by: abhijith-darshan <abhijith.ravindra@sap.com>

(chore): retain catalog secret err in inventory status
@abhijith-darshan abhijith-darshan force-pushed the fix/retain_catalog_secret_err branch from 63a029f to 68d7b7a Compare December 3, 2025 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants