At the moment, when server receives a request for repo that is already destroyed (hence no PreviewApps table in dynamodb) or a user profile that does not exist anymore in config file for AWS(this should not technically happen), the error needs to be caught. In the front end, apps should not really be pulled unless the status is meant to be active
At the moment, when server receives a request for repo that is already destroyed (hence no PreviewApps table in dynamodb) or a user profile that does not exist anymore in config file for AWS(this should not technically happen), the error needs to be caught. In the front end, apps should not really be pulled unless the status is meant to be active