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

Bugfix/pulsar manager persistence #485

Merged
merged 1 commit into from
Apr 4, 2024

Conversation

Mortom123
Copy link
Contributor

Fixes #470

Motivation

Reconditioning the pulsar manager after reinstall should not be necessary and data should be persisted.

Modifications

Multiple modifications. It did not work beforehand because SPRING_CONFIGURATION_FILE was set in the environment resulting in a default configuration.

During my investigations, I found out that the pulsar manager does not setup the database correctly and instead defaults to user/password = pulsar/pulsar.
Once the changes on the side of the manager are implemented the same credentials as specified should be used.
See: apache/pulsar-manager#556

Verifying this change

  • Make sure that the change passes the CI checks.

only setup environment in pulsar manager if broker is deployed

fix indent

enable persistence for manager and move configs around
@Mortom123
Copy link
Contributor Author

I think this solves the previous issues @lhotari @wuyudian1

@lhotari
Copy link
Member

lhotari commented Apr 3, 2024

Awesome work @Mortom123 ! Thank you

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.

Pulsar Manager v0.4.0 in kubernetes still can not persist any data
2 participants