graphql-engine icon indicating copy to clipboard operation
graphql-engine copied to clipboard
verified publisher icon hasura

docs: add Cloud Foundry deployment guide

Open 0NIKHIL0 opened this issue 2 months ago • 1 comments

Add comprehensive guide for deploying and configuring Hasura on Pivotal Cloud Foundry (PCF). This resolves issue #2891 by providing step-by-step instructions for deploying Hasura GraphQL Engine on Cloud Foundry, including database setup, configuration, scaling, and troubleshooting.

Description

Changelog

Component : server / cli / console / build

Type: bugfix / feature / enhancement

Product: community-edition

Short Changelog

Long Changelog

Related Issues

Solution and Design

Steps to test and verify

Limitations, known bugs & workarounds

Server checklist

Catalog upgrade

Does this PR change Hasura Catalog version?

  • [ ] No
  • [ ] Yes
    • [ ] Updated docs with SQL for downgrading the catalog

Metadata

Does this PR add a new Metadata feature?

  • [ ] No
  • [ ] Yes
    • Does run_sql auto manages the new metadata through schema diffing?
      • [ ] Yes
      • [ ] Not required
    • Does run_sql auto manages the definitions of metadata on renaming?
      • [ ] Yes
      • [ ] Not required
    • Does export_metadata/replace_metadata supports the new metadata added?
      • [ ] Yes
      • [ ] Not required

GraphQL

  • [ ] No new GraphQL schema is generated
  • [ ] New GraphQL schema is being generated:
    • [ ] New types and typenames are correlated

Breaking changes

  • [ ] No Breaking changes

  • [ ] There are breaking changes:

    1. Metadata API

      Existing query types:

      • [ ] Modify args payload which is not backward compatible
      • [ ] Behavioural change of the API
      • [ ] Change in response JSON schema
      • [ ] Change in error code

    2. GraphQL API

      Schema Generation:

      • [ ] Change in any NamedType
      • [ ] Change in table field names

      Schema Resolve:-

      • [ ] Change in treatment of null value for any input fields

    3. Logging

      • [ ] Log JSON schema has changed
      • [ ] Log type names have changed

0NIKHIL0 avatar Nov 01 '25 06:11 0NIKHIL0

This appears to be AI-generated with a few outdated concepts and issues, @0NIKHIL0. Have you been through this guide yourself?

robertjdominguez avatar Nov 18 '25 23:11 robertjdominguez