Luke
Luke
Ah no, these changes are only ever made to the amplify-meta file which I believe should always be overwritten automatically before any deploys (with the built contents of the backend-config...
Sorry to necro an old issue but any chance of a resolution/more reliable workaround for this issue? Currently it seems the only way to resolve it requires manual intervention in...
This is key functionality for us which has regressed and gone undocumented in the migration to v6, could we get a status update on when this will be resolved please?...