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

Create forward compatibility layer for new configuration format #884

Open
alcaeus opened this issue Dec 2, 2019 · 0 comments
Open

Create forward compatibility layer for new configuration format #884

alcaeus opened this issue Dec 2, 2019 · 0 comments
Labels

Comments

@alcaeus
Copy link
Member

alcaeus commented Dec 2, 2019

3.0 brings a new configuration format to allow for multiple namespaces. To avoid a hard BC break, we should add a forward compatibility layer to 2.3 that allows people to change the configuration to the new format. However, since 2.x only supports a single namespace, the config reader should throw an exception when more than one migration namespace is configured.

This also entails deprecating the old configuration format for removal.

@alcaeus alcaeus added this to the 2.3.0 milestone Dec 2, 2019
@greg0ire greg0ire modified the milestones: 2.3.0, 2.4.0 Oct 28, 2020
@derrabus derrabus removed this from the 2.4.0 milestone Nov 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants