Skip to content

feat(search): Index billing accounts - #332

Merged
kevwilliams merged 1 commit into
mainfrom
feat/search-index-billing-accounts
Nov 16, 2026
Merged

kevwilliams merged 1 commit into
mainfrom
feat/search-index-billing-accounts

Conversation

@kevwilliams

Copy link
Copy Markdown
Contributor

Problem

There is no ResourceIndexPolicy for billing.miloapis.com BillingAccount, so the search service never indexes billing accounts and they can't be found through search.

Change

This PR adds config/services/search.miloapis.com/billingaccount-resourceindexpolicy.yaml and lists it in that folder's kustomization.yaml. The following fields are searchable:

  • .metadata.name
  • .metadata.annotations["kubernetes.io/display-name"]
  • .spec.contactInfo.email: the billing contact's email
  • .spec.contactInfo.invoiceEmails[*]: the addresses invoices are sent to
  • .status.paymentArrangement.invoice.purchaseOrderNumber
  • .status.paymentArrangement.invoice.agreementReference: the signed MSA or order form, when there is one

The last two only exist on accounts with an active Invoice arrangement.

Contact names, postal addresses and tax IDs are left out on purpose.

Testing

kustomize build config/services/search.miloapis.com succeeds and outputs 10 ResourceIndexPolicy objects, up from 9.

As with the organization and project policies in #331, I haven't confirmed whether existing billing accounts are indexed as soon as this is applied, or only when each account next changes.

Add a ResourceIndexPolicy for billing.miloapis.com BillingAccount so
staff can find an account by its name, display name, billing contact
email, invoice emails, purchase order number or agreement reference.
@kevwilliams
kevwilliams requested a review from a team November 16, 2026 21:35
@kevwilliams
kevwilliams merged commit 99f97d2 into main Nov 16, 2026
10 checks passed
@kevwilliams
kevwilliams deleted the feat/search-index-billing-accounts branch November 16, 2026 21:39
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.

2 participants