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

Terraform fails because of difference between plan and apply #1835

Closed
mspaulding06 opened this issue Oct 6, 2017 · 2 comments
Closed

Terraform fails because of difference between plan and apply #1835

mspaulding06 opened this issue Oct 6, 2017 · 2 comments
Labels
bug Addresses a defect in current functionality. service/lambda Issues and PRs that pertain to the lambda service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@mspaulding06
Copy link
Contributor

Crash Output

https://gist.github.com/mspaulding06/34722cebfa8ae1072d34d82e88074244

Expected Behavior

Terraform should have applied the plan correctly

Actual Behavior

Failed to apply because of differences between the plan and the apply configurations.

Steps to Reproduce

  1. terraform init
  2. terraform apply

Please note that this failure does not always happen. I believe that this is related to a pull request I have submitted to the AWS provider.

#1797

If you notice in the crash gist the qualified ARN values for the lambda in the appVariables environment variable have different function versions (9 versus 10).

@Ninir Ninir added the bug Addresses a defect in current functionality. label Oct 11, 2017
@radeksimko radeksimko added the service/lambda Issues and PRs that pertain to the lambda service. label Jan 28, 2018
@github-actions
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Mar 29, 2020
@ghost
Copy link

ghost commented May 30, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators May 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/lambda Issues and PRs that pertain to the lambda service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

3 participants