Using the following Terraform I ran into an issue where devcontainers were named the same. The current strategy for naming devcontainers is overly complex and this change simplifies it by removing one source for them.

While at it, sort order of devcontainers is also made stable by sorting on devcontainer folder rather than name. The previous sorting resulted in devcontainers jumping around in the UI if their name changed.

resource"coder_devcontainer""repositories" {for_each=local.repositoriesagent_id=coder_agent.dev.idworkspace_folder="/home/coder/${module.git-clone[each.key].folder_name}"}

And this looks wrong in the UI:

And once the devcontainers come up, only one sub-agent can be created. The other will fail due to "name in use" because the implementation in the provisioner assumed this case is not possible.