-
Notifications
You must be signed in to change notification settings - Fork 4
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
allow sending key/value pairs with dispatch #78
Conversation
Make pulumictl dispatch more generally useful, and allow key/value pairs in addition to a single ref. For starters we'll use this to dispatch a GitHub actions job that will update the `latest-dev-version` file (see pulumi/docs#10365), but this can be used for other workflows as well.
1c9feb7
to
61b2ac1
Compare
cmd/pulumictl/dispatch/cli.go
Outdated
@@ -53,7 +64,6 @@ func Command() *cobra.Command { | |||
} | |||
|
|||
_, err := semver.Parse(gitversion.StripModuleTagPrefixes(ref)) |
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 semver check needs moving into the payloadMap["ref"]
side of the if above.
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.
Linting didn't pick this up because there's global var defined at line 22. That can go but I'm pretty sure the others can probably go as well.
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.
Ah yes, good catch, thanks!
Yeah indeed, all the global variables can go. In fact that made me realize that we never actually used the org
variable, and that command line parameter doesn't do anything. I removed it now.
Make pulumictl dispatch more generally useful, and allow key/value pairs in addition to a single ref. For starters we'll use this to dispatch a GitHub actions job that will update the
latest-dev-version
file (see pulumi/docs#10365), but this can be used for other workflows as well./xref pulumi/pulumi#14623