StackJack 0.1.0.6193+4b1556f

This release adds an email notice when StackJack automatically combines a second subscription into your existing bundle, fixes the CIPP audit-log tools so they return the searches and records that actually exist, and corrects a misleading CyberCNS connector error that blamed your credentials when the saved host address was wrong.

New features

• Email notice when subscriptions are combined automatically. If a second subscription is created for your account and StackJack folds it into your existing bundle, the account owner now receives an email explaining what happened: which connectors were combined, that the unused days on the second subscription were refunded, and that the prorated remainder was charged to the bundle. Previously the only trace of this was the payment provider's own cancellation, refund and charge notices. Each combination sends one notice; a retry of the same combination does not send a second email.

Improvements

• cipp_list_audit_logs is described accurately and gains filters. The tool's description previously claimed it returned the Microsoft 365 unified audit log. It actually returns CIPP's own audit records, which only exist for events that matched an enabled CIPP alert rule, so a zero-row result is often correct rather than a failure. The description now says so. The tool also accepts the startDate, endDate, relativeTime and logId filters that CIPP supports, with notes on how they interact. The tenantFilter parameter now states that it must be the tenant's default .onmicrosoft.com domain (as reported by cipp_list_tenants); a vanity domain returns an empty list.
• cipp_list_audit_log_searches exposes all three CIPP views. You can now choose Searches (the default: tenant-scoped, with live status), SearchResults with a searchId to read a finished search's rows, or Ledger. Invalid combinations (an unknown type, SearchResults without a searchId, a days value below 1) are refused with a clear validation error instead of silently returning the wrong data. A blank or omitted type takes the default.

Bug fixes

• cipp_list_audit_log_searches returned an empty list for searches that existed. The request was not asking CIPP for the right view, so searches over older windows were excluded and came back as an empty result with no error. Existing searches are now returned.
• CyberCNS connector: a wrong host address was reported as rejected credentials. If the saved host was the ConnectSecure sign-in portal address (or another host that does not serve the pod API), the connector reported that your Tenant Name, Client ID and Client Secret had been rejected and told you to regenerate your API key, and the credential was disabled on that basis, even though nothing had checked the credentials. The connector card now explains that the saved address is not a pod API host, that your credentials were not rejected and do not need to change, and that the correct pod host can be read from your browser's address bar after signing in (on-premises installations use their own host). The message also now fits fully on the connector card instead of being cut off mid-sentence. Hosts whose names happen to contain numbers such as 401, 403 or 404 are no longer misread as credential, permission or not-found failures.
• D&H connector: clearing the account number field caused an error on save. Emptying the D&H account number box and then saving the connector produced an error instead of treating the field as blank. A cleared field is now handled as empty.