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
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
First, bravo for this great tool : )
I'am using this to convert all our Postman collection into k6 script, and I had a tons of http 403 response, found out that the generated k6 script does not have a default value for AWS service name, if this field is left empty in the Postman interface.
A suggestion from me would be to set the default service name value to execute-api, and eventually for all other value that are auto generated by Postman if left blank.
Regards
The text was updated successfully, but these errors were encountered:
Due to the inability to properly support this project, the k6 team has decided not to continue its development. The primary reason is that k6 scope has grown significantly with the launch of k6 extensions. The team is prioritizing extending k6 capabilities over the converters.
We suggest you post your issue at api-deck/postman-to-k6. The project is active and maintained on this fork.
Hello
First, bravo for this great tool : )
I'am using this to convert all our Postman collection into k6 script, and I had a tons of http 403 response, found out that the generated k6 script does not have a default value for AWS service name, if this field is left empty in the Postman interface.
postman
AWS4-HMAC-SHA256 Credential=XXX/XXX/eu-central-1/execute-api/aws4_request ...
post-to-k6
AWS4-HMAC-SHA256 Credential=XXX/XXX/eu-central-1//aws4_request
A suggestion from me would be to set the default service name value to
execute-api
, and eventually for all other value that are auto generated by Postman if left blank.Regards
The text was updated successfully, but these errors were encountered: