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

feat: add priority plugin chain order with plugin reload #62

Merged
merged 4 commits into from
May 13, 2024

Conversation

VivekPipaliya23
Copy link

Proposed Changes

The current functionality of the Plugin loading priority order loads the plugins in a specific order when Vernemq starts up. However, it does not maintain this order after any plugin reloads via vmq-admin. This pull request aims to extend the functionality of the plugin priority order set in vernemq.conf, which will ensure that the priority order is maintained even after a plugin reload.

Types of Changes

  • Bugfix (non-breaking change which fixes issue #XXXX)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (correction or otherwise)
  • Cosmetics (whitespace, styles...)
  • DevOps (Build scripts, pipelines...)

Checklist

  • I have read the CODE_OF_CONDUCT.md document
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if needed)
  • Any dependent changes have been merged and published in related repositories
  • I have updated changelog (At the bottom of the release version)
  • I have squashed all my commits into one before merging

@VivekPipaliya23 VivekPipaliya23 force-pushed the feat/add-priority-order-to-plugin-chain branch from 2adbc60 to 48928ae Compare May 9, 2024 08:52
@dhruvjain99 dhruvjain99 merged commit 54d2f80 into main May 13, 2024
3 checks passed
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.

2 participants