Visitar URL original
Add conformance test for using a provider in a component by Frassle · Pull Request #23904 · pulumi/pulumi · GitHub
Skip to content

Add conformance test for using a provider in a component - #23904

Merged
Frassle merged 4 commits into
masterfrom
fraser/l3compprov
Jul 13, 2026
Merged

Frassle merged 4 commits into
masterfrom
fraser/l3compprov

Conversation

@Frassle

@Frassle Frassle commented Jul 13, 2026

Copy link
Copy Markdown
Member

Towards fixing #23896. Get a conformance test added to check that a component can declare and use a provider resource.

This needed pcl.MapProvidersAsResources called when generating component programs to fix up the type tokens.

@Frassle
Frassle marked this pull request as ready for review July 13, 2026 12:05
@Frassle
Frassle requested a review from a team as a code owner July 13, 2026 12:05
@Frassle
Frassle force-pushed the fraser/l3compprov branch from fedba48 to fe8b716 Compare July 13, 2026 12:14
@Frassle
Frassle enabled auto-merge July 13, 2026 14:42
@Frassle
Frassle added this pull request to the merge queue Jul 13, 2026
Merged via the queue into master with commit f669f79 Jul 13, 2026
128 checks passed
@Frassle
Frassle deleted the fraser/l3compprov branch July 13, 2026 16:28
@pulumi-bot

Copy link
Copy Markdown
Contributor

This PR has been shipped in release v3.253.0.

iwahbe added a commit to pulumi/pulumi-java that referenced this pull request Jul 21, 2026
The l3-component-provider conformance test is new in pulumi/pulumi v3.253.0
(pulumi/pulumi#23904). Java codegen does not emit the component resource
declaration, so the generated program fails to compile with "cannot find
symbol: myComponent". pulumi-language-go expects this test to fail for a
similar reason.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants