-
Notifications
You must be signed in to change notification settings - Fork 887
stick to consistent terminology re: build options / ephemeral parameters #10488
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
Comments
cc.: @mtojek |
@spikecurtis Referring to our docs:
AFAIR, ephemeral was considered to be a bit mysterious, hence we decided to replace it with simpler term, a "build option". Without breaking API/Terraform changes, we can remove all references to ephemeral except for the Terraform template, unless we deprecate it, and define a new one - Personally, I like the |
I just want it to be consistent in both places. We'll have to deprecate the old term in one place or other but keep it as an alias for back compat. |
@bpmct Are we good with deprecating |
@kylecarbs expressed that the terminology build_option compared to build_parameter is pretty confusing. I agree. Naming is hard 😅 Because of this, my preference is to remove any in-product terminology/db stuff for |
You mean, rename build_option -> ephemeral parameter and deprecate build_option? |
Yep |
Did we do this? adding it into next sprint as a good debt item |
Trying to understand the whole scope of this ticket as I'm working on it , I've seen there's two parameters :
Do we want to deprecate both or one specifically ? The first one seems to be a list of key=value while the second one is enabling the prompt for each parameter considered as ephemeral in the template. |
I think we want to deprecate both, but keep them around as an alias to "ephemeral parameters" |
This PR aims to rename `build-option` to `ephemeral-parameters` based on #10488 conversation. `build-option` has been renamed `ephemeral-parameter` and can be used to define a value for an ephemeral parameter in the template. `build-options` has been renamed `prompt-ephemeral-parameters` and can be used to prompt the user to put values for the ephemeral parameters in the template. --------- Co-authored-by: Mathias Fredriksson <mafredri@gmail.com> Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com> Co-authored-by: defelmnq <yvincent@coder.com>
Closing this one as we merged the associated PR . Should be good with build-option(s) staying as deprecated and ephemeral-parameters replacing it. |
When authoring templates the concept is called an "ephemeral parameter" but when starting workspaces it's a "build option." The CLI help gives no further explanation of what a build option is.
We need to use consistent terminology. Template authors are often end users. Template authors and end users need to be able to communicate with one another about templates and workspaces, so they need a common set of terms.
The text was updated successfully, but these errors were encountered: