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

[DPE-3551] Fix large objects ownership #390

Merged
merged 3 commits into from
Feb 19, 2024

Conversation

marceloneppel
Copy link
Member

@marceloneppel marceloneppel commented Feb 9, 2024

Issue

If we relate a charm like the MAAS operator to the PostgreSQL operator, remove the relation and relate again, then MAAS doesn't have access to the previously created PostgreSQL large objects.

#389

Solution

When a charm is related again to the PostgreSQL operator, give the ownership of the existing large objects to that charm user, as we already do for tables and other objects.

Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
…s-ownership

Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
@marceloneppel marceloneppel marked this pull request as ready for review February 19, 2024 11:48
@marceloneppel marceloneppel merged commit 76135cf into main Feb 19, 2024
41 checks passed
@marceloneppel marceloneppel deleted the dpe-3551-large-objects-ownership branch February 19, 2024 21:13
BON4 pushed a commit to BON4/postgresql-k8s-operator that referenced this pull request May 20, 2024
* Fix large objects ownership

Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>

* Bump LIBPATCH

Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>

---------

Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants