When creating the BucketQuota for a Bucket with a custom name the code was incorrectly prefixing the bucket ID and NOT the bucket name. This lead to the Create Quota attempting to create a quota on a bucket that doesn't exist.
This wasn't picked up by the Unit tests previously because BUCKET_NAME was used for both the ID and the name of the bucket being created therefore the original Unit tests still produced a valid result even if the prefix was incorrectly applied. This has been fixed in this PR.
When creating the BucketQuota for a Bucket with a custom name the code was incorrectly prefixing the bucket ID and NOT the bucket name. This lead to the Create Quota attempting to create a quota on a bucket that doesn't exist.
This wasn't picked up by the Unit tests previously because
BUCKET_NAMEwas used for both the ID and the name of the bucket being created therefore the original Unit tests still produced a valid result even if the prefix was incorrectly applied. This has been fixed in this PR.