Skip to content

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

Closed
spikecurtis opened this issue Nov 2, 2023 · 11 comments
Closed
Assignees
Labels
s3 Bugs that confuse, annoy, or are purely cosmetic

Comments

@spikecurtis
Copy link
Contributor

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.

@spikecurtis spikecurtis added s3 Bugs that confuse, annoy, or are purely cosmetic bug labels Nov 2, 2023
@BrunoQuaresma
Copy link
Collaborator

cc.: @mtojek

@mtojek
Copy link
Member

mtojek commented Feb 4, 2024

@spikecurtis Referring to our docs:

  • in Terraform it is called "ephemeral" parameter
  • in UI it is build option.

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 - build_option = true.

Personally, I like the ephemeral as it is more descriptive.

@spikecurtis
Copy link
Contributor Author

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.

@mtojek
Copy link
Member

mtojek commented Feb 6, 2024

@bpmct Are we good with deprecating ephemeral and replacing it with build_option? This will affect code, database schema, and docs, but it shouldn't be breaking.

@bpmct
Copy link
Member

bpmct commented Feb 6, 2024

@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 build_option as well 👍🏼

@spikecurtis
Copy link
Contributor Author

Because of this, my preference is to remove any in-product terminology/db stuff for build_option as well 👍🏼

You mean, rename build_option -> ephemeral parameter and deprecate build_option?

@bpmct
Copy link
Member

bpmct commented Feb 6, 2024

Yep

@bpmct
Copy link
Member

bpmct commented Apr 26, 2024

Did we do this? adding it into next sprint as a good debt item

@bpmct bpmct added the chore label May 31, 2024
@defelmnq defelmnq self-assigned this Oct 7, 2024
@defelmnq
Copy link
Contributor

defelmnq commented Oct 8, 2024

Trying to understand the whole scope of this ticket as I'm working on it , I've seen there's two parameters :

      --build-option string-array, $CODER_BUILD_OPTION
          Build option value in the format "name=value".

      --build-options bool
          Prompt for one-time build options defined with ephemeral 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.

@spikecurtis
Copy link
Contributor Author

I think we want to deprecate both, but keep them around as an alias to "ephemeral parameters"

@matifali matifali removed bug labels Oct 14, 2024
defelmnq added a commit that referenced this issue Oct 16, 2024
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>
@defelmnq
Copy link
Contributor

Closing this one as we merged the associated PR . Should be good with build-option(s) staying as deprecated and ephemeral-parameters replacing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s3 Bugs that confuse, annoy, or are purely cosmetic
Projects
None yet
Development

No branches or pull requests

6 participants