Skip to main content
print this page
print this page
print this page

· 2 min read
Fix Available

In amorphic we have different set of permissions to access different components and features. This permissions are given to an amorphic role and user who have access to these role can use those features. This bug is relate to an issue that is users were able to call specific APIs and use those features in Amoprhic even if their role doesn't have the required permission.

Affected Versions: 2.6.1 and below

Fix Version: 2.7

print this page
print this page
print this page
print this page

· 2 min read
Fix Available
Patch Available

While performing the following operations, the directory path for S3 connection type datasets is getting deleted from the metadata:

  • Updating a dataset schema
  • Updating DataConversionParameters for Redshift datasets
  • Updating GlobalSecondaryIndexes for DynamoDB datasets
  • Conducting batch edit operations on datasets

Affected Versions: 2.6 2.6.1

Fix Version: 2.6* 2.6.1* 2.7

print this page
print this page

· 2 min read
Fix Available
Patch Available

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

print this page

· 2 min read
Fix Available
Patch Available

After upgrading to v2.4, workflows created before the upgrade fails when triiggered to run.

Affected Versions: 2.4

Fix Version: 2.5