[DOCS] Add missing "required" property in Security APIs#240921
[DOCS] Add missing "required" property in Security APIs#240921lcawl merged 40 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/experience-docs (Team:Docs) |
…atus --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/streams --include-path /api/fleet --include-path /api/saved_objects/_import --include-path /api/saved_objects/_export --include-path /api/maintenance_window --include-path /api/agent_builder --update
…atus --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/streams --include-path /api/fleet --include-path /api/saved_objects/_import --include-path /api/saved_objects/_export --include-path /api/maintenance_window --include-path /api/agent_builder --update
…atus --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/streams --include-path /api/fleet --include-path /api/saved_objects/_import --include-path /api/saved_objects/_export --include-path /api/maintenance_window --include-path /api/agent_builder --update
…atus --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/streams --include-path /api/fleet --include-path /api/saved_objects/_import --include-path /api/saved_objects/_export --include-path /api/maintenance_window --include-path /api/agent_builder --update
|
I've added the cloud/serverless deployment labels so we can do a quick smoke test to confirm, but this should be good to go as there ended up being no functional changes. Once tested I'll approve and we can get this merged. Thanks for raising this @lcawl! |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Public APIs missing comments
Async chunks
Page load bundle
History
|
spong
left a comment
There was a problem hiding this comment.
Confirmed existing route functionality is working as expected on CI cloud deployment:
GET /api/security_ai_assistant/knowledge_base/
POST /api/security_ai_assistant/knowledge_base/
So long as the doc outputs are as you expect @lcawl, this LGTM from my end! 🙂
|
Starting backport for target branches: 9.2 https://github.com/elastic/kibana/actions/runs/19447947094 |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Co-authored-by: Garrett Spong <garrett.spong@elastic.co> (cherry picked from commit 4f056d6)
… (#243581) # Backport This will backport the following commits from `main` to `9.2`: - [[DOCS] Add missing "required" property in Security APIs (#240921)](#240921) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-11-17T23:20:18Z","message":"[DOCS] Add missing \"required\" property in Security APIs (#240921)\n\nCo-authored-by: Garrett Spong <garrett.spong@elastic.co>","sha":"4f056d632363f21d6cc4a2090aae4bd5e1bbcb4c","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport missing","docs","ci:cloud-redeploy","ci:project-deploy-security","backport:version","v9.3.0","v9.2.1"],"title":"[DOCS] Add missing \"required\" property in Security APIs","number":240921,"url":"https://github.com/elastic/kibana/pull/240921","mergeCommit":{"message":"[DOCS] Add missing \"required\" property in Security APIs (#240921)\n\nCo-authored-by: Garrett Spong <garrett.spong@elastic.co>","sha":"4f056d632363f21d6cc4a2090aae4bd5e1bbcb4c"}},"sourceBranch":"main","suggestedTargetBranches":["9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/240921","number":240921,"mergeCommit":{"message":"[DOCS] Add missing \"required\" property in Security APIs (#240921)\n\nCo-authored-by: Garrett Spong <garrett.spong@elastic.co>","sha":"4f056d632363f21d6cc4a2090aae4bd5e1bbcb4c"}},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Garrett Spong <garrett.spong@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Garrett Spong <garrett.spong@elastic.co>


Summary
Relates to #233419, #228077
This PR addresses the following errors that are returned by
node scripts/validate_oas_docs.js:Per discussion with @spong the API is valid both with and without the resource parameter. This PR therefore adds the second variation of the path and updates the code to use the new path where appropriate. No functional changes were necessary as the Kibana server supports optional path params, so all that was needed was to override the generated types to make
resourceoptional again for all the existing usages.Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support- [ ] Documentation was added for features that require explanation or tutorials- [ ] Unit or functional tests were updated or added to match the most common scenarios- [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list- [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. Therelease_note:breakinglabel should be applied in these situations.- [ ] Flaky Test Runner was used on any tests changed- [ ] The PR description includes the appropriate Release Notes section, and the correctrelease_note:*label is applied per the guidelines- [ ] Review the backport guidelines and apply applicablebackport:*labels.Identify risks
N/A