Emre

+1 For example, there is no explanation as to how we can implement a modified AuthRule directive: https://docs.amplify.aws/cli/graphql/authorization-rules/#how-it-works 

Using `amplifyPush --simple` in `amplify.yml` still overwrites `hooks` folder with the S3 bucket `hooks` folder (which doesn't have correct content).

@lazpavel Yes it's set to latest, and I've verified with build logs.

@hloriana I don't feel comfortable providing the App ID in a public forum. What does your `amplify.yml` look like while testing? I'm guessing the issue is, if deploying to different...

Hi @hloriana, thanks for the follow-up. - We only have one app. - Setting `AMPLIFY_SKIP_BACKEND_BUILD` to `true` does not work either, it still runs the build. 

Just as an additional point, I have this enabled, which probably affects it.  > Enable full-stack continuous deployments (CI/CD) > Full-stack CI/CD allows you to continously deploy frontend and...

@oste Yes you should be able to use `amplifyPush --simple` in backend build according to docs. But there seems to be a (edge case) bug where it always does backend...

Why is the custom salt feature even there?