[CDF-28563] 🪧Remove resource worker

[doctrino]

Description

Resource worker was used in deploy v1, and is no longer necessary. It is replaced by DeployV2Command.categorize_resources

Bump

• Patch
• Skip

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

[doctrino]

/gemini review

[gemini-code-assist]

Code Review

This pull request refactors the deployment process by removing the ResourceWorker class and moving the resource categorization logic to DeployV2Command.categorize_resources. It also updates the create method in FunctionScheduleLoader to manually set the data attribute from the request. Feedback on the changes suggests using loader.get_id(resource) instead of resource.as_id() in the test utilities and integration tests to ensure consistency and prevent potential AttributeErrors.

[github-actions]

☂️ Code Coverage

current status: ✅

Overall Coverage

Statements	Covered	Coverage	Threshold	Status
42780	36614	86%	80%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
cognite_toolkit/_cdf_tk/commands/deploy_v2/command.py	86%	🟢
cognite_toolkit/_cdf_tk/resource_ios/init.py	75%	🟢
cognite_toolkit/_cdf_tk/resource_ios/_resource_ios/function.py	89%	🟢
TOTAL	83%	🟢

updated for commit: 66c6e51 by action🐍

[codecov]

Codecov Report

❌ Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 85.58%. Comparing base (e2809bd) to head (66c6e51).
⚠️ Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
...nite_toolkit/_cdf_tk/commands/deploy_v2/command.py	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3220      +/-   ##
==========================================
- Coverage   85.61%   85.58%   -0.03%     
==========================================
  Files         460      459       -1     
  Lines       42872    42780      -92     
==========================================
- Hits        36704    36614      -90     
+ Misses       6168     6166       -2     

Files with missing lines	Coverage Δ
cognite_toolkit/_cdf_tk/resource_ios/__init__.py	75.40% <ø> (-0.40%)	⬇️
...kit/_cdf_tk/resource_ios/_resource_ios/function.py	88.80% <100.00%> (+0.02%)	⬆️
...nite_toolkit/_cdf_tk/commands/deploy_v2/command.py	85.78% <80.00%> (-0.09%)	⬇️

... and 6 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.