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

fix: Do not integrate an invalid relation #509

Merged
merged 2 commits into from
Oct 15, 2024

Conversation

Gu1nness
Copy link
Contributor

Issue

It is needed to check first if the relation is valid.

Solution

The reusable check works with proxy relations (so config-server can get data proxified by mongos), so we first check here that the basic relation is valid.

This should be improved in the future to make it more straightforward.

It is needed to check first if the relation is valid.
The reusable check works with proxy relations (so config-server can get
data proxified by mongos), so we first check here that the basic
relation is valid.

This should be improved in the future to make it more straightforward.
Mehdi-Bendriss
Mehdi-Bendriss previously approved these changes Oct 14, 2024
lib/charms/mongodb/v1/mongodb_provider.py Outdated Show resolved Hide resolved
lib/charms/mongodb/v1/mongodb_provider.py Outdated Show resolved Hide resolved
lib/charms/mongodb/v1/mongodb_provider.py Outdated Show resolved Hide resolved
@Gu1nness Gu1nness force-pushed the fix/do-not-integrate-if-relation-not-feasible branch from d21702d to 7d0cec2 Compare October 15, 2024 08:22
@Gu1nness Gu1nness merged commit 33eb4b4 into 6/edge Oct 15, 2024
30 of 33 checks passed
@Gu1nness Gu1nness deleted the fix/do-not-integrate-if-relation-not-feasible branch October 15, 2024 11:34
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.

3 participants