-
Notifications
You must be signed in to change notification settings - Fork 0
OPSEXP-3125 hxi_connector: handle repository extension properties in the extension entrypoint #13
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
Conversation
Docs Build 📝The docs for this PR have been published here: You can compare to the docs for the |
* improve documentation and entrypoint metadata
2d6ca45
to
c2422a3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just realising that now, but why are we using the side-effect playbook?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's something you did a while ago in the upstream role, looks like to verify that the service get reloaded upon config change.
here I've reused it to actually test both behaviors of the extension entrypoint (when passing all the arguments vs only the required ones)
70d1b8c
to
46ce551
Compare
This reverts commit dc39996.
9da85e8
to
d32ea60
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
OPSEXP-3125