additional process callstack custom_documentation fields

[jdu2600]

Change Summary

Add missing process.parent.thread.Ext.call_stack fields to custom_documentation.
These optional fields have existed since 8.8.0

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-10-03T08:39:47.730+0000

• Duration: 7 min 53 sec

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[gabriellandau]

Thanks @jdu2600

[gabriellandau]

@joeypoon I don't think this is PR is touching anything related to this. Do you know how to resolve this? https://buildkite.com/elastic/endpoint-package/builds/76#018af4af-0bad-4fa5-b452-b98fe7af6866/188-189

Traceback (most recent call last):
  File "/opt/buildkite-agent/builds/bk-agent-prod-gcp-1696322235768810428/elastic/endpoint-package/.buildkite/scripts/find_oldest_supported_version.py", line 262, in <module>
    main()
  File "/opt/buildkite-agent/builds/bk-agent-prod-gcp-1696322235768810428/elastic/endpoint-package/.buildkite/scripts/find_oldest_supported_version.py", line 129, in main
    run(cfg)
  File "/opt/buildkite-agent/builds/bk-agent-prod-gcp-1696322235768810428/elastic/endpoint-package/.buildkite/scripts/find_oldest_supported_version.py", line 119, in run
    kibana_version_condition = manifest_doc["conditions"]["kibana.version"]
KeyError: 'kibana.version'
🚨 Error: The command exited with status 1
user command error: exit status 1

[joeypoon]

@joeypoon I don't think this is PR is touching anything related to this. Do you know how to resolve this? buildkite.com/elastic/endpoint-package/builds/76#018af4af-0bad-4fa5-b452-b98fe7af6866/188-189

Traceback (most recent call last):
  File "/opt/buildkite-agent/builds/bk-agent-prod-gcp-1696322235768810428/elastic/endpoint-package/.buildkite/scripts/find_oldest_supported_version.py", line 262, in <module>
    main()
  File "/opt/buildkite-agent/builds/bk-agent-prod-gcp-1696322235768810428/elastic/endpoint-package/.buildkite/scripts/find_oldest_supported_version.py", line 129, in main
    run(cfg)
  File "/opt/buildkite-agent/builds/bk-agent-prod-gcp-1696322235768810428/elastic/endpoint-package/.buildkite/scripts/find_oldest_supported_version.py", line 119, in run
    kibana_version_condition = manifest_doc["conditions"]["kibana.version"]
KeyError: 'kibana.version'
🚨 Error: The command exited with status 1
user command error: exit status 1

pretty sure that's just transient from the recent version bump for release. we can ignore this right @pzl ?

[kevinlog]

yes, this is just buildkite related that is an in-progress migration

[pzl]

Yes, we are still mid-process transitioning to Buildkite, so it is expected to fail until the CI migration is unblocked.

The ones marked required are the important ones, they are passing, so this is good (also any changes to the custom_documentation stuff is more or less instant-approve, merge at will. It is not shipped as part of the package itself (only things in package/endpoint get deployed to package stores)

[gabriellandau]

Thanks @joeypoon @kevinlog. Cherry-picked backport PR is here: #437

[elasticmachine]

Package endpoint - 8.12.0 containing this change is available at https://epr.elastic.co/search?package=endpoint