liquidware-ninjaSecond brain & toolkit
Personal project. Research and learning only. Not for production. No warranty.Not for production
  • Built on my own time for research and learning. Not affiliated with, endorsed by or supported by my employer, Liquidware or Microsoft.
  • Bring your own Liquidware licenses. Don't run any of it in production or against tenants and subscriptions that matter. Test in a dedicated lab first.
  • Provided "as is", without warranty of any kind, under each repository's license. You use it at your own risk and own the Azure charges it incurs.
  • Contributions and forks are welcome and encouraged on public repos. See Contribute.

Asks for Liquidware

partialReviewed 2026-10-18Source: liquidware/upstream.md

Gaps this project has hit, worth raising with Liquidware. Each says what's missing, the evidence, and its status. (The family keeps these in an upstream.yaml data file; this KB can't yet, because the shared scripts read that file from a fixed path. A family format proposal is open: decision 0012.)

Ask Evidence Status
Configure a new Hub through the API (license, API user, allow list) so first-time setup can be automated The published API guide covers data queries only (api.md); whether the Hub's own reference shows configuration calls is unverified Open, to check on the first lab run
Publish the Database and Collector roles in Azure Marketplace, or document how to deploy them in Azure The Marketplace offer is documented for the Hub; Database and Collector plans are unverified Open
A sample that keeps TLS verification on The SE PowerTools batch script disables certificate checks (community-projects.md) Open
A license on the liquidwarelabs sample repos, so the community can adapt them No license file (community-projects.md) Open
Document the Connector ID Key's exit codes, service names and settings key for scripted rollouts This KB marks them unverified (connector-id-key.md) Open
Linked from 2 pages