Skip to content
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

fix: pipeline diff fails on v10 #3154

Merged
merged 3 commits into from
Jan 8, 2025
Merged

fix: pipeline diff fails on v10 #3154

merged 3 commits into from
Jan 8, 2025

Conversation

justinwilaby
Copy link
Contributor

Fixes the problem with pipelines failing on v10

image

use ./bin/run pipelines:diff -a heroku-vscode-staging to test - this pipeline and apps should be accessible to all heroku-dev-tools team members

@justinwilaby justinwilaby requested a review from a team as a code owner December 21, 2024 19:30
Copy link
Contributor

@k80bowman k80bowman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good and seems to work. This is the response I got using heroku-vscode-staging, is that expected?
image

sbosio
sbosio previously requested changes Dec 23, 2024
Copy link
Contributor

@sbosio sbosio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest to split this PR into prioritizing a bugfix PR for the issue, and then a follow up PR with other refactors.

I agree in general that your implementation is correct. I would maintain things like introducing the Github interface types and remove those any types. But changes to the Fir types file are so huge that even Github won't display them. I would suggest for the bug fix to restrict the changes to the relevant interfaces (Pipeline, PipelineCoupling, etc.), if they're needed, avoiding other changes because of the potential risk of effecting other commands that rely on the current state of those interfaces.

If we want to update the fir.d.ts file by uploading another updated file autogenerated by the API schema converter tool, I would provide that as a separate PR with clear documentation on the interfaces that were updated and that are in use by any commands so we can test accordingly. I would love to rely on our current test suite to rule out any issues automatically, but we know there are commands that lack proper testing.

packages/cli/src/commands/pipelines/diff.ts Outdated Show resolved Hide resolved
packages/cli/src/commands/pipelines/diff.ts Outdated Show resolved Hide resolved
packages/cli/src/lib/buildpacks/buildpacks.ts Show resolved Hide resolved
@sbosio sbosio temporarily deployed to AcceptanceTests January 2, 2025 20:36 — with GitHub Actions Inactive
@sbosio sbosio temporarily deployed to AcceptanceTests January 2, 2025 20:36 — with GitHub Actions Inactive
@sbosio sbosio requested review from sbosio and k80bowman January 2, 2025 20:47
@k80bowman k80bowman force-pushed the jw/fix/pipelines-diff branch from 052196d to 49d758a Compare January 8, 2025 15:25
@k80bowman k80bowman dismissed sbosio’s stale review January 8, 2025 16:27

Requested changes have been resolved.

Copy link
Contributor

@eablack eablack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

going to approve because it looks like this fixes this bug. this pr would have benefited from a more explicit description of what was causing the bug and what specific change fixed it. there is a non-trivial amount of refactoring here, so it's a little hard to provide helpful feedback when it's unclear what the core issue is/was. we should probably revisit what our PR template looks like and how we can improve it so that we use it appropriately and put reviewers in the best position possible to provide feedback.

@k80bowman k80bowman merged commit acb4b76 into main Jan 8, 2025
8 checks passed
@k80bowman k80bowman deleted the jw/fix/pipelines-diff branch January 8, 2025 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants