amplify-cli icon indicating copy to clipboard operation
amplify-cli copied to clipboard

Add command `amplify custom push`

Open romeubertho opened this issue 3 years ago • 1 comments

Is this feature request related to a new or existing Amplify category?

New category

Is this related to another service?

No response

Describe the feature you'd like to request

Today, it is possible to provision only some category cloud resources by running the following command: amplify <category> push But it's not possible to run amplify custom push yet.

Describe the solution you'd like

It would be great if we have support to run amplify custom push and provision only the custom category cloud resources as we have for other categories.

Also, update the description when running amplify custom:

amplify <subcommands> custom

  add      Takes you through steps in the CLI to add a custom resource to your local backend                                   
  update   Takes you through steps in the CLI to update a custom resource
  push     Provisions only custom cloud resources with the latest local developments                                                       
  remove   Removes a custom resource from your local backend. The resource is removed from the cloud on the next push command. 
  build    Builds custom CDK resources 

Describe alternatives you've considered

I don't think we have any alternative other than amplify custom push

Additional context

No response

Is this something that you'd be interested in working on?

  • [ ] 👋 I may be able to implement this feature request
  • [ ] ⚠️ This feature might incur a breaking change

romeubertho avatar Jan 25 '22 02:01 romeubertho

Hey @romeubertho :wave: thanks for raising this! Marking as a feature request 🙂

josefaidt avatar Jan 25 '22 14:01 josefaidt

One use case I ran into for me is I am trying to remove a custom lambda resolver and instead place it on the schema using (@function(name: "newLambda-${env}")

I have removed it from my custom CDK and added it to my schema.graphql, however upon amplify push I get error Reason: Only one resolver is allowed per field. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; which means I need to first push the custom removal, then once that's done, add it via schema.graphql.

I need ability to push only custom cdk updates so it unblocks further updates...

samturner3 avatar Oct 05 '23 04:10 samturner3