Successful attribute option POST returns 'true', not the option hash or value

[dnadle]

Preconditions

1. Magento 2.1.0.

Steps to reproduce

1. POST an new option value using /V1/products/attributes/{attributeCode}/options. Request body looks like {"option": {"label": "FOOBAR"} }
2. Examine response content.

Expected result

1. Returned body should contain full record of option inserted including the option "value."

Actual result

1. Response body contains only 'true'. To learn the value of the newly inserted option you most GET the entire list again.

[mbrinton01]

@dnadle please provide full POST call used. Thanks!

[dnadle]

The full post body is

{ "option":
    {
        "label": "FOOBAR",
        "is_default": false
    }
}

[mbrinton01]

Thank you @dnadle, I have confirmed this behavior. Tracking internally as a bug under https://jira.corp.magento.com/browse/MAGETWO-57585.

[dnadle]

I'd appreciate it if you could look at #6127 and #6120 as well. These bugs make it very difficult to manage products through the API.

[magento-engcom-team]

@dnadle, thank you for your report.
We've created internal ticket(s) MAGETWO-57585 to track progress on the issue.

[k-raputa]

#distributed-cd

[magento-engcom-team]

@kraputa-sintra thank you for joining. Please accept team invitation here and self-assign the issue.

[magento-engcom-team]

@k-raputa thank you for joining. Please accept team invitation here and self-assign the issue.

[magento-engcom-team]

Hi @milindsingh. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team 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!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[milindsingh]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @milindsingh. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @milindsingh, here is your Magento instance.
Admin access: https://i-6300-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[milindsingh]

@dnadle @mbrinton01 I rechecked and found that

• 2.3-develop : the API response was "id_FOOBAR"
• 2.2-develop: the API response was "true"

What do you suggest,

1. We shall use the same object as in return i.e.

{ 
   "option":
       {
           "label": "FOOBAR",
           "is_default": false
       }
}

2. Or just backport the of 2.3-develop as the return, i.e

"id_FOOBAR"

[mbrinton01]

@milindsingh Option 2 (backport 2.3-develop approach)

[m2-assistant]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team 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!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[ghost]

Hi @dnadle thank you for you report, this issue has already fixed in 2.3-develop branch. #19108