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

Ensure tracking upstream replacements and excludes #3076

Open
t0yv0 opened this issue Dec 1, 2023 · 0 comments
Open

Ensure tracking upstream replacements and excludes #3076

t0yv0 opened this issue Dec 1, 2023 · 0 comments
Labels
kind/engineering Work that is not visible to an external user

Comments

@t0yv0
Copy link
Member

t0yv0 commented Dec 1, 2023

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

Follow-up on: #2987

Our bridged provider is inheriting issues from upstream provider through the dependency chain. When upstream mitigates the issues by Go replace or exclude directives, it would be ideal for the Pulumi provider to follow that, so that it uses the exact same dependencies as upstream. Unfortunately nothing guarantees this today, causing issues like 2987.

Affected area/feature
@t0yv0 t0yv0 added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Dec 1, 2023
@iwahbe iwahbe removed the needs-triage Needs attention from the triage team label Dec 2, 2023
@t0yv0 t0yv0 added kind/engineering Work that is not visible to an external user and removed kind/enhancement Improvements or new features labels Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/engineering Work that is not visible to an external user
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@t0yv0 @iwahbe