Skip to content

fix: replace non-existent cloud.projects.replace with cloud.projects.update#10

Merged
pedrodeoliveira merged 1 commit intomainfrom
fix/replace-projects-replace-with-update
Mar 12, 2026
Merged

fix: replace non-existent cloud.projects.replace with cloud.projects.update#10
pedrodeoliveira merged 1 commit intomainfrom
fix/replace-projects-replace-with-update

Conversation

@pedrodeoliveira
Copy link
Contributor

@pedrodeoliveira pedrodeoliveira commented Mar 12, 2026

Summary

  • The Gcore SDK does not have a replace method on the projects resource — the correct method is update
  • This was causing the management toolset to expect 18 tools but only 17 were being registered

Test plan

  • Verify the management toolset registers all expected tools without errors

…update

The Gcore SDK does not have a 'replace' method on projects resource.
The correct method is 'update'. This was causing the management toolset
to expect 18 tools but only 17 were being registered.
@pedrodeoliveira pedrodeoliveira self-assigned this Mar 12, 2026
@pedrodeoliveira pedrodeoliveira merged commit 47ac18b into main Mar 12, 2026
3 checks passed
@pedrodeoliveira pedrodeoliveira deleted the fix/replace-projects-replace-with-update branch March 12, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants