Skip to content

Allow for resource type refs in schema #3069

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
guineveresaenger opened this issue May 13, 2025 · 0 comments · May be fixed by #3070
Open

Allow for resource type refs in schema #3069

guineveresaenger opened this issue May 13, 2025 · 0 comments · May be fixed by #3070
Assignees
Labels
area/tfgen Issues in pkg/tgen, excluding docs generation - use area/docsgen for those kind/bug Some behavior is incorrect or out of spec

Comments

@guineveresaenger
Copy link
Contributor

guineveresaenger commented May 13, 2025

Currently, when we add extra types that actually reference a resource, the bridge generates tokens of the format::
"$ref": "#/types/aws:apigateway/restApi:RestApi".

But aws:apigateway/restApi:RestApi is a resource, resulting in dangling schema types.

To fix this, the bridge should use the #resources prefix to the type ref.

Sample desired diff:

{
"type": "string",
-    "$ref": "#/types/aws:apigateway/restApi:RestApi"
+    "$ref": "#/resources/aws:apigateway/restApi:RestApi"
}
@pulumi-bot pulumi-bot added the needs-triage Needs attention from the triage team label May 13, 2025
@guineveresaenger guineveresaenger self-assigned this May 13, 2025
@guineveresaenger guineveresaenger added kind/bug Some behavior is incorrect or out of spec area/tfgen Issues in pkg/tgen, excluding docs generation - use area/docsgen for those and removed needs-triage Needs attention from the triage team labels May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tfgen Issues in pkg/tgen, excluding docs generation - use area/docsgen for those kind/bug Some behavior is incorrect or out of spec
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

2 participants