-
Notifications
You must be signed in to change notification settings - Fork 0
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
Idempotent mediator invitation url #113
Conversation
Signed-off-by: Clément Humbert <[email protected]>
If the invite is the same as last time, don't we want to skip creation of a new connection? |
Thanks for the review guys. This is the kind of feedback I was looking for since I'm still not fully acquainted with aca-py. I will submit an update next week. |
To ease Aca-py's deployment in scenarios where command line arguments cannot be changed easily, make `--mediatior-invitation` and `--mediator-connections-invite` available to the `provision` command. `provision` stores the mediator invite to be used by `start` command. If the invitation changed, `start` updates the stored invite and uses the new one. Signed-off-by: Clément Humbert <[email protected]>
2a14100
to
eeb1fbf
Compare
Whenever the conductor needs to setup a new mediation connection (eg: the invitation url provided by the command line arguments has changed), clear the old default mediator settings prior to setting up the new connection and default mediator. Signed-off-by: Clément Humbert <[email protected]>
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.
Looks good!
Thanks for the review, I'll open a PR on the original repo. |
Intermediary PR to make sure everything fits before proposing this on aca-py main repo.
Connection to the mediator is now established using the url stored at provision-time. If the invitation is changed, the new one is stored and used.
A new connection is still established at each start.