Tirumarai Selvan

Unfortunately, not at the moment. Maybe we can have a `dryRun` flag in the `deployment` section of the `remote`. This is quite easy to implement. Any takers?

@gaui Few examples for both mono and multi repo organizations are given here: https://github.com/hasura/gitkube-example

@disha94 which version did you have the issue with and which issue fixed it for you? We have docs/minikube.md where we can mention this.

@mandarku Could you please specify additional details like which Kubernetes version, which provider (if any), etc. You may want to open a new issue just for this.

@mandarku Yes, as the error suggest your K8s version does not have the APIs like ClusterRoleBinding or CustomResourceDefinition (or have it in a different api group). Hence, gitkube works only...

One workaround could be to set `HASURA_GRAPHQL_LIVE_QUERIES_MULTIPLEXED_REFETCH_INTERVAL` to a larger value like 10s or more which can give sufficient time for the migration to execute without conflicting with the subscription.

We are thinking of extending the `custom_types` metadata to have an `import_enums_from_table` field which can take a list of enum tables. Those enums will be available to automatically use in...

Hi @abseht 1. Do you see the same runtime characteristics with 2.32 or earlier? 2. What kind of workload are you running your Hasura? The more detailed the better to...

I agree that it makes sense to add `scheme` customization to CustomHeader. We will add it to our backlog but it may take a couple of weeks to prioritize this.

I think it is because of inefficient indexes on `hdb_catalog.event_log` table that is causing more than required disk IOPS. We have fixed this in `main` recently and should be out...