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.

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

Add database documentation to conformance endpoint #236

Closed
pcgeek86 opened this issue Mar 11, 2016 · 2 comments
Closed

Add database documentation to conformance endpoint #236

pcgeek86 opened this issue Mar 11, 2016 · 2 comments

Comments

@pcgeek86
Copy link
Contributor

The conformance endpoint documentation doesn't talk about the reporting database, except to mention that it exists, and the web service reads / writes data to it.

  • Where the database runs
  • What alternative database services are supported
  • What the database schema looks like
  • How to connect to the database directly and query it

#40

Cheers,
Trevor Sullivan
Microsoft MVP: PowerShell

@ArieHein
Copy link
Contributor

  • The Report Server is a Pull Server that is just not serving configurations and modules.
    so its basically the same mdb file (used to be edb prior to 5.0 RTM, but i think thats a bug as well)
    Its mainly used for Push mode, or if you really really dont like the resporting of the nodes done on the
    same db the configuration is being served from.
  • None what so ever, this is internal structure that will probaby only be available if DSC and LCM go open source.
  • You cant tell but you can query it same as you could in v4 via REST API.
  • See previous point

@ghost
Copy link

ghost commented Mar 23, 2016

Accessing the database directly is not supported, and won't be documented. Please let us know what functionality you would like to see the reporting REST API support.

@ghost ghost closed this as completed Mar 23, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants