-
Notifications
You must be signed in to change notification settings - Fork 153
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
Pass the DeploySource directly to the plugin #5050
Conversation
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Signed-off-by: Shinnosuke Sawada-Dazai <shin@warashi.dev>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5050 +/- ##
==========================================
+ Coverage 22.45% 22.48% +0.02%
==========================================
Files 522 522
Lines 57026 57007 -19
==========================================
+ Hits 12807 12818 +11
+ Misses 43192 43161 -31
- Partials 1027 1028 +1 ☔ View full report in Codecov by Sentry. |
// The source of the deployment. | ||
DeploySource deploy_source = 3; | ||
// The source of the last successful deployment. | ||
DeploySource last_successful_deploy_source = 4; |
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 source of the deployment. | |
DeploySource deploy_source = 3; | |
// The source of the last successful deployment. | |
DeploySource last_successful_deploy_source = 4; | |
// The source of the target state. | |
DeploySource target_deploy_source = 3; | |
// The source of the running state. | |
DeploySource running_deploy_source = 4; |
How about renaming like this 👀
I have not been able to work on this PR for a while. |
What this PR does / why we need it:
This PR modifies the plugin input.
The piped passes the deploy source information directly to the plugin, and the plugin expects the piped to prepare the deploy source before invoking the RPC methods.
The application spec is defined in bytes because we don't want to define the spec's structure for each plugin.
This PR does not touch the deploysource package because it's widely used, and the type
DeploySource
is not only used in the pipedv1 but also in other packages.Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: