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

up stack delete attempts to delete roles it didn't create #787

Closed
3 of 4 tasks
davidmc24 opened this issue Oct 23, 2019 · 0 comments
Closed
3 of 4 tasks

up stack delete attempts to delete roles it didn't create #787

davidmc24 opened this issue Oct 23, 2019 · 0 comments
Labels

Comments

@davidmc24
Copy link
Contributor

Prerequisites

  • I am running the latest version. (up upgrade)
  • I searched to see if the issue already exists.
  • I inspected the verbose debug output with the -v, --verbose flag.
  • Are you an Up Pro subscriber?

Description

At the company I work at, we do not have the IAM permission to create/delete IAM roles/policies. I was expecting that if up.yml was configured with a value for lamba.role, it would use that role without attempting to modify it. This appears to work as expected for stack creation and deployment, but when doing a stack deletion, it appears to attempt to delete the default function role even though it wasn't using it.

While it's possible that my situation (not having permission to delete roles) is uncommon, this also has the possibility of deleting unrelated roles that happen to have the expected name and may be in use for other purposes.

Steps to Reproduce

  • Create a service with a provided lambda role and an AWS profile that isn't allowed to delete roles.
  • Deploy the service.
  • Run up stack delete and see the error

Love Up?

Please consider signing up for Up Pro (https://up.docs.apex.sh/#guides.subscribing_to_up_pro) or donating via https://opencollective.com/apex-up/donate.

Slack

Join us on Slack https://chat.apex.sh/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants