Skip to content

Introduced granulated Media Gallery ACL resources #29715

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 30 commits into from
Sep 11, 2020
Merged

Introduced granulated Media Gallery ACL resources #29715

merged 30 commits into from
Sep 11, 2020

Conversation

Nazar65
Copy link
Member

@Nazar65 Nazar65 commented Aug 21, 2020

Description (*)

Related Pull Requests

https://github.com/magento/partners-magento2-infrastructure/pull/35

Fixed Issues

Fixes magento/adobe-stock-integration#1487: Introduce granulated Media Gallery ACL resources and enforce for old media gallery

Approval Request

https://jira.corp.magento.com/browse/MC-37384

Manual testing scenarios (*)

** Upload assets
** Edit assets
** Delete assets
** Insert assets into the content
** Create folder
** Delete folder
  1. Create new admin user
  2. Try to apply all mentioned acl resources for this user one by time
  3. Verify functionality in old media gallery && new media gallery

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Aug 21, 2020

Hi @Nazar65. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

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

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@Nazar65
Copy link
Member Author

Nazar65 commented Aug 21, 2020

@magento run all tests

@BarnyShergold BarnyShergold self-assigned this Aug 21, 2020
@magento-engcom-team
Copy link
Contributor

Hi @BarnyShergold, thank you for the review.
ENGCOM-8057 has been created to process this Pull Request
✳️ @BarnyShergold, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

Copy link

@BarnyShergold BarnyShergold left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sort order for Create Folder & Delete Folder need to be different values

@sivaschenko sivaschenko added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Aug 24, 2020
@ghost ghost assigned sivaschenko Aug 24, 2020
@Nazar65 Nazar65 changed the title [WIP] Introduce granulated Media Gallery ACL resources and enforce for old media gallery Introduce granulated Media Gallery ACL resources and enforce for old media gallery Aug 28, 2020
@Nazar65
Copy link
Member Author

Nazar65 commented Aug 28, 2020

@magento run all test

@Nazar65
Copy link
Member Author

Nazar65 commented Aug 28, 2020

@magento run all tests

@Nazar65
Copy link
Member Author

Nazar65 commented Aug 28, 2020

@magento run all tests

@sivaschenko
Copy link
Member

@magento run all tests

@magento-engcom-team
Copy link
Contributor

Hi @sidolov, thank you for the review.
ENGCOM-8057 has been created to process this Pull Request

@sivaschenko
Copy link
Member

@magento run all tests

@engcom-Bravo
Copy link
Contributor

✔️ QA Passed

Tested the following manual scenarios:

  • Upload assets
  • Edit assets
  • Delete assets
  • Insert assets into the content
  • Create folder
  • Delete folder

Tested the following admin role resources in New Media Gallery:
Media Media Gallery:

  • Insert assets into the content
  • Upload assets
  • Edit asset details
  • Adobe Stock
  • Save Preview Image
  • License images
  • Delete assets
  • Create folder
  • Delete folder

Tested creating a user role on Magento 2.4.0 + ASI 2.0.0-master, and upgrade instance to Magento 2.4.0 + ASI 2.1.0-master

Test scenarios which cover ACL functionality:
https://studio.cucumber.io/projects/131313/test-plan/folders/943908/scenarios/3218882
https://studio.cucumber.io/projects/131313/test-plan/folders/1051731/scenarios/3967955
https://studio.cucumber.io/projects/131313/test-plan/folders/1051731/scenarios/3968678

@sivaschenko
Copy link
Member

@magento run all tests

@sivaschenko
Copy link
Member

@magento run Functional Tests B2B,Sample Data Tests B2B

@sivaschenko
Copy link
Member

SVC Approved. MFTF failures are caused by downtime of 3rd party service (InStorePickup modules). Ready for delivery

magento-engcom-team pushed a commit that referenced this pull request Sep 11, 2020
@magento-engcom-team magento-engcom-team merged commit e9e7bed into magento:2.4-develop Sep 11, 2020
@m2-assistant
Copy link

m2-assistant bot commented Sep 11, 2020

Hi @Nazar65, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: Cms Component: MediaGalleryCmsUi Component: MediaGalleryUi Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept Project: ASI Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Introduce granulated Media Gallery ACL resources and enforce for new media gallery
7 participants