Can't use https://www.graphqlbin.com/v2/new

[oefterdal]

Preconditions and environment

• 2.4.5

Steps to reproduce

Go to: https://www.graphqlbin.com/v2/new Enter: https://venia.magento.com/graphql

Expected result

Possibility to query the api

Actual result

Nothing

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @oefterdal. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[oefterdal]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @oefterdal. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @oefterdal, here is your Magento Instance: https://fc028b8b231b22afe95e6a723030f149.instances-prod.magento-community.engineering Admin access: https://fc028b8b231b22afe95e6a723030f149.instances-prod.magento-community.engineering/admin_652c Login: 14a350de Password: 8c00684d0e92

[m2-assistant[bot]]

Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[oefterdal]

https://github.com/magento give me 2.4-develop instance

[oefterdal]

Here is https://venia.magento.com/graphql

[oefterdal]

Magento Instance: https://fc028b8b231b22afe95e6a723030f149.instances-prod.magento-community.engineering/

[engcom-Dash]

Hi @oefterdal ,

Thank you for reporting this ticket,

For better understanding could please share more information about steps to reproduce, Because i am unable to access your venia link,Hence would require to know whether in which environment are you trying install venia(PWA).

Additionally require below details aparts from steps: 1.Magento 2.4.6 Base link on top of if you are installing PWA. 2.Environment details like DEV/QA/PROTECTION

Regards,

[oefterdal]

Paste https://fc028b8b231b22afe95e6a723030f149.instances-prod.magento-community.engineering/graphql into https://www.graphqlbin.com/v2/new

[fooman]

@oefterdal the errors in the screenshot indicate that this is related to CORS errors. I don't see this as something that needs to be addressed - if you wish to run your own instance you can set the headers in such a way that one can use https://www.graphqlbin.com.

[oefterdal]

@fooman thank you, which headers do we need to set and where do we set them on the instance?

[fooman]

@oefterdal that depends on your server setup. It could be done in the Nginx config for example. Another approach is to use https://github.com/graycoreio/magento2-cors. I don't think the test instances under magento-community.engineering will see this added.

[engcom-Dash]

Hi @oefterdal ,

Thanks for your Quick response,

We have some security constraints we are not able test this issue now and We can use altair chrome extension in order to run GraphQL queries.As per my request Kindly update the steps to reproduce,its very easy to proceed further in this case.

Let us know if we missing anything,

Regards,

[oefterdal]

@engcom-Dash How come the the altair chrome extension work?

[m2-assistant[bot]]

Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-November. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-November, here is your Magento Instance: https://fc028b8b231b22afe95e6a723030f149.instances-prod.magento-community.engineering Admin access: https://fc028b8b231b22afe95e6a723030f149.instances-prod.magento-community.engineering/admin_05d8 Login: 2644252c Password: 29df1c424188

[engcom-November]

Hi @oefterdal , Thank you for the response. Verified the behavior on Magento 2.4-develop instance and is reproducible however this is not Magento related issue. https://www.graphqlbin.com/v2/new is not part of https://github.com/magento/magento2/ repository and community is not able to provide fix for it in this repository. All questions, issue reports and fix for them should be addressed to the corresponding extension/owners(support). Alternatively Graphql operations can be performed using POSTMAN or Altair GraphL client chrome extension which can be downloaded from here Once the extension is downloaded on chrome browser, its easy to run any graphql query. Please refer the below screenshot for the same. Please refer below screenshot of POSTMAN UI where graphql operations can be performed:

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @oefterdal,

We have noticed that this issue has not been updated for a period of 14 Days.
Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.