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

[Auth] Cannot remove lambda trigger #5986

Closed
iyz91 opened this issue Nov 26, 2020 · 2 comments
Closed

[Auth] Cannot remove lambda trigger #5986

iyz91 opened this issue Nov 26, 2020 · 2 comments
Labels
auth Issues tied to the auth category of the CLI bug Something isn't working

Comments

@iyz91
Copy link

iyz91 commented Nov 26, 2020

Describe the bug
After adding a lambda trigger, I cannot remove it. It was the only trigger, and I am able to deselect that trigger and enable another, but I cannot deselect/remove when there's only a single remaining trigger. There are no errors and the CLI returns "Successfully updated resource locally". Trigger is not removed, auth update shows it still selected, amplify status is not altered.

Amplify CLI Version
4.36.0

To Reproduce

  1. Add "Post Confirmation" trigger.
  2. Push and use.
  3. Call amplify auth update, step through, and deselect above trigger.
  4. Trigger is not removed, auth update shows it still selected, amplify status is not altered.
    (Can, however, deselect and enable another, it will delete the previous and enable the new one, but still cannot delete last remaining trigger).

Expected behavior
Deselecting a trigger should remove it.

Screenshots
N/A

Desktop (please complete the following information):

  • OS: Windows 10
  • Node Version: 14.12.0

Additional context
N/A

@ammarkarachi ammarkarachi added auth Issues tied to the auth category of the CLI pending-triage Issue is pending triage bug Something isn't working and removed pending-triage Issue is pending triage labels Nov 27, 2020
@akshbhu
Copy link
Contributor

akshbhu commented Jan 27, 2021

Closing this issue as it is solved with this PR #6403. It will be available in the next version.

@akshbhu akshbhu closed this as completed Jan 27, 2021
@github-actions
Copy link

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auth Issues tied to the auth category of the CLI bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants