-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create Waypoint resources with module ID #198
Conversation
8bb0382
to
eaf3830
Compare
BREAKING CHANGE: The no-code module ID is required when creating a template or add-on definition for Waypoint.
474f68b
to
9f230cf
Compare
@@ -135,6 +136,15 @@ $ hcp waypoint add-ons definitions create -n=my-add-on-definition \ | |||
"when the execution mode is set to 'agent'.", | |||
Value: flagvalue.Simple("", &opts.TerraformAgentPoolID), | |||
}, | |||
{ | |||
Name: "tf-no-code-module-id", |
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.
Totally nonblocking and more of just a general observation about the Waypoint CLI commands:
With flags like this that have longer names, typing them out can be fairly frustrating in my experience when you have to enter a bunch of them. To alleviate this, I think a useful pattern for us to adopt would be adding many more "shorthand"
options to these flags.
Not necessarily something you have to do here as it might be useful to do en masse if we go in this direction, but reading your PR reminded me of it.
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 agree that having shorthand flags for these longer-named flags would be nice shortcuts for users who frequent the CLI!
BREAKING CHANGE: The no-code module ID is required when creating a template or add-on definition for Waypoint.
π οΈ Description
π Additional Link
ποΈ Local Testing
π Checklist