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

provider/aws: Correctly handle missing lambda function #5668

Merged
merged 1 commit into from
Mar 16, 2016
Merged

provider/aws: Correctly handle missing lambda function #5668

merged 1 commit into from
Mar 16, 2016

Conversation

Bowbaq
Copy link
Contributor

@Bowbaq Bowbaq commented Mar 16, 2016

When a function doesn't get created properly / gets externally deleted, that change should be detected. Right now, an error is returned.

@radeksimko

@jen20
Copy link
Contributor

jen20 commented Mar 16, 2016

Hi @Bowbaq! This looks good to me. FYI another way to implement it using an Exists function which gets called prior to Read - this was introduced in #766. This works too though!

jen20 added a commit that referenced this pull request Mar 16, 2016
…ambda

provider/aws: Correctly handle missing lambda function
@jen20 jen20 merged commit 69c6510 into hashicorp:master Mar 16, 2016
@ghost
Copy link

ghost commented Apr 27, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants