SG-43459 Migrate Build scene/template workflows#145
SG-43459 Migrate Build scene/template workflows#145carlos-villavicencio-adsk wants to merge 35 commits into
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## ticket/SG-43456_migration_1 #145 +/- ##
==============================================================
Coverage ? 19.16%
==============================================================
Files ? 51
Lines ? 4841
Branches ? 0
==============================================================
Hits ? 928
Misses ? 3913
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
chenm1adsk
left a comment
There was a problem hiding this comment.
Left some question of improvement that I am not sure if we should aim for in the scope of this ticket.
| if len(actions) == 0: | ||
| actions.extend(list(mappings.get("All", []))) |
There was a problem hiding this comment.
Not introduced by this PR but as I mentioned in phase1 PR, this will change the behaviour of when to append actions in "All", we shouldn't introduce to tk-multi-loader2.
| enable_flowam = app.get_setting("enable_flowam", False) | ||
| if enable_flowam: | ||
| am_base_obj = kwargs.get("am_base_obj") | ||
| if self.parent.context.flow_project_id: |
There was a problem hiding this comment.
I feel like it is better to just create a function to group flow logic.
For example create a _flow_execute_action and called it when flow project id exists
Base branch #137
Requirements
Description
This will prevent having these workflows dependant from tk-framework-flowam.
TODO
flowam_actions.pyinfo.ymltk_core_reffromazure-pipelines.yml