Skip to main content
print this page

Failed to retrieve resourceId based on resource name using fetch resourceId API.

· 2 min read
Fix Available
Fix Available
This bug has been fixed
Patch Available
Patch Available
This bug has a patch available for affected versions

While retrieving the resourceId providing the resource name using the Amorphic's fetch resourceId API i.e. /resourcetypes/{resource_type}/resources/{resource_name}, It is failing with 'Invalid resource name' error for datasets and views with capital letters in the resource name.

For other resource types, API is failing with the key error: ResourceNameIndexGroupsResourceTable

For retrieving roles, It's failing with error: IPV-1004 - Invalid resource type - 'roles' is not supported

Affected Versions: 2.5 2.5.1 2.6

Fix Version: 2.6.1

Root cause(s)​

While making few enhancements and refactors in the 2.5 (CLOUD-4376) related to groups functionality which resulted in these errors.

Impact​

After upgrading to 2.5, When users try to retrieve any resourceId using the API /resourcetypes/{resource_type}/resources/{resource_name}, the API will fail with error 'Invalid resource name'.

Mitigation​

Fix available

Fix is available in Amorphic version 2.6.1. Please upgrade to the latest version to resolve this issue.

Patch available

Patch is available for Amorphic versions v2.5.1, 2.6

Please contact amorphic-support@cloudwick.com to patch your application.

Timeline​

gantt
    title Timeline
    dateFormat YYYY-MM-DD
    tickInterval 7day
    axisFormat %b-%d
    todayMarker off
    section Tracker
        %% update the ticket number and date of bug report
        CLOUD-4766 : done, 2024-07-15, 0d
    section Identification
        Reported : crit, des1, 2024-07-15, 0d
    section Mitigation
        %% Update number of days took for each step below
        Bug Fixed: crit, done, 2024-07-15, 1d
    section Delivery
        %% update the date of each step below
        testing complete: milestone, 2024-07-19, 0d
        patch avaialble: milestone, 2024-07-19, 0d
  • 2024-07-15: Bug reported/identified (CLOUD-4766)
  • 2024-07-15: Bug triaged
  • 2024-07-15: Bug fixed
  • 2024-07-19: Testing of patch on v2.5.1 is completed
  • 2024-07-19: Patch for v2.5.1 released