Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Resources not imported correctly #11

Closed
sadooghi opened this issue Apr 28, 2019 · 4 comments
Closed

Resources not imported correctly #11

sadooghi opened this issue Apr 28, 2019 · 4 comments
Labels
bug Something isn't working

Comments

@sadooghi
Copy link

Hi

My Project-id is: c8900804-9dd8-47ff-84bf-9351bb6aa535

In my AWS-Mobile CLI I had 4 tables and 4 api gateways configure(Profiles, Foods, FoodInfo, PlannedFood) but when I look at the resources that have been imported I only see one table for Storage (Profiles) and only one api gateway imported (Foods) in my amplify-meta.json File.

Also, my backend functions are still in awsmobilejs/backend/cloud-api folder. If I make any changes to them they won't be updated. Shouldn't have those functions been copied to amplify/backend folder?

@nimacks nimacks added the bug Something isn't working label May 30, 2019
@nimacks
Copy link
Contributor

nimacks commented May 30, 2019

Hey @sadooghi, my apologies for not responding to this issue earlier. We'll have someone take a look at this for you. Thanks.

@swaminator
Copy link
Contributor

#12

@nimacks
Copy link
Contributor

nimacks commented Aug 13, 2019

@sadooghi, please make sure you're looking at this file #current-cloud-backend/amplify-meta.json. The resources migrated will be stored in this directory and not the backend folder since they already exist.

To answer your question about functions in the backend folder, the answer is no. Only resources that are managed by the Amplify CLI are in the backend folder. The Amplify CLI uses CloudFormation to provision and update resources on your behalf. MobileHub does not use CloudFormation so your imported MobileHub resources cannot be updated in the Amplify CLI.

Please let us know if your migrated resources are not in the file #current-cloud-backend/amplify-meta.json.

@swaminator
Copy link
Contributor

Closing this issue. @sadooghi if you are still stuck, please re-open the issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants