Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression Issue: Renaming of API Function from download_a_file_by_fileid to download_a_file_by_file_id Breaks Module Functionality #188

Open
3 tasks done
syed-khadeerahmed opened this issue Jan 21, 2025 · 1 comment

Comments

@syed-khadeerahmed
Copy link

syed-khadeerahmed commented Jan 21, 2025

Prerequisites

  • Have you tested the operation in the API directly?
  • Do you have the latest SDK version?
  • Review the compatibility matrix before opening an issue.

Describe the bug
This issue involves a regression caused by a change in the API function name that was not handled in the latest SDK's alias function. The issue directly impacts the functionality of the inventory_workflow_manager module. this behavior is observed in the latest version of dnacentersdk version - 2.10.3 and 2.8.2 (public version)

The API function download_a_file_by_fileid was renamed to download_a_file_by_file_id starting from SDK version v2_3_7_6. However, this change introduced a regression because the updated function name was not reflected in the alias function of the latest SDK, leading to broken functionality.

Expected behavior
To ensure backward compatibility, the SDK should support both download_a_file_by_fileid and download_a_file_by_file_id function names. This approach would prevent existing modules from breaking when the SDK is updated.

Screenshots

Image

Latest function:

Image

Environment (please complete the following information):

  • Cisco DNA Center Version and patch:
  • Python version: 3.9.19
  • SDK version: 2.10.3, 2.8.2(public version)

Additional context
Add any other context about the problem here.

fmunozmiranda added a commit that referenced this issue Jan 23, 2025
@JosePabloOcampo1212
Copy link
Collaborator

Hi! Could you try updating to the latest version?

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

No branches or pull requests

2 participants