Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RFC: osquery API (table names and column names) change tracking #315

Closed
theopolis opened this issue Nov 1, 2014 · 3 comments
Closed

RFC: osquery API (table names and column names) change tracking #315

theopolis opened this issue Nov 1, 2014 · 3 comments
Labels
deployment RFC Request for comments: ideas or concepts to discuss. Not to merge it as is.

Comments

@theopolis
Copy link
Member

Add a script to post API changes when releases are cut.
@theopolis theopolis added deployment RFC Request for comments: ideas or concepts to discuss. Not to merge it as is. labels Nov 1, 2014
@theopolis
Copy link
Member Author

From an offline discussion with @marpaia, a document would be nice for column name recommendation and join-centric strategy to assure not replicating field names for different uses; or duplicating information in tables where joining is straightforward.

As well as a defined review before cutting a release, which audits the names.

@theopolis
Copy link
Member Author

A page on osquery.io detailing the tables/columns per release tag (+master) would be helpful.

@theopolis
Copy link
Member Author

http://osquery.io/tables/ is the new home. And ./tools/genapi.py will generate this data from HEAD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
deployment RFC Request for comments: ideas or concepts to discuss. Not to merge it as is.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@theopolis