<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=551935) </details> <!--IssueSummary end--> MR: Pending <!--NOTE: For context on MR heading, see: https://handbook.gitlab.com/handbook/engineering/devops/dev/create/remote-development/index.html#relationship-of-issues-to-mrs--> ## Description DesiredConfigFetcher was a temporary class created to fetch desired_config during [the shadow run](https://gitlab.com/gitlab-org/gitlab/-/issues/538163). This class fetches `desired_config` stored in `workspace_agentk_states` table. In case it is not found, the `desired_config` is generated on the fly. Once the BBM to backfill `workspace_agentk_states` is finalized, we can remove this class and the replace [the call to it in `response_payload_builder.rb`](https://gitlab.com/gitlab-org/gitlab/blob/7242aa65030eef7cfbcf69208dcab97e6332326b/ee/lib/remote_development/workspace_operations/reconcile/output/response_payload_builder.rb#L87-87) to simply fetch desired_config from the database. <!--TODO: What kind of issue is this? Please uncomment and include one of the following: /label ~"type::feature" /label ~"type::bug" /label ~"type::maintenance"--> <!--OPTIONAL: Is this a feature/enhancement? - Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole. - Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.--> <!--OPTIONAL: Is this a bug? Please uncomment and include the following: - **Current behavior:** - **Expected behavior:** - **Steps to reproduce:** - **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue!--> ## Acceptance criteria - [ ] Remove all the temporary logic written for shadow run this includes the class _`DesiredConfigFetcher`_ and the logic in `response_payload_builder.rb` - [ ] Ensure workspaces are created as expected ## Implementation plan * Delete class _`DesiredConfigFetcher`_ * Replace the call in `response_payload_builder.rb` with `workspace.workspace_agentk_state` * Update all the specs. \[Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.\] <!--NOTE: Feel free to expand with more sections and headers as needed--> <!--DO NOT TOUCH BELOW-->