Create registry.yml per #16993
ps. just got your message in Slack. This has a particularly gnarly query
because the registry data is gross. I have broken it on new lines at the
commands but it's all going to be a big blob in the fixed width columns
on the site & Fleet UI anyway. We'll see what it does. If you would
prefer I could "minify" these all onto 1 line no matter how long they
are?
The Example header was not showing on this page. Moved the query up to
the example block with explanation.
---------
Co-authored-by: Eric <eashaw@sailsjs.com>
Updates to cpu_info data table in Fleet Table Docs per #16993
I am trying something. The arp_cache table .yml has no references to the
Column || Type || Description schema table on the page, so, I am
assuming you are doing magic to combine the other sections of the page
(Description, Examples, Notes) with the data from osquery tables.
If I needed to make explicit reference to them, I am dumb.
If I only to need to make explicit reference to them IFF I am changing
the schema table, yay.
Thanks!!!!!!!
---------
Co-authored-by: Eric <eashaw@sailsjs.com>
Please check the new scalar is working correctly. I am going to have to
do a PR on the authdb table because some of the markdown syntax is
showing on the updated page. Thanks!
---------
Co-authored-by: Eric <eashaw@sailsjs.com>
Fixed copy+paste or find+replace booboo when scalar was changed from >-
to |-
Copy operation caught up the angle brackets used around "right_name" in
this doc.
Thanks.
Closes: #19271Closes: #19286
Changes:
- Updated the example in the schema folder readme
- Updated the block scalar used in Fleet's osquery override
documentation (`>-` » `|-`) and removed extra newlines
- Updated the block scalar used in URLs used to create new yaml override
files
- Regenerated osqeury_fleet_schema.json
Need help to get the correct formatting for the notes key/val
---------
Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Drew Baker <89049099+Drew-P-drawers@users.noreply.github.com>
Changes:
- Updated the version of osquery schema that is merged with Fleet's
overrides: (5.11.0 » 5.12.1)
- Regenerated schema/osquery_fleet_schema.json
Closes: #18240
Changes:
- Updated the schema override files to use only one YAML block scalar
(`>-`)
- Updated the template yaml included in the link to create a new
override file in get-extended-osquery-schema helper to use the `>-`
block scalar
- regenerated osquery_fleet_schema.json
Changes:
- Deleted `schema/fleet_schema.json` (This file was previously used when
merging the osquery schema with Fleet's overrides before we switched to
using YAML override files).
- Updated the description of the `generate-merged-schema` script.
Changes:
- Updated the `build-static-content` script to remove support for the
`requires_user_context` column attribute
- Updated `get-extended-osquery-schema` to not set a
`requires_user_context` value in the merged schema json.
- Regenerated `schema/osquery_fleet_schema.json`
