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.

Sign up for GitHub

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

Jump to bottom

Failures in automatic aliasing for muxed providers #1937

Closed
t0yv0 opened this issue May 8, 2024 · 1 comment · Fixed by #1938
Closed

Failures in automatic aliasing for muxed providers #1937

t0yv0 opened this issue May 8, 2024 · 1 comment · Fixed by #1938
Assignees
@t0yv0
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Milestone
0.104

Comments

@t0yv0
Copy link
Member

t0yv0 commented May 8, 2024

What happened?

In the case of AWS new resources are developed with Plugin Framework, and AWS is in Pulumi is a muxed provider with an
SDKv2 base and a PF based overload. Unfortunately the auto-aliasing feature does not work as expected.

Specifically, introducing a "bedrockanalysis" module to move some resource tokens for best UX has failed AWS builds with
the following message:

error: failed to compute dispatch for muxed provider: Resources without backing provider:
  - aws_bedrockagent_agent_knowledge_base_association_legacy
  - aws_bedrockagent_agent_alias_legacy
  - aws_bedrockagent_agent_action_group_legacy
  - aws_bedrockagent_agent_legacy
  - aws_bedrockagent_knowledge_base_legacy
  make: *** [tfgen_no_deps

Example

See above.

Output of pulumi about

N/A

Additional context

N/A

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
@t0yv0 t0yv0 added needs-triage Needs attention from the triage team kind/bug Some behavior is incorrect or out of spec labels May 8, 2024
t0yv0 added a commit that referenced this issue May 8, 2024
@t0yv0
Fix automatic aliasing of muxed providers
bfaea6b 
Fixes #1937

This PR fixes the automatic aliasing of muxed providers by dispatching a ResourceMap Clone operation to the sub-map that
owns the key being cloned and making PF resource maps mutable.
@t0yv0 t0yv0 mentioned this issue May 8, 2024
Merged
@t0yv0
Copy link
Member Author

t0yv0 commented May 8, 2024

I have a fix PR.

This was referenced May 8, 2024
Merged
Open
@iwahbe iwahbe removed the needs-triage Needs attention from the triage team label May 9, 2024
t0yv0 added a commit that referenced this issue May 15, 2024
@t0yv0
Fix automatic aliasing of muxed providers
599d38d 
Fixes #1937

This PR fixes the automatic aliasing of muxed providers by dispatching a ResourceMap Clone operation to the sub-map that
owns the key being cloned and making PF resource maps mutable.
t0yv0 added a commit that referenced this issue May 15, 2024
@t0yv0
Fix automatic aliasing of muxed providers (#1938)
1c1c073 
Fixes #1937

This PR fixes the automatic aliasing of muxed providers by dispatching a
ResourceMap Clone operation to the sub-map that owns the key being
cloned and making PF resource maps mutable.
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label May 15, 2024
@t0yv0 t0yv0 added this to the 0.104 milestone May 15, 2024
guineveresaenger added a commit to pulumi/pulumi-okta that referenced this issue May 22, 2024
@guineveresaenger
Use latest bridge to avoid pulumi/pulumi-terraform-bridge#1937 on tfgen
cdaebf8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@t0yv0 t0yv0

Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Milestone
0.104
Development

Successfully merging a pull request may close this issue.

Fix automatic aliasing of muxed providers pulumi/pulumi-terraform-bridge
3 participants
@t0yv0 @iwahbe @pulumi-bot