Greptile Overview

Greptile Summary

This PR improves the user experience in the Certificate Profile creation modal by disabling the certificate policy selector when no policies are available and displaying a helpful message "No certificate policies available" instead of the generic placeholder.

Changes made:

• Modified the placeholder prop to conditionally show "No certificate policies available" when certificatePolicies.length === 0
• Added certificatePolicies.length === 0 to the isDisabled condition alongside the existing isEdit check

Issue identified:
The form validation schema still requires certificatePolicyId to be non-empty (line 55), creating a situation where users can open the modal but cannot submit the form when no policies exist. Consider preventing modal access entirely when no policies are available, or showing a more prominent warning message explaining that certificate profiles cannot be created without policies.

Confidence Score: 4/5

• This PR is safe to merge with minor UX concerns
• The change improves user experience by providing clear feedback when no certificate policies are available. However, there's a logical gap where users can still open the modal but cannot submit the form due to validation requirements, which could be confusing. The implementation is sound but would benefit from handling the no-policies scenario at a higher level (e.g., disabling the "Create Profile" button when no policies exist).
• No files require special attention - the change is localized and straightforward

Important Files Changed

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Additional Comments (1)
frontend/src/pages/cert-manager/PoliciesPage/components/CertificateProfilesTab/CreateProfileModal.tsx The schema requires certificatePolicyId with .min(1) validation, but the UI now allows the form to render when certificatePolicies.length === 0. Users won't be able to submit the form (it'll fail validation), but they can open the modal and see a disabled field. Consider either:

1. Preventing the "Create Profile" action entirely when no policies exist (at the button/trigger level)
2. Making the field optional in the schema when no policies are available and showing a clear error message

This prevents a confusing user experience where the form appears but cannot be submitted.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

This shouldn't matter. They won't be able to submit the form and that's the intended behavior. Once we add the option to create policies in-line, the user will have a way to keep moving forward even if there's no policy available.