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

Use actual tf plugin sdk version from bridge in provider upgrades #245

Closed
VenelinMartinov opened this issue Feb 1, 2024 · 1 comment
Closed

Use actual tf plugin sdk version from bridge in provider upgrades #245

VenelinMartinov opened this issue Feb 1, 2024 · 1 comment
Labels
kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue

Comments

@VenelinMartinov
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

We currently upgrade providers to the newest plugin sdk version, which could be newer than the replace in the bridge we are upgrading to.

We could instead parse the bridge replace directive and use the same version in the provider.

Affected area/feature
@VenelinMartinov VenelinMartinov added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Feb 1, 2024
@VenelinMartinov VenelinMartinov mentioned this issue Feb 1, 2024
Merged
@iwahbe iwahbe added resolution/duplicate This issue is a duplicate of another issue and removed needs-triage Needs attention from the triage team labels Feb 1, 2024
@iwahbe
Copy link
Member

iwahbe commented Feb 1, 2024

@VenelinMartinov This looks like a duplicate of #243.

@iwahbe iwahbe closed this as not planned Won't fix, can't repro, duplicate, stale Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iwahbe @VenelinMartinov