Expose the ATC configs via table
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 23.6k
- Forks
- 2.6k
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 14
Description
Feature request
In debugging something in ATC, I wanted to know what a running osquery thought it's configure was. We surface a lot of the configuration through tables like osquery_packs, osquery_schedule, and osquery_flags. But I don't think we surface the ATC configs. (Or even the entire configuration directly)
What new feature do you want?
Surface the ATC configs, and/or the full configuration object.
How is this new feature useful?
Improve remote debuging
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing osquery_packs, osquery_schedule, and osquery_flags tables to understand how configuration is surfaced. Define whether the completed work exposes ATC configs, the full configuration object, or both, and verify that the result supports remote debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100