That would be super helpful. Issues #7087 , #7272 and #7280 are similar.

This is a duplicate of #7272. You may close one of these.

I really like option 2. It's a clean abstraction that can be per-template for users that create a lot of workspaces.

For option 2. Could we also use browser cache/storage? cc: @BrunoQuaresma
It could also work like password autofill works by suggesting last typed values.

My understanding of option 2 is we would suggest the list of previously used values for the same parameter name (regardless of whether it's "dotfiles_url")?

@matifali — I think we should lean on the DB here to provide a consistent experience since we already have the parameter data there.

@ammario if we do want to use database then I think option 1 is better. We can just allow a user to specify their dotfiles in their account settings page.
It could be made available via data.coder_workspace.me.dotfiles_url

We can also run coder dotfiles as part of agent init_script if a user has it specified under account settings. This approach will liberate template admins of configuring it in the template.

Option 1 is a non-starter to me, as it adds a new, opinionated "dotfiles" primitive to the product. I also don't see how using the database would make Option 1 better. We can go with Option 2 using what we already store in the DB.

Option 3 would be awesome! I know that is the one that requires more development, but it is the more and predictable solution. Even we could do something like:

 data "coder_parameter" "dotfiles_uri" {
   name        = "What dotfiles repo would you like to use for your workspace?"
   description = "Dotfiles repo URI (optional). See https://dotfiles.github.io"
   icon        = "/emojis/1f9f0.png"
   default = "https://github.com/example/dotfiles.git"
+  default_env = "DOTFILES_URI" # This will load the environment variable configured in the user profile
   mutable = false
 }

The cool thing about this approach is that we can extend it to whatever coder_parameter we have, not only the dotfiles one.

I agree that option 3 for generic user-specified coder_parameter defaults would be really valuable. The dotfiles use case presented here makes a lot of sense, and I could also see this being very useful for things like region defaults (East Coast users can select the "US East" region as their default, etc.).