Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulumi schema for resource references #15681

Closed
Tracked by #1971
EronWright opened this issue Mar 14, 2024 · 3 comments
Closed
Tracked by #1971

Pulumi schema for resource references #15681

EronWright opened this issue Mar 14, 2024 · 3 comments
Labels
area/component-packages aka multi-language components kind/enhancement Improvements or new features needs-triage Needs attention from the triage team resolution/duplicate This issue is a duplicate of another issue

Comments

@EronWright
Copy link
Contributor

Hello!

  • Vote on this issue by adding a 馃憤 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

As a component provider author, I would like to define an output property called resources whose type would be an array of resources that were produced by the component. The provider code would assumedly return ResourceReference property values. At the SDK level, I would expect the resources property to have a type of ResourceArray.

Affected area/feature

Workarounds

Use pulumi.json#/Any:

            "properties": {
                "resources": {
                    "type": "array",
                    "items": {
                        "$ref": "pulumi.json#/Any"
                    },
                    "description": "Resources created by the component."
                }
            }
@EronWright EronWright added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team area/component-packages aka multi-language components labels Mar 14, 2024
@EronWright
Copy link
Contributor Author

This is related to this conversation.

@lukehoban
Copy link
Member

I expect we would accomplish this by adding one (or three) new built in types to Pulumi schema:

  1. pulumi.json#/Resource
  2. pulumi.json#/CustomResource
  3. pulumi.json#/ComponentResource

And then add support for these in codegen for each language.

@justinvp
Copy link
Member

This is a dupe of #6346

@lukehoban lukehoban added the resolution/duplicate This issue is a duplicate of another issue label Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/component-packages aka multi-language components kind/enhancement Improvements or new features needs-triage Needs attention from the triage team resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants