Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to remove custom category from backend? #13527

Closed
OperationalFallacy opened this issue Jan 11, 2024 · 5 comments
Closed

How to remove custom category from backend? #13527

OperationalFallacy opened this issue Jan 11, 2024 · 5 comments
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question

Comments

@OperationalFallacy
Copy link

OperationalFallacy commented Jan 11, 2024

Amplify CLI Version

12.10.0

Question

I've added some resources with lambdaTriggerPermissions custom category, but I can't figure out how to delete it.

tree -L 2 amplify/backend/

├── amplify-meta.json
├── api
│   └── tradedal
├── auth
│   ├── xxx
│   └── userPoolGroups
├── awscloudformation
│   └── build
├── backend-config.json
├── custom
│   └── mailinginfra
├── function
│   ├── mailer
│   ├── requestTrade
│   ├── xxxCustomMessage
│   ├── xxxPostConfirmation
│   └── xxxPreSignup
├── lambdaTriggerPermissions
│   └── triggersPermissions
├── tags.json
└── types
    └── amplify-dependent-resources-ref.d.ts

Is it manual operation?
I see it gets marked as "to delete", when I manually delete category from backend-config.json and cli-input.json
Plus amplify env checkout dev?

@OperationalFallacy OperationalFallacy added pending-triage Issue is pending triage question General question labels Jan 11, 2024
@ykethan
Copy link
Member

ykethan commented Jan 11, 2024

Hey @OperationalFallacy, how was the resource added? as custom resources created by amplify add custom are created under the custom folder and can be removed using amplify remove custom.

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Jan 11, 2024
@OperationalFallacy
Copy link
Author

No, these are custom "category" - added manually: define in backed-config.json, create folder, etc.

It looks like these custom categories get deleted with this sequence:

  1. remove it from backend-config.json
  2. amplify env checkout dev
  3. amplify status shows category is getting deleted

Could you explain what the #2 step is for?

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Jan 11, 2024
@ykethan
Copy link
Member

ykethan commented Jan 11, 2024

@OperationalFallacy the step 2 is to regenerate the amplify-meta file from the backend-config file.
Are you running into errors when you run push?

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Jan 11, 2024
@josefaidt
Copy link
Contributor

Closing due to inactivity

@josefaidt josefaidt closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2024
Copy link

github-actions bot commented Feb 2, 2024

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question
Projects
None yet
Development

No branches or pull requests

3 participants