You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When creating a service endpiont using apigeecli it fails with disk encryption error and the same request works fine using apigee api curl command
Version
apigeecli version 2.9.0 date: 2025-01-22T22:34:55Z [commit: 4d20467]
To Reproduce
Create a PSC Service Attachment in Producer project first and use the corresponding service attachment details in the following command to create the apigeex endpoint attachment for the PSC consumer
Thanks for creating this bug, I was able to verify and determine the root cause:
In the lines below is using the wrong parameter location
ok := re.Match([]byte(location))
if !ok {
return fmt.Errorf("disk encryption key must be of the format " +
"projects/{project-id}/regions/{location}/serviceAttachments/{sa-name}")
}
It should be serviceAttachment:
ok := re.Match([]byte(serviceAttachment))
if !ok {
return fmt.Errorf("serviceAttachment must be of the format " +
"projects/{project-id}/regions/{location}/serviceAttachments/{sa-name}")
}
Describe the bug
When creating a service endpiont using apigeecli it fails with disk encryption error and the same request works fine using apigee api curl command
The command in question:
Error: disk encryption key must be of the format projects/{project-id}/regions/{location}/serviceAttachments/{sa-name}
The following curl command works fine and successfuly creates the endpoint attachment for PSC consumer:
Version
apigeecli version 2.9.0 date: 2025-01-22T22:34:55Z [commit: 4d20467]
To Reproduce
Create a PSC Service Attachment in Producer project first and use the corresponding service attachment details in the following command to create the apigeex endpoint attachment for the PSC consumer
Expected behavior
Endpoint attachment should be created successfully without any errors within ApigeeX
Additional context
The text was updated successfully, but these errors were encountered: