Issue Cleanup Round #1

[f0ssel]

We have an overwhelming amount of issues that go stale and are better off being remade when they come back up in priority. In our retro today this was brought up again. I'm trying to go through old issues that have the following problems:

• No longer applicable / information is out of date
• Not clearly actionable
• Done / Decided we won't do
• Not detailed enough
• Probably won't prioritize in the next 3 months

Remembering that all issues can easily be reopened at a later date, I would like to close the following:

• Allow external provisioner daemons to register with Coder #44
• Security: Implement encryption of provisioner state #358
• Sign Windows CLI #359
• Investigate which backend audit log ingestion services are highest values for our customers  #470
• Organization Support #479
• RBAC Support  #519
• Add a "What's New Dialog" for users to see what has been added/changed/fixed in the version they are using #581
• Admin Settings Support  #589
• Add initial setup walkthrough in dash #603
• Active user status indicator support in user list #611
• UI performance benchmark testing for active users #613
• Investigate the benchmarking needs for the product to ensure we can properly scale #614
• E2E testing for organization support  #619
• CLI Experience #620
• Organizations - Enterprise #665
• RBAC - Enterprise MVP #672
• Multiple organization support in site #686
• AuthN / OIDC  #695
• Implement scoping for RBAC - APIs merged with User Roles #722
• Roles as a Resource support for RBAC #726
• Windows Installer #736
• Implement a standard way to handle errors on the ui/cli #764
• CLI Experience - Enterprise MVP #778
• Build an OAuth sign in provider wrapper so we can share same code in the future #790
• Admin Settings - Git OAuth management #791
• Add OIDC provider support for backend #792
• Admin Settings - License management #793
• Admin Settings - Enterprise MVP #798
• Example Epic  #842
• Example Issue #843
• Improve dev experience by adding "local" template #905
• Add retry to frontend API calls #912
• Review Linter #945
• Frontend Users Read - Pagination #979
• Update Material UI #990
• Refactor Snackbar into XService #997
• Fmt/sql is slightly slow #1067
• Use dscl to get the users shell on a MacOS agent #1068
• Implement missing trusted-types CSP #1078
• Allow specifying initial state of workspaces #1097
• Create api types and responses for audit logs #1099
• Add Storybook for site/src/components/TableHeaders #1224
• Support window resizing for terminal sharing via URLs #1276
• Support web terminal sharing between users via URL #1277
• Terminal Sharing Support #1286
• Define: clear path to debugging a broken workspace #1321
• Automated tests on examples lifecycle (template init, template create, workspace create, ssh) #1383
• Endpoint to generate a provisionerd token #1391
• CLI command to register a provisionerd and return a token #1392
• Provisionerd reads authentication token on startup #1393
• Extract helper function for creating a new workspace build #1401
• Implement template versions in the CLI #1425
• Add /workspaces to allow for filtered and paginated querying #1477
• Global Consistency Items - Enterprise MVP #1479
• Epic: In-product Changelog #1525
• Simply running make bin is not sufficient when testing changes #1547
• Print API requests made by CLI #1565
• Provisionerd should register the running provisioners when it connects #1605
• Add lifecyle info to Resources card #1628
• coder reset-password should be nested under coder users #1631
• Scan for open ports from the coder agent #1762
• Make deleting from a slice a generic function #1780

[kylecarbs]

I agree with closing all!

[f0ssel]

@tjcran @bpmct I would like you both to sign off before the purge

[bpmct]

All good to close all except #802 #1554 as I think we'll be doing both relatively soon!

[presleyp]

Please keep #1082 #1532 and #961

[dwahler]

I think #909, which is currently on the proposed August roadmap, depends on #44. Depending on the implementation, it might also depend on #1391, #1392, #1393, and/or #1605.

Many of these sound like issues that we've said we do plan to implement at some point, even though the issue descriptions might be out of date. Do we plan to reopen them when we eventually get around to them?

[tjcran]

I think #909, which is currently on the proposed August roadmap, depends on #44. Depending on the implementation, it might also depend on #1391, #1392, #1393, and/or #1605.

Many of these sound like issues that we've said we do plan to implement at some point, even though the issue descriptions might be out of date. Do we plan to reopen them when we eventually get around to them?

@dwahler yes! closing does not mean its forever closed. any of them can always be reopened.

[f0ssel]

@dwahler after reading through those tickets it seemed to me the plan and details were out of date. Closing these tickets in no way implies that work won't be planned or worked on, but that these tickets being open and existing are not helping us right now.

[f0ssel]

@spikecurtis @dwahler I reopened the ones I think are relevant to your work, sorry for misunderstanding and jumping the gun on that.

[dwahler]

@f0ssel No problem at all, and thanks for doing this cleanup!