mirror of
https://github.com/coder/coder.git
synced 2026-09-21 20:51:01 +08:00
dependabot[bot]
2e06b6f75e
Bumps [github.com/zclconf/go-cty](https://github.com/zclconf/go-cty) from 1.16.3 to 1.17.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/zclconf/go-cty/releases">github.com/zclconf/go-cty's releases</a>.</em></p> <blockquote> <h2>v1.17.0</h2> <p><code>cty</code> now requires Go 1.23 or later.</p> <ul> <li> <p><code>cty.Value.Elements</code> offers a modern <code>iter.Seq2</code>-based equivalent of <code>cty.Value.ElementIterator</code>.</p> </li> <li> <p><code>cty.DeepValues</code> offers a modern <code>iter.Seq2</code>-based equivalent of <code>cty.Walk</code>.</p> </li> <li> <p><code>cty.Value.WrangleMarksDeep</code> allows inspecting and modifying individual marks throughout a possibly-nested data structure.</p> <p>Having now got some experience using marks more extensively in some callers, it's become clear that it's often necessary for different subsystems to be able to collaborate using independent marks without upsetting each other's assumptions. Today that tends to be achieved using hand-written transforms either with <code>cty.Transform</code> or <code>cty.Value.UnmarkDeepWithPaths</code>/<code>cty.Value.MarkWithPaths</code>, both of which can be pretty expensive even in the common case where there are no marks present at all.</p> <p>This new function allows inspecting and transforming marks with far less overhead, by creating new values only for parts of a structure that actually need to change and by reusing (rather than recreating) the "payloads" of the values being modified when we know that only the marks have changed.</p> </li> <li> <p><code>cty.ValueMarksOfType</code> and <code>cty.ValueMarksOfTypeDeep</code> make it easier to use type-based rather than value-based mark schemes, where different values of a common type are used to track a specific kind of relationship with multiple external values.</p> </li> <li> <p><code>cty.Value.HasMarkDeep</code> provides a "deep" version of the existing <code>cty.Value.HasMark</code>, searching throughout a possibly-nested structure for any values that have the given mark.</p> </li> <li> <p><code>cty.Value.UnmarkDeep</code> and <code>cty.Value.UnmarkDeepWithPaths</code> are now implemented in terms of <code>cty.Value.WrangleMarksDeep</code>, so they benefit from its reduced overhead. In particular they avoid reconstructing a data structure that contains no marked values at all.</p> </li> <li> <p><code>cty.Value.MarkWithPaths</code> now has a fast path when it's given a zero-length <code>PathValueMarks</code>, in which case it just returns the value it was given with no modifications.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/zclconf/go-cty/blob/main/CHANGELOG.md">github.com/zclconf/go-cty's changelog</a>.</em></p> <blockquote> <h1>1.17.0 (September 5, 2025)</h1> <p><code>cty</code> now requires Go 1.23 or later.</p> <ul> <li> <p><code>cty.Value.Elements</code> offers a modern <code>iter.Seq2</code>-based equivalent of <code>cty.Value.ElementIterator</code>.</p> </li> <li> <p><code>cty.DeepValues</code> offers a modern <code>iter.Seq2</code>-based equivalent of <code>cty.Walk</code>.</p> </li> <li> <p><code>cty.Value.WrangleMarksDeep</code> allows inspecting and modifying individual marks throughout a possibly-nested data structure.</p> <p>Having now got some experience using marks more extensively in some callers, it's become clear that it's often necessary for different subsystems to be able to collaborate using independent marks without upsetting each other's assumptions. Today that tends to be achieved using hand-written transforms either with <code>cty.Transform</code> or <code>cty.Value.UnmarkDeepWithPaths</code>/<code>cty.Value.MarkWithPaths</code>, both of which can be pretty expensive even in the common case where there are no marks present at all.</p> <p>This new function allows inspecting and transforming marks with far less overhead, by creating new values only for parts of a structure that actually need to change and by reusing (rather than recreating) the "payloads" of the values being modified when we know that only the marks have changed.</p> </li> <li> <p><code>cty.ValueMarksOfType</code> and <code>cty.ValueMarksOfTypeDeep</code> make it easier to use type-based rather than value-based mark schemes, where different values of a common type are used to track a specific kind of relationship with multiple external values.</p> </li> <li> <p><code>cty.Value.HasMarkDeep</code> provides a "deep" version of the existing <code>cty.Value.HasMark</code>, searching throughout a possibly-nested structure for any values that have the given mark.</p> </li> <li> <p><code>cty.Value.UnmarkDeep</code> and <code>cty.Value.UnmarkDeepWithPaths</code> are now implemented in terms of <code>cty.Value.WrangleMarksDeep</code>, so they benefit from its reduced overhead. In particular they avoid reconstructing a data structure that contains no marked values at all.</p> </li> <li> <p><code>cty.Value.MarkWithPaths</code> now has a fast path when it's given a zero-length <code>PathValueMarks</code>, in which case it just returns the value it was given with no modifications.</p> </li> </ul> <h1>1.16.4 (August 20, 2025)</h1> <ul> <li><code>cty.UnknownAsNull</code> now accepts marked values and preserves the given marks in its result. Previously it had no direct support for marks and so would either panic or return incorrect results when given marked values.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/zclconf/go-cty/commit/da4c600729aefcf628d6b042ee439e6927d1104e"><code>da4c600</code></a> CHANGELOG: Prepare for v1.17.0 release</li> <li><a href="https://github.com/zclconf/go-cty/commit/b13ddd40b1cd39b19c1acfab789049d7ff34358c"><code>b13ddd4</code></a> cty: Use WrangleMarksDeep for UnmarkDeep and UnmarkDeepWithPaths</li> <li><a href="https://github.com/zclconf/go-cty/commit/4453ac2b7f5200601370c6a3f27207ebc81d2df4"><code>4453ac2</code></a> cty: Use DeepValues instead of Walk for deep marks inspections</li> <li><a href="https://github.com/zclconf/go-cty/commit/f833b10b8efd62c42155b93ab1864c77c836dbc0"><code>f833b10</code></a> Bulk replace interface{} -> any</li> <li><a href="https://github.com/zclconf/go-cty/commit/d4bb9d4fb66471b4ffd521770f5a9f4ff277ee04"><code>d4bb9d4</code></a> cty: Various new mark-inspecting helpers</li> <li><a href="https://github.com/zclconf/go-cty/commit/31572cfc28dc2446e7f163451f78116c6cf776bb"><code>31572cf</code></a> cty+ctymarks: Deep mark wrangling helper</li> <li><a href="https://github.com/zclconf/go-cty/commit/d95a68cf6be26d4d0c841a6de102483c9d382006"><code>d95a68c</code></a> cty: Modern iter.Seq2 equivalents of Value.ElementIterator and Walk</li> <li><a href="https://github.com/zclconf/go-cty/commit/e76eeea526f53bec67a8fda74d68c9593f1a500a"><code>e76eeea</code></a> v1.16.4 release</li> <li><a href="https://github.com/zclconf/go-cty/commit/700a2bccfebdc72ce9270b9715dd2d4e86bd1fa6"><code>700a2bc</code></a> cty: UnknownAsNull accepts marked values and preserves marks</li> <li><a href="https://github.com/zclconf/go-cty/commit/3c2b6a0e21d8e541c2ff5b3825b27483fad0bd1b"><code>3c2b6a0</code></a> Prepare for future v1.16.4 release</li> <li>See full diff in <a href="https://github.com/zclconf/go-cty/compare/v1.16.3...v1.17.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Coder enables organizations to set up development environments in their public or private cloud infrastructure. Cloud development environments are defined with Terraform, connected through a secure high-speed Wireguard® tunnel, and automatically shut down when not used to save on costs. Coder gives engineering teams the flexibility to use the cloud for workloads most beneficial to them.
- Define cloud development environments in Terraform
- EC2 VMs, Kubernetes Pods, Docker Containers, etc.
- Automatically shutdown idle resources to save on costs
- Onboard developers in seconds instead of days
Quickstart
The most convenient way to try Coder is to install it on your local machine and experiment with provisioning cloud development environments using Docker (works on Linux, macOS, and Windows).
# First, install Coder
curl -L https://coder.com/install.sh | sh
# Start the Coder server (caches data in ~/.cache/coder)
coder server
# Navigate to http://localhost:3000 to create your initial user,
# create a Docker template and provision a workspace
Install
The easiest way to install Coder is to use our
install script for Linux
and macOS. For Windows, use the latest ..._installer.exe file from GitHub
Releases.
curl -L https://coder.com/install.sh | sh
You can run the install script with --dry-run to see the commands that will be used to install without executing them. Run the install script with --help for additional flags.
See install for additional methods.
Once installed, you can start a production deployment with a single command:
# Automatically sets up an external access URL on *.try.coder.app
coder server
# Requires a PostgreSQL instance (version 13 or higher) and external access URL
coder server --postgres-url <url> --access-url <url>
Use coder --help to get a list of flags and environment variables. Use our install guides for a complete walkthrough.
Documentation
Browse our docs here or visit a specific section below:
- Templates: Templates are written in Terraform and describe the infrastructure for workspaces
- Workspaces: Workspaces contain the IDEs, dependencies, and configuration information needed for software development
- IDEs: Connect your existing editor to a workspace
- Administration: Learn how to operate Coder
- Premium: Learn about our paid features built for large teams
Support
Feel free to open an issue if you have questions, run into bugs, or have a feature request.
Join our Discord to provide feedback on in-progress features and chat with the community using Coder!
Integrations
We are always working on new integrations. Please feel free to open an issue and ask for an integration. Contributions are welcome in any official or community repositories.
Official
- VS Code Extension: Open any Coder workspace in VS Code with a single click
- JetBrains Toolbox Plugin: Open any Coder workspace from JetBrains Toolbox with a single click
- JetBrains Gateway Plugin: Open any Coder workspace in JetBrains Gateway with a single click
- Dev Container Builder: Build development environments using
devcontainer.jsonon Docker, Kubernetes, and OpenShift - Coder Registry: Build and extend development environments with common use-cases
- Kubernetes Log Stream: Stream Kubernetes Pod events to the Coder startup logs
- Self-Hosted VS Code Extension Marketplace: A private extension marketplace that works in restricted or airgapped networks integrating with code-server.
- Setup Coder: An action to setup coder CLI in GitHub workflows.
Community
- Provision Coder with Terraform: Provision Coder on Google GKE, Azure AKS, AWS EKS, DigitalOcean DOKS, IBMCloud K8s, OVHCloud K8s, and Scaleway K8s Kapsule with Terraform
- Coder Template GitHub Action: A GitHub Action that updates Coder templates
Contributing
We are always happy to see new contributors to Coder. If you are new to the Coder codebase, we have a guide on how to get started. We'd love to see your contributions!
Hiring
Apply here if you're interested in joining our team.