@yas
Please try the merge again. Thanks.
@yas
Please review this patch. Thanks.
hosomitm → created an issue.
@yas
Please review this patch. Thanks.
hosomitm → created an issue.
@yas
Please review this patch. Thanks.
Previously, in response to #3408104, I added source code that took a screenshot of the Subnet deletion form by mistake for the Launch Template deletion form.
As a result, the source code for taking screenshots of the Subnet deletion form is duplicated in two places.
- In Subnet feature: https://git.drupalcode.org/project/cloud/-/blob/4e6265fe2da22316449a5583...
- In Launch template feature. (Duplicate): https://git.drupalcode.org/project/cloud/-/blob/4e6265fe2da22316449a5583...
Delete it and instead add the source code to take a screenshot of the Launch Template's deletion form, which should have been added.
hosomitm → created an issue.
@yas
Please review this patch. Thanks.
Previously, in response to #3406675 📌 Add a BDD test step to take a screenshot to come up with the UI design document (OpenStack Launch template) Fixed , I added source code that took a screenshot of the Network deletion form by mistake for the Launch Template deletion form.
As a result, the source code for taking screenshots of the Network deletion form is duplicated in two places.
- In Network feature: https://git.drupalcode.org/project/cloud/-/blob/24f7dcb920cc04597a41a113...
- In Launch template feature. (Duplicate): https://git.drupalcode.org/project/cloud/-/blob/24f7dcb920cc04597a41a113...
Delete it and instead add the source code to take a screenshot of the Launch Template's deletion form, which should have been added.
hosomitm → created an issue.
@yas
I have corrected the wording you pointed out.
Please review again.
@yas
Please review this patch. Thanks.
hosomitm → created an issue.
@yas
Please review this patch. Thanks.
@yas
Please review this patch. Thanks.
hosomitm → created an issue.
hosomitm → created an issue.
@yas
Please review this patch. Thanks.
hosomitm → created an issue.
@yas
Please review this patch. Thanks.
There is still work to be done:
When I actually tried running Behat, the output was in HTML format instead of PNG format.
I need to modify it so that it is output in PNG format.
@yas
Please review this patch. Thanks.
@yas
I've rebased the source branch from the latest 6.x.
Please review again and merge.
Thanks.
@yas
Please review this patch. Thanks.
@yas
Please review this patch. Thanks.
@yas
Please review this patch. Thanks.
There is still work to be done:
- Change
I take form screenshot
toI take screenshot
.
There is still work to be done:
- Change
I take from screenshot
toI take screenshot
.
There is still work to be done:
- Change
I take from screenshot
toI take screenshot
.
@yas
Please review this patch. Thanks.
hosomitm → created an issue.
@yas
Please review this patch. Thanks.
hosomitm → created an issue.
hosomitm → created an issue.
@yas
Please review the code. Thanks.
hosomitm → created an issue.
@yas
I have corrected the indicated source code.
Please review again.
@yas
Please review the code. Thanks.
Note:
If you merge this Merge request, the argument will not be passed correctly to "updatedNodes" of k8s_node_heatmap.js. When refactoring k8s_node_heatmap.js, keep in mind that you need to make sure that the arguments are passed correctly from k8s_refresh_resource_trigger.js to updatedNodes in k8s_node_heatmap.js.
hosomitm → created an issue.
@yas
I created a patch/merge request for 5.x.
Please review the code for 5.x. Thanks.
@yas
Please review the code. Thanks.
hosomitm → created an issue.
@yas
I created a patch/merge request for 5.x.
Please review the code for 5.x. Thanks.
@yas
Please review the code. Thanks.
hosomitm → created an issue.
@yas
Please review the code. Thanks.
hosomitm → created an issue.
@yas
Please review the code. Thanks.
@yas
Please review the code. Thanks.
hosomitm → created an issue.
@yas
I'm sorry. I overlooked a violation of coding standards.
I have fixed it, so please check it.
Thank you.
@yas
Please review the code.
I used the tom-select library to customize the Flavor drop-down list in the Create and Edit forms of Launch Template, but as a result, tom-select automatically rewrote the for attribute in the <label>
tag. , and the Behat scenario can no longer find the <select>
for Flavor.
As a workaround, Behat is trying to avoid this problem by directly specifying the id attribute of the
tag instead of the Label value.
The way the scenario is written is different from other form elements, but is this acceptable?
Thanks.
The following BDD test scenario fails to select Flavor. I think the problem is due to the modification of this issue.
BDD file: OpenStack-ATDD-03-05-OperateInstances.feature
Scenario: Create a launch template by a user and a cloud admin
I will make additional modifications so that the BDD scenario can pass.
@yas
Please review the code. Thanks.
hosomitm → created an issue.
@yas
Please review the code. Thanks.
hosomitm → created an issue.
@yas
Please review the code. Thanks.
@yas
Please review the code. Thanks.
hosomitm → created an issue.
hosomitm → created an issue.
@yas
Please review the patch. Thanks.
hosomitm → created an issue.
@yas
Please review the code. Thanks.
hosomitm → made their first commit to this issue’s fork.
@yas @ryo-yamashita
Please review the code. Thank you.
hosomitm → created an issue.
@yas @ryo-yamashita
Please review the code.
As a known remaining issue, the Well-known protocols list is hard-coded, so it is necessary to make the list added in #3374538 available as a JSON API.
Thank you.
hosomitm → created an issue.
@yas
I sorted the modules to install in ascending alphabetical order.
For some reason there were two node modules, so I deleted one.
Please review again. Thank you.
@yas
I had a feeling that they were probably trying to sort alphabetically by Core modules, then by contributed modules, and then by Cloud Orchestrator instead of a simple alphabetical order.
However, that rule seems to be breaking down a bit.
I'm going to follow your advice and sort by simple alphabetical order.
@yas
Please review the patch. Thank you.
hosomitm → created an issue.
@yas
Please review the code. Thank you.
hosomitm → created an issue.
@yas
I have fixed the issues pointed out in the review.
Please review again. Thanks you.
@yas
Please review the code. Thank you.
hosomitm → created an issue.
@yas
Please review the patch. Thank you.
hosomitm → created an issue.
@yas
Please review the code. Thank you.
hosomitm → created an issue.
@yas
Thank you for your comment.
I have refactored it.
Please review it again. Thank you.
@yas
Please review the code. Thank you.
hosomitm → created an issue.
@yas @ryo-yamashita
Please review the code.
The "Administration" link is displayed when logged in as a user with the View cloud service provider administration list
permission.
The "Users" link is displayed when logged in as a user with the Administer users
permission and the
RoleAssign →
module is installed.
I have added an API to the cloud module's ApiController for determining whether each menu should be displayed. Is there any issue with adding it in that location?
Thank you.
hosomitm → created an issue.
@yas @baldwinlouie
I fixed bug with links not working.
Please review the patch. Thank you.
@yas @baldwinlouie
I'm sorry.
There was a problem that clicking the link did not transition to the link destination.
I will fix it.
@yas @baldwinlouie
Please review the patch. Thank you.
@yas @baldwinlouie
Please review the patch. Thank you.
hosomitm → created an issue.
hosomitm → created an issue.