RESTful API: No way to discover attribute set / group / attribute information

[gibbotronic]

Using the RESTful interface, there is no way to interrogate an attribute set to see which attributes are assigned to it by group.

This means I have no way of knowing whether an attribute should be assigned to an attribute set, so I must blindly and dumbly assign all my attributes to their respective attribute sets and groups every time I want to interact with them, as I have absolutely no way of knowing what already exists. eg. with a POST to rest/V1/products/attribute-sets/attributes with

{"attributeCode":"myNewAttribute", "attributeGroupId":1550, "attributeSetId":148, "sortOrder":0}

1. You can discover all attributes via rest/V1/products/attributes?searchCriteria but this doesn't give any group information or attribute set relationship information.
2. You can query an individual attribute via rest/V1/products/attributes/{attributeCode} (eg. rest/V1/products/attributes/color) but this does not give any group information or attribute set relationship information.
3. You can search for all attribute sets via rest/V1/products/attribute-sets/sets/list?searchCriteria&fields=items but this does not give any group information.
4. You can query an individual attribute set via its id (eg. 4 for Default, out of the box) via rest/V1/products/attribute-sets/4 but this does not give any group information or details on the attributes that belongs to this attribute set.
5. You can query an individual attribute set via its id to discover the attributes within that set (eg. 4 for Default) via rest/V1/products/attribute-sets/4/attributes but this does not give any group information.
6. You can query for all groups via rest/V1/products/attribute-sets/groups/list?searchCriteria but this does not tell you which attributes actually belong to the returned list of groups and attribute sets.
7. There does not appear to be a way to fetch individual group information.

Preconditions (*)

1. Magento 2.3.2

Steps to reproduce (*)

1. There is no way of getting this information!

Expected result (*)

1. I would like to be able to know the tuple of attribute set / group / attribute relationships.
2. I would expect this somewhere under the attribute set API or under the attribute API

Actual result (*)

1. This is impossible.

[m2-assistant[bot]]

Hi @gibbotronic. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@gibbotronic do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

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

[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.

[engcom-Charlie]

This issue looks like a feature request. @sdzhepa can you transfer this issue to the feature requests repository?

[m2-assistant[bot]]

Hi @sdzhepa. 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.

[gibbotronic]

Thanks for adding this as a feature request - much appreciated. At the moment there is no way to get this data out of Magento via the API.

[priti2jcommerce]

@magento give me 2.3-develop instance - upcoming 2.3.x release

[magento-engcom-team]

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

[magento-engcom-team]

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

[sdzhepa]

Based on the description and label feature request the issue has been transferred to Magento Feature Request public repo.