Skip to content
stackqlPublic

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Repository files navigation

🚨 🚨 FORMALLY DEPRECATED — DO NOT USE FOR NEW DEVELOPMENT 🚨 🚨

This repository is open ONLY for bug fixes and security upgrades. No new features or enhancements will be accepted. All functionality has migrated to omnisdk. Use omnisdk for all new development.


Platforms Go License Lines

any-sdk

A golang library to support:

  • traversal algorithms on StackQL augmented openapi doc structure.
  • SQL semantics thereupon.

From those who brought you

StackQL

Evolution to protocol agnostic

The basic idea is a full decouple and abstraction of the interface from openapi.

Based upon the fact that golang text templates are Turing complete, as are numerous other DSLs, we can use these to define and route SQL input to arbitrary interfaces. For instance, here is the brainf@$& interpreter described in the article.

As a side note, this review piece gives some insight into whay all DSLs wind up Turing complete and also therefore rather messy for narrowband purposes.

Provider document verification

Registry verification uses FIPS 204 ML-DSA-65 from Go's standard library. verifyConfig.nopVerify: true preserves unverified reads; false requires x-stackql-signature on every provider, service and referenced document read from a local registry, cache, or remote source. There is no .sig or certificate fallback. Verified readers parse the exact authenticated YAML payload returned by the shared github.com/stackql/stackql-provider-registry/signing/pqsig package.

verifyConfig.publicKeys may supply a kid to hex public-key map for a private registry; it replaces the embedded production roots. An empty map is invalid. The SDK's existing nil-config behavior is unchanged; StackQL supplies nopVerify: true by default. Archive extraction is outside this verification boundary.

Acknowledgements

Extensions, adaptations and shims of the following support our work:

We gratefully acknowledge these pieces of work.

Licensing

Please see the stackql LICENSE.

Licenses for third party software we are using are included in the /licenses directory.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages