feat(registry): Add pgEdge provider package

[KnockOutEZ]

Description

This PR adds the pgEdge provider package to the Pulumi Registry. The pgEdge provider enables management of pgEdge Cloud resources, supporting both Developer and Enterprise editions. This provider allows users to manage databases, clusters, backup stores, and cloud accounts through Pulumi infrastructure as code.

Adding a new package?

If this pull request adds a new package:

• The package's schema URL in this PR is correct (provider/cmd/pulumi-resource-pgedge/schema.json).
• The package metadata file contains:
  • a supported category (Database).
  • a valid plugin download URL (via GitHub repo: https://github.com/pgedge/pulumi-pgedge).
  • a description ("A Pulumi package for creating and managing pgEdge Cloud resources.").
  • a valid logo URL (https://pgedge-public-assets.s3.amazonaws.com/product/images/pgedge_mark.svg).
• The package repo contains an Overview doc (/docs/_index.md) that includes:
  • a brief explanation of the pgEdge provider and its capabilities.
  • representative examples in TypeScript and Go.
  • front-matter layout property set to package.
• The package repo contains an Installation and Configuration doc (/docs/installation-configuration.md) that includes:
  • links to Node.js and Go SDKs.
  • installation commands for npm/yarn and go get.
  • configuration examples using environment variables (PGEDGE_CLIENT_ID and PGEDGE_CLIENT_SECRET).
• The repository has:
  • version tag v0.0.28 with corresponding GitHub release
• A CODEOWNER has reviewed the PR.
• A member of the @pulumi/docs team has reviewed all documentation.

Additional Notes:

• Package is currently in public preview status
• Supports both Developer and Enterprise editions with different feature sets
• Includes comprehensive support for database, cluster, and backup management
• Provides multi-region deployment capabilities

[iwahbe]

Hi @KnockOutEZ, thanks for opening a PR and writing such great docs. We will need to make a couple of changes before merging.

[iwahbe]

TitleLookup is being deprecated in favor of the "displayName" field in the provider schema. If you set tfbridge.ProviderInfo.DisplayName, then it will flow through.

We are not adding new packages to lookup.go.

[iwahbe]

Instead of setting this in the override map, please just set catagory/database in your schemas "keywords" section with tfbridge.ProviderInfo.Keywords.

[iwahbe]

This file is auto-generated, and will be added automatically.

[iwahbe]

Docs files are pulled from your repo. This file should live at github.com/pgedge/pulumi-pgedge/docs/_index.md. The registry will pick it up during builds.

This way the docs are:

1. Versioned with your provider.
2. Editable by you without going through our PR process.

[iwahbe]

Docs files are pulled from your repo. This file should live at github.com/pgedge/pulumi-pgedge/docs/installation-configuration.md. The registry will pick it up during builds.

[iwahbe]

This is the only change we need here.

[KnockOutEZ]

Thanks for the feedbacks @iwahbe . I just fixed the PR items and also updated the pulumi-pgedge repo.

[mjeffryes]

Thanks for the contribution @KnockOutEZ. A few questions:

• Our partnerships team likes to maintain an email contact for a maintainer on contributed providers. Can you share a contact to represent pgEdge as a maintainer of this provider?
• Our policy is generally to wait until all Pulumi languages are supported before publishing in our registry, but I noticed that support for python and dotnet SDKs are listed as coming soon. Can you please publish SDKs to PyPi and Nuget and update examples in your index and configuration docs to match?