Rui Pedrosa

icon indicating a website link https://www.linkedin.com/in/ruipedrosa icon indicating an email [email protected]

icon company manifestsoftware.io icon location Porto icon location I strive for technical excellence and few things make me happier than having robust code in production being used 🤓

Results 5 comments of Rui Pedrosa

Step Functions

I also would like to have this as well (which is something [supported on the serverless framework](https://serverless.com/aws-step-functions/) as a comparison). By now, we are using [custom CF stacks](https://aws-amplify.github.io/docs/cli-toolchain/quickstart#custom-cloudformation-stacks) to setup...

Step Functions

@cschow-ucsd I make step-functions working by creating a "[Custom CloudFormation stacks](https://docs.amplify.aws/cli/usage/customcf)". Similar to this [this](https://medium.com/swlh/add-monitoring-to-your-amplify-app-by-using-amplify-framework-d4c43b2bb84b) but for using Step Functions as orchestration instead of SNS topics for monitoring

Separation of Prod and Non-Prod accounts for Amplify Console when using CodeCommit

I also need this. It is frustrating that we can connect to Github from multiple AWS accounts on Amplify but not to Code Commit (own by AWS itself!)

Separation of Prod and Non-Prod accounts for Amplify Console when using CodeCommit

another problem of the console is that `amplifyPush --simple ` does not pick settings from team-provider-info.json

Separation of Prod and Non-Prod accounts for Amplify Console when using CodeCommit

@swaminator I think I was using `amplifyPush --simple` in Amplify Console and `amplifyPush --simple`didn't look on `team-provider-info.json` file to find out, for example, what is the `AmplifyAppId` to use for...