Problem/Motivation

  • Update AWS resource status with REST API

Proposed resolution

  • Add a REST API to the cloud module to update AWS entity

Issue fork cloud-3226828

Command icon 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

Ryo Yamashita created an issue. See original summary.

Ryo Yamashita’s picture

Status: Needs work » Needs review
yas’s picture

Title: Add a REST API to update AWS entity » Add a REST API to update AWS Cloud entity
yas’s picture

Status: Needs review » Needs work
Ryo Yamashita’s picture

Status: Needs work » Needs review
yas’s picture

Status: Needs review » Needs work

@ryo-yamashita

Thank you for the update. I tried to apply the patch and received the following error. Could you please rebase the patch? Thanks!

error: patch failed: modules/cloud_service_providers/aws_cloud/aws_cloud.routing.yml:798
error: modules/cloud_service_providers/aws_cloud/aws_cloud.routing.yml: patch does not apply
error: patch failed: modules/cloud_service_providers/aws_cloud/src/Controller/Ec2/ApiController.php:622
error: modules/cloud_service_providers/aws_cloud/src/Controller/Ec2/ApiController.php: patch does not apply
error: patch failed: modules/cloud_service_providers/aws_cloud/src/Controller/Ec2/ApiControllerInterface.php:132
error: modules/cloud_service_providers/aws_cloud/src/Controller/Ec2/ApiControllerInterface.php: patch does not apply
error: patch failed: modules/cloud_service_providers/aws_cloud/src/Service/Ec2/Ec2Service.php:1279
error: modules/cloud_service_providers/aws_cloud/src/Service/Ec2/Ec2Service.php: patch does not apply
error: patch failed: modules/cloud_service_providers/aws_cloud/src/Service/Ec2/Ec2ServiceInterface.php:1853
error: modules/cloud_service_providers/aws_cloud/src/Service/Ec2/Ec2ServiceInterface.php: patch does not apply
Ryo Yamashita’s picture

@yas

Thank you for reporting this error message. In this screenshot, the following message is displayed, and rebase is not available by d.o.

Therefore, when I run the rebase command locally, I see that a conflict occurs.

Is it OK to commit after resolving the conflict and then push it?

yas’s picture

Issue summary: View changes

@ryo-yamasthia

Yes you need to rebase locally: "Fast-forward merge is not possible. To merge this request, first rebase locally." It is simply a git repository so we can use the common git commands.

Ryo Yamashita’s picture

Status: Needs work » Needs review

@yas

I rebased and pushed the fix commit. Please check this commit.

  • yas committed c42f96b on 4.x authored by Ryo Yamashita
    Issue #3226828 by Ryo Yamashita, yas: Add a REST API to update AWS Cloud...
yas’s picture

Status: Needs review » Fixed

@ryo-yamashita

Thank you for the update. I merged the patch to 4.x and closing this issue as Fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.