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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce mux and port the provider to v6. #1

Merged

Conversation

dimuon
Copy link
Owner

@dimuon dimuon commented Sep 6, 2022

Description

Port existing provider to v6.
It should allow us to

  • create a new provider
  • port data sources and resources to the new provider
  • once all data sources and resources are ported, we can remove mux.

The approach should allow us to keep almost the full functionality of the provider available during the migration process.

Related Issues

Motivation and Context

How Has This Been Tested?

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (improves code quality but has no user-facing effect)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation

Readiness Checklist

  • My code follows the code style of this project
  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed

Copy link
Collaborator

@pascal-hofmann pascal-hofmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome. This looks really good and will make a transition to the framework very smooth. I'll rebase my changes on your code once it's merged.

@dimuon dimuon merged commit 043bbe7 into feature/530/migrate-to-plugin-framework Sep 7, 2022
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.

2 participants