Hosting integration for Permify #1102
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1068
This PR adds hosting integration for Permify as discussed in #1068.
I've added methods for setting up the HTTP API, gRPC API, database support and watch support.
One part I need help with is the setup of OTLP, from what I gather there's a
.WithOtlpExporter()method which injects variables to configure the OTLP, however Permify uses it's own variables (specificallyPERMIFY_TRACER_ENDPOINTandPERMIFY_METER_ENDPOINT).AI suggested using
.WithEnvironmentwith a callback that fetches the endpoint variable and pass it on, however then it turns out Permify expects the host + port in the endpoint variables without a scheme.I'm looking for the recommended / idiomatic way to handle this.
PR Checklist
Other information
As described above, requires some fixes to the OTLP integration