You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sounds like a good companion to the auth choices available with Keycloak and the proposed OpenFGA (#1043) integration.
Consider how the config would be managed - is there a .NET object model that exists (maybe the SDK?) for the YAML config file, otherwise, how would the database be effectively provided from the PostgreSQL resource to the Permify container.
The track_commit_timestamp is optional and only required when using the watch service.
If you don't pass in the postgres bit it just runs entirely in-memory (but it won't persist and the watch service doesn't work as it relies on Postgres for notifications).
I think the only thing I'd have to look into (but I'm sure you guys know this off the top of your head) is that Permify exposes 2 endpoints, a HTTP one and gRPC one and preferably I'd inject both with just .WithReference(permify) rather than the WithHttpEndpoint I'm doing now.
My clienta side there's I think around 2 other clients that could be used, though I don't know how well they integrate with Aspire as-is.
What about the config file described here? How much of that can be modelled in the app host or should people be expected to write a YAML file that it consumes?
For providing the endpoints to a client, that's easily done using a connection string and just defining a custom format that you want to consume.
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.
Activity
aaronpowell commentedon Dec 16, 2025
Sounds like a good companion to the auth choices available with Keycloak and the proposed OpenFGA (#1043) integration.
Consider how the config would be managed - is there a .NET object model that exists (maybe the SDK?) for the YAML config file, otherwise, how would the database be effectively provided from the PostgreSQL resource to the Permify container.
dealloc commentedon Dec 17, 2025
I'm writing a .NET client right now over at dealloc/permify-client, for the Aspire example I'm currently using the following code:
The
track_commit_timestampis optional and only required when using the watch service.If you don't pass in the postgres bit it just runs entirely in-memory (but it won't persist and the watch service doesn't work as it relies on Postgres for notifications).
I think the only thing I'd have to look into (but I'm sure you guys know this off the top of your head) is that Permify exposes 2 endpoints, a HTTP one and gRPC one and preferably I'd inject both with just
.WithReference(permify)rather than theWithHttpEndpointI'm doing now.My clienta side there's I think around 2 other clients that could be used, though I don't know how well they integrate with Aspire as-is.
aaronpowell commentedon Dec 17, 2025
What about the config file described here? How much of that can be modelled in the app host or should people be expected to write a YAML file that it consumes?
For providing the endpoints to a client, that's easily done using a connection string and just defining a custom format that you want to consume.
dealloc commentedon Dec 18, 2025
All YAML configuration can be passed as environment variables by prefixing with
PERMIFY_and uppercasing everything.so the Yaml path
service.watch.enabledwould becomePERMIFY_SERVICE_WATCH_ENABLED(which I actually have in my previous example).as far as I'm aware, no yaml required :)
dealloc commentedon Dec 19, 2025
@aaronpowell when making a PR, do I target
mainoraspire-13.1like in #1021 ?github-actions commentedon Jan 10, 2026
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use
/stale-extendto extend the window.dealloc commentedon Jan 10, 2026
/stale-extend
aaronpowell commentedon Jan 12, 2026
Target
main, as I will get around to doing a merge of the 13.1 branch and release that soondealloc commentedon Jan 20, 2026
@aaronpowell opened a PR, added some questions regarding potential conflicts and the OTLP integration
github-actions commentedon Mar 31, 2026
We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use
/stale-extendto extend the window.github-actions commentedon Apr 14, 2026
This issue has been stale for 5 weeks and has been automatically closed.