-
Notifications
You must be signed in to change notification settings - Fork 47
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
How to deal with optional/unsupported keys? #14
Comments
It would include the new (optional) keys for this. It would likely also include a flag in the provider databag saying
Ignore. However, the requirer would check for
in combination with two requirer expectations:
If this is an optional feature, it would be happy without it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suppose I have two charms providing the ingress interface (interoperable).
One of them adds a new feature (say, TLS), to the ingress library and make it optional so that it will still support integrating with providers or requirers using earlier versions.
The text was updated successfully, but these errors were encountered: