Repository navigation
Follow the final API document; clearer refusals, key expiry and deprecation warnings - #280
Merged
Merged
Conversation
Refresh the vendored OpenAPI document and the generated client. The document now also describes an operation that writes; the CLI reads only, so the generator skips operations that are not GET. Signed-off-by: d0ubl3g <48954024+d0ubl3g@users.noreply.github.com>
…asons A 403 whose reason is IP_NOT_ALLOWED or MFA_ENROLLMENT_REQUIRED now says what is wrong and what to do about it. Any other reason code the API sends shows the API's own message. All of them keep exit code 4. Signed-off-by: d0ubl3g <48954024+d0ubl3g@users.noreply.github.com>
When the API refuses a request because of a query parameter it does not know, the error now lists the unknown name or names and the ones the API accepts. A new test checks that every query parameter the client can send is declared in the vendored API document. Signed-off-by: d0ubl3g <48954024+d0ubl3g@users.noreply.github.com>
whoami shows the key's expiry (a `Key expires` line, and the additive credential_expires_at field in --json, null for no expiry) and warns on standard error when the key expires within 14 days or has expired. Signed-off-by: d0ubl3g <48954024+d0ubl3g@users.noreply.github.com>
The client reports the Deprecation and Sunset headers of an answer, and the CLI prints one warning on standard error per run when it sees one. Signed-off-by: d0ubl3g <48954024+d0ubl3g@users.noreply.github.com>
…ation warning Signed-off-by: d0ubl3g <48954024+d0ubl3g@users.noreply.github.com>
… document A refusal with the PLAN_WITHOUT_API reason, and a device sign-in refused for the same reason, now say the tenant's plan does not include API or CLI access and where the plan can be changed. The vendored API document is the final one for 2026-11-15; alerts now carry their MITRE ATT&CK mapping. Signed-off-by: d0ubl3g <48954024+d0ubl3g@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes you will see as a user:
Alerts now carry their MITRE ATT&CK mapping:
alerts list --jsonshowsmitre_techniquesandmitre_mapping, and--csvhas two more columns at the end.hodeishield whoamishows when a tenant API key expires, as a "Key expires" line and acredential_expires_atfield in--json. It warns on standard error when the keyexpires within 14 days or has already expired.
an IP address that is not allowed, an account that must enrol multi-factor
authentication, and a tenant plan that does not include API or CLI access. A device
sign-in refused because of the plan shows the same message. Any other refusal reason
shows the API's own message, also with exit code 4.
parameter and the accepted ones.
deprecated.
vendored API document.