turbot / steampipe-plugin-sdk

Steampipe Plugin SDK is a simple abstraction layer to write a Steampipe plugin. Plugins automatically work across all engine types including the Steampipe CLI, Postgres FDW, SQLite extension and the export CLI.

https://hub.steampipe.io/plugins

turbot/steampipe-plugin-sdk Issues

QueryData passed to `ConnectionKeyColumns` value callback is not populated with ConnectionManager
Closed 8 days ago
Remove QualMapToJSONString and instead add QualMapToSerializableSlice
Closed a month ago
Operator `<>` is not working properly
Updated 2 months ago
Unexpected hydrate call count from query stats
Updated 2 months ago
Add support for connection key columns
Closed 2 months ago
Add `sp_ctx` and sp`connection_name` columns to all tables
Closed 2 months ago
AWS plugin: IgnoreConfig codes are not functioning as expected
Updated 2 months ago1
Minimally hosting a plugin
Updated 3 months ago4
The original function names for Memoized hydrate calls are incorrectly resolved.
Closed 3 months ago
If cache is disabled for the server, but enabled for the client, the query execution code tries to stream to the cache even though there is not active set operation
Closed 3 months ago
Fix error invalid URL escape "% ^"
Updated 4 months ago
When deleting and then re-adding a connection, get a "plugin has no connections" error
Closed 5 months ago
encapsulate plugin server so it is possible to use it in-process as well as via GRPC
Closed 5 months ago
Add version metadata to the _ctx column
Closed 5 months ago
Transform `NullIfEmptySliceValue` failed with panic reflect
Closed 6 months ago
Update proto.ColumnDefinition (part of GetSchemaResponse) to include column default and hydrate func
Closed 6 months ago
Verify, re-design(if needed) and re-enable caching tests
Updated 6 months ago
Show the name of the connection that failed along with the error message
Closed 6 months ago
Cache parameters cannot be set independently
Updated 6 months ago
Query fails to executed with multiple `IN` operator in where clause.
Updated 6 months ago
Incompatible package for azure-ad plugin
Closed 6 months ago1
Getting an error when trying to load child properties of an object from the connection config
Updated 6 months ago3
Update connection cache to use a backing store per connection, rather than a shared backing store
Closed 6 months ago
Can we add support for map/object in configSchema
Updated 7 months ago1
initialise is not being called for implicit hydrate config - this leads to a nil reference error if the hydrate function returns an error
Closed 7 months ago
Improve logging for connection config updates and connection cache clearing
Closed 7 months ago
Add GRPC endpoint to clear connection cache
Closed 8 months ago
_ctx column is showing delay for hydrate calls even if there are no rate limiters
Closed 8 months ago
list func names for parent/child hydrate functions are not populated in `_ctx` field
Closed 8 months ago
Validate plugin rate limiters names to ensure they are valid HCL names
Closed 8 months ago1
Fix STEAMPIPE_DIAGNOSTIC_LEVEL over STEAMPIPE_DIAGNOSTICS_LEVEL
Closed 8 months ago1
Deprecate STEAMPIPE_DIAGNOSTICS_LEVEL
Closed 8 months ago
Add `function_name` into hydrate call scope values
Closed 8 months ago
Crash when selecting table with memoized hydrate calls
Closed 8 months ago
When a hydrate call is memoized, the wrapped hydrate func has the name `func1` which may cauise issues for any code which uses the hydrate name
Closed 8 months ago1
Rename `connection` in _ctx back to `connection_name`
Closed 8 months ago
Add support for multiple instances of a plugin version to be run
Closed 8 months ago
The getSourceFiles function throws an error when file paths are unavailable in CWD
Updated 8 months ago
Ensure consistency of namedHydrateFunc usage
Closed 8 months ago
Add Equals function for QualValue
Closed 8 months ago
Rate limiters should not apply to memoized hydrate functions
Closed 8 months ago
Memoized functions appear with a function name of `func1` in the _ctx field
Closed 8 months ago
Show rate limiter properties in _ctx even if they are empty/zero
Closed 8 months ago
When resolving rate limiters, apply `where` filter even to properties not in the scope
Closed 8 months ago
get fails if there is a matrix - rate limiters atre not initialised because we are using parent query data not matrix query data
Closed 8 months ago
Add support for rate limiting
Closed 8 months ago
`CallId` in the log is not consistent with the `callId` prefix in the log
Updated 9 months ago
Use custom `io.Writer` in plugin logger in SDK.
Closed 9 months ago
When plugin startup experiences panic, write known string to stdout so plugin manager can intercept the "Unrecognized remote plugin message" and instead return the panic message
Closed 9 months ago
Enable OpenTelemetry metrics
Closed 10 months ago