Magento2: [2.3.x][REST] required configurable attributes should not be required value in configurable product

[davidverholen]

Preconditions

1. Magento 2.3.x CE & EE
2. API Integration in place

Steps to reproduce

1. Create a custom required, global product attribute that can be used for configurations (e.g. select)
2. Create one or more simple products with different values for the attribute
3. Create a configurable product over the rest api and leave the required attribute empty
   (I think the API point is only important for reproducing since creating the product in the backend would most likely lead to have the default value / first value in select for the attribute submitted)

Expected result

1. The created attribute should not be required for the configurable product when it is used for configurations

Actual result

1. We get "message": "The \"test\" attribute value is empty. Set the attribute and try again."
   With empty value for attribute:
   
   Without attribute(same response):
   

Current Workaround is to set the attribute to not required

[piotrekkaminski]

Thank you for your submission.

We recently made some changes to the way we process GitHub submissions to more quickly identify and respond to core code issues.

Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here).

We are closing this GitHub ticket and have moved your request to the new forum.

[davidverholen]

@serhii-balko @piotrekkaminski may I ask why this was marked as a feature request?

it is clearly a bug since you have to set a value for a required attribute on a configurable product when this attribute is used for configurations, which does not make any sense. the configurable attributes should be excluded from validation for configurable products (or even better, they should be forced to be empty)

[davidverholen]

hello anyone? @magento-engcom-team maybe? Waiting it out is not a solution :P

[nadeefit6]

Can i pick this issue?

[social-assassin]

@piotrekkaminski Why was this closed? Not a feature request, I'm having the same issue.

[NiklasBr]

@piotrekkaminski this is obviously not a feature request.

[m2-assistant[bot]]

Hi @engcom-Charlie. 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).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-20223 were created

Issue Available: @engcom-Charlie, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._