Move provisioning proxy steps to the new LSO endpoint
All threads resolved!
All threads resolved!
Move away from GÉANT-specific API endpoints in LSO, and instead make use of the generic one
Merge request reports
Activity
requested review from @mohammad.torkashvand
assigned to @sergio.gimenez
Without knowing much about how it was working before, I can see now you relay in this generic
execute_playbook
method instead of specific methods from the provisioning proxy. Looks a more generic approach and looks good to me :D. I'll wait for Mohammad's green light and then I'll merge it.Edited by Giménez, Sergiorequested review from @neda.moeini and removed review request for @mohammad.torkashvand
- Resolved by Karel van Klink
assigned to @karel.vanklink and unassigned @sergio.gimenez
@karel.vanklink Please rebase it. There are conflicts.
added 17 commits
-
2468574e...4caf2766 - 7 commits from branch
develop
- 20c2c8c3 - Add an indifferent pp interaction, that won't make the workflow fail despite the outcome
- 052520a6 - add generic playbook execution method to the provisioning proxy service
- f04758f2 - update typing of provisioning proxy inventory
- a4b2ba43 - add module for shared workflow steps
- 03843a6b - use built-in raise_for_status in provisioning proxy service
- 83a56040 - move create router workflow to new provisioning proxy endpoint
- c7aaea3f - move iptrunk workflows to new provisioning proxy endpoint
- b7cc4094 - remove unused provisioning proxy methods
- d1c4524d - split off duplicate code to helper method
- 6191d0fe - fix one unit test, and remove some unused code
Toggle commit list-
2468574e...4caf2766 - 7 commits from branch
enabled an automatic merge when the pipeline for 6191d0fe succeeds
Please register or sign in to reply