-
Notifications
You must be signed in to change notification settings - Fork 20
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
IFC-727 calculate diff tree in proposed change pipeline #4546
Conversation
CodSpeed Performance ReportMerging #4546 will not alter performanceComparing Summary
|
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.
I think the changes looks solid. What I don't really like is that we don't get to see that the changes will work in combination. As the Git submodule still points to a commit that doesn't include the changes you made in the SDK we wouldn't spot any errors at this point of there was anything that is wrong and it will be harder to understand why something starts to fail later.
I'm not sure how we should handle this in general.
One way would be to;
- update the submodule commit in this PR to be that of your SDK branch in order to verify that it is working
- merge the PR in the SDK
- go back to this PR, either change the submodule to the current stable commit or leave it
What are your thoughts around that?
component_registry = get_component_registry() | ||
async with service.database.start_transaction() as dbt: | ||
diff_coordinator = await component_registry.get_component(DiffCoordinator, db=dbt, branch=source_branch) | ||
await diff_coordinator.update_branch_diff(base_branch=destination_branch, diff_branch=source_branch) |
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.
This would only update the branch diff and not in any way give us access to the diff_summary right? I'm thinking that we first do some operations directly against the database and then as the next step we use the SDK to query for the changes (which I guess would be what we updated but also what might have been updated earlier)
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.
the DiffTree
and DiffTreeSummary
graphql queries get their data from the same place. Running update_branch_diff
here will create/update that data so that both queries can be used and will be up-to-date (for the moment, at least. other stuff that runs in the pipeline can make changes that will require another update to the diff
a4e2d92
to
e08d7b5
Compare
I updated the |
e08d7b5
to
91760ab
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. Not sure what the commit for the SDK if that should be replaced with the latest "stable" one if this is another one.
IFC-727
sdk PR opsmill/infrahub-sdk-python#61