Problem/Motivation
- Fix the access control on the Launch template before approval so that the access control is as follows.
- Launch approved cloud launch template: Only approved Launch template can be launched.
- Launch cloud launch template: All Launch templates can be launched, including unapproved ones.
Issue fork cloud-3371480
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
phyllanthus commentedComment #4
yas@nakamurarts
Thank you for the fix.
@sekinet
What do you think?
Comment #5
yas@nakamurarts
The PhpUnit test failed at https://www.drupal.org/pift-ci-job/2705863. Can you please fix it? Thanks
Comment #6
sekinet commented@nakamurarts @yas
Thank you for the patch.
We may want to confirm this fix with a BDD test. How about adding the following scenario for this purpose?
Launchtab is displayed even before approveLaunchtab before approveThanks.
Comment #7
phyllanthus commentedComment #8
yas@sekinet
Can you please review the patch? Thanks
Comment #9
sekinet commented@yas @nakamurarts
Thank you for the patch. I think we should add phpunit tests.
Launchtab is displayed even before approveLaunchtab before approveComment #10
phyllanthus commented@yas @sekinet
Thank you all for your reviews.
I added tests based on the suggestion.
Please review, thank you.
Comment #11
yas@nakamurarts (cc: @sekine)
Thank you for the update. I don't think we should remove the permission
launch cloud server template. It means we need to include two testcasesscenarios: one for Drupal'sadministrator, the other one for a genericauthenticated user.Comment #12
yas@nakamurarts
On my second thought, the test case looks good.
Can you please fix the coding standard error? Thanks
→ https://www.drupal.org/pift-ci-job/2718783
Comment #13
yasComment #14
phyllanthus commented@yas
Thank you for your review. I fixed the coding standard errors.
Comment #15
yas@nakamurarts
Thank you for the update. It looks good to me now. I'll merge the patch to
5.xand6.x, and close this issue as Fixed.Comment #18
yas