path based routing on hasura

[moshtab]

Can we do path based routing on hasura? If we can then what should be the context path. Please suggest

[adas98012]

Hasura does not have a "routing" feature, much less "path based routing".

Can you expand on what you mean by "path based routing"?
Perhaps links to external resources so we can understand your question?

[moshtab]

Hi, Suppose if we writing ingress rules which is pointing to hasura service For example spec: rules: - http: paths: - path: /What should be mentioned here? backend: serviceName: hasura-service servicePort: 8080 So, in the above example, what should be the value for path, if iam going with path based routing.....

…

On Mon, 22 Aug 2022, 11:17 pm adas98012, ***@***.***> wrote: Hasura does not have a "routing" feature, much less "path based routing". Can you expand on what you mean by "path based routing"? Perhaps links to external resources so we can understand your question? — Reply to this email directly, view it on GitHub <#8817 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUX4C53QUAJ27QXACPNQ4MTV2O4JPANCNFSM567U4JZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[BenoitRanque]

Hasura does not have routing functionality.
If you are handling routing in a reverse proxy or similar, you would need to defer to the documentation of that server.

If you are using hasura cloud you would typically point to your hasura instance's endpoint.

[dsandip]

I could be wrong, but perhaps the path in the ingress/reverse-proxy will be something like <domain-where-hasura-is-deployed>/v1/graphql (e.g. https://localhost:8080/v1/graphql or https://moshtab.hasura.app/v1/graphql

[86label]

I have tried what you're suggesting, and found the following to be needed in an ingress to point to 2 different services using one ingress.

rules:
  - host: my-host.someurl.com
    http:
      paths:
      - backend:
          service:
            name: hasura-service
            port:
              number: 443
        path: /console
        pathType: ImplementationSpecific
      - backend:
          service:
            name: hasura-service
            port:
              number: 443
        path: /v1
        pathType: ImplementationSpecific
      - backend:
          service:
            name: hasura-service
            port:
              number: 443
        path: /v2
        pathType: ImplementationSpecific
      - backend:
          service:
            name: otherapp-service
            port:
              number: 443
        path: /
        pathType: ImplementationSpecific

[BenoitRanque]

I see, you seem to be setting up some ingress configuration for some third party service.

Besides the /console endpoint, you could look at our API Reference for a list of endpoints hasura has.

[moshtab]

Hi Hasura/Graphql-Engine Can we change the hasura console context path? Suppose i want to add a prefix to my hasura url like below <my_domain>/test/console Can we do this? If we can then what are the possible ways..

…

On Wed, 24 Aug 2022, 8:55 pm Benoit Ranque, ***@***.***> wrote: I see, you seem to be setting up some ingress configuration for some third party service. Besides the /console endpoint, you could look at our API Reference <https://hasura.io/docs/latest/api-reference/index/> for a list of endpoints hasura has. — Reply to this email directly, view it on GitHub <#8817 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUX4C5Y66DONPOXDRXUURILV2Y5HJANCNFSM567U4JZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[akhil-naidu]

Jumping here to clarify a few things. Let us assume the below was your ingress configuration.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: hasura-ingress
  namespace: hasura
spec:
  rules:
  - host: hasura.yourdomian.com
    http:
      paths:
      - path: /hasura
        backend:
          serviceName: hasura-svc
          servicePort: 8080

Note 1: The above configuration alias to, when a public user reaches to https://hasura.yourdoman.com/hasura it will reach out to the hasura-svc:8080 which can be multiple instances.

Note 2: To work with the Hasura GraphQL engine, one should be able to send a POST request to the URI: hasura-svc:8080/v1/graphql

Note 3: Based on the above path-based ingress configuration,

1. You can access Hasura Console(Web UI) at https://hasura.yourdomian.com/hasura/console
2. You need to send a POST request to https://hasura.yourdomian.com/hasura/v1/graphql to execute your GQL Queries/Mutation/Subscriptions

[moshtab]

Hi Hasura/Graphql-Engine, I have tried the above but still the console is not opening

…

On Mon, 5 Sept 2022, 10:48 am Akhil Naidu, ***@***.***> wrote: Jumping here to clarify a few things. Let us assume the below was your ingress configuration. apiVersion: extensions/v1beta1kind: Ingressmetadata: name: hasura-ingress namespace: hasuraspec: rules: - host: hasura.yourdomian.com http: paths: - path: /hasura backend: serviceName: hasura-svc servicePort: 8080 *Note 1*: The above configuration alias to, when a public user reaches to https://hasura.yourdoman.com/hasura it will reach out to the hasura-svc:8080 which can be multiple instances. *Note 2*: To work with the Hasura GraphQL engine, one should be able to send a POST request to the URI: hasura-svc:8080/v1/graphql *Note 3*: Based on the above path-based ingress configuration, 1. You can access Hasura Console(Web UI) at https://hasura.yourdomian.com/hasura/console 2. You need to send a POST request to https://hasura.yourdomian.com/hasura/v1/graphql to execute your GQL Queries/Mutation/Subscriptions — Reply to this email directly, view it on GitHub <#8817 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUX4C57BKJZ63KR7RB4PXOTV4V7DDANCNFSM567U4JZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[moshtab]

Hi Hasura/Graphql-Engine, I am using ingress rule as below - host: ede.firstrepublictest.com http: paths: - path: /cbxbo-hasura pathType: Prefix backend: serviceName: cbxbo-hasura-service servicePort: 80 When I am trying to hit hasura console with http://ede.firstrepublictest.com/cbxbo-hasura/console then iam getting below response {"path":"$","error":"resource does not exist","code":"not-found"}

…

On Mon, Sep 5, 2022 at 12:08 PM md mohsin ***@***.***> wrote: Hi Hasura/Graphql-Engine, I have tried the above but still the console is not opening On Mon, 5 Sept 2022, 10:48 am Akhil Naidu, ***@***.***> wrote: > Jumping here to clarify a few things. Let us assume the below was your > ingress configuration. > > apiVersion: extensions/v1beta1kind: Ingressmetadata: > name: hasura-ingress > namespace: hasuraspec: > rules: > - host: hasura.yourdomian.com > http: > paths: > - path: /hasura > backend: > serviceName: hasura-svc > servicePort: 8080 > > *Note 1*: The above configuration alias to, when a public user reaches > to https://hasura.yourdoman.com/hasura it will reach out to the > hasura-svc:8080 which can be multiple instances. > > *Note 2*: To work with the Hasura GraphQL engine, one should be able to > send a POST request to the URI: hasura-svc:8080/v1/graphql > > *Note 3*: Based on the above path-based ingress configuration, > > 1. You can access Hasura Console(Web UI) at > https://hasura.yourdomian.com/hasura/console > 2. You need to send a POST request to > https://hasura.yourdomian.com/hasura/v1/graphql to execute your GQL > Queries/Mutation/Subscriptions > > — > Reply to this email directly, view it on GitHub > <#8817 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AUX4C57BKJZ63KR7RB4PXOTV4V7DDANCNFSM567U4JZQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[moshtab]

Hi Hasura/Graphql-Engine, I am using ingress rule as below - host: hasura_domain http: paths: - path: /cbxbo-hasura pathType: Prefix backend: serviceName: cbxbo-hasura-service servicePort: 80 When I am trying to hit hasura console with http://hasura_domain/cbxbo-hasura/console <http://ede.firstrepublictest.com/cbxbo-hasura/console> then iam getting below response {"path":"$","error":"resource does not exist","code":"not-found"}

…

On Mon, Sep 5, 2022 at 12:08 PM md mohsin ***@***.***> wrote: Hi Hasura/Graphql-Engine, I have tried the above but still the console is not opening On Mon, 5 Sept 2022, 10:48 am Akhil Naidu, ***@***.***> wrote: > Jumping here to clarify a few things. Let us assume the below was your > ingress configuration. > > apiVersion: extensions/v1beta1kind: Ingressmetadata: > name: hasura-ingress > namespace: hasuraspec: > rules: > - host: hasura.yourdomian.com > http: > paths: > - path: /hasura > backend: > serviceName: hasura-svc > servicePort: 8080 > > *Note 1*: The above configuration alias to, when a public user reaches > to https://hasura.yourdoman.com/hasura it will reach out to the > hasura-svc:8080 which can be multiple instances. > > *Note 2*: To work with the Hasura GraphQL engine, one should be able to > send a POST request to the URI: hasura-svc:8080/v1/graphql > > *Note 3*: Based on the above path-based ingress configuration, > > 1. You can access Hasura Console(Web UI) at > https://hasura.yourdomian.com/hasura/console > 2. You need to send a POST request to > https://hasura.yourdomian.com/hasura/v1/graphql to execute your GQL > Queries/Mutation/Subscriptions > > — > Reply to this email directly, view it on GitHub > <#8817 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AUX4C57BKJZ63KR7RB4PXOTV4V7DDANCNFSM567U4JZQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[akhil-naidu]

The service port should be 8080(the default port exposed by Hasura). You can also verify the port number in this line.

[moshtab]

Even after mentioning the service port to 8080, its still same issue

…

On Mon, Sep 5, 2022 at 12:58 PM Akhil Naidu ***@***.***> wrote: The service port should be 8080(the default port exposed by Hasura). You can also verify the port number in this line <https://github.com/hasura/graphql-engine/blob/master/install-manifests/kubernetes/deployment.yaml#L34> . — Reply to this email directly, view it on GitHub <#8817 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUX4C56DQAKWGFB6BHOSCSLV4WOIHANCNFSM567U4JZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>