Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Beanstalk environment settings always diff

See original GitHub issue

Beanstalk Environment settings always show a diff after the first up.

Code to reproduce

https://gist.github.com/clstokes/a2ad22a0d9c0ede138f4d56383a67052

Steps to reproduce

pulumi up the code above
pulumi preview - observe diff of environment settings

Issue Analytics

State:
Created 3 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

2reactions

lukehobancommented, May 4, 2020

I’m going to close this out and continue tracking the few different issues identified here in other issues.

ID => ARN normalization: This appears to be by-design for Beanstalk, but could potentially be handled/suppressed better by the provider in https://github.com/terraform-providers/terraform-provider-aws/issues/280#issuecomment-333288403.
aws:elasticbeanstalk:customoption diffs: These aren’t actually persisted to Beanstalk. A pulumi refresh should solve these. We are considering whether to refresh by default in Pulumi in https://github.com/pulumi/pulumi/issues/2247, and this is another case that argues in favor of that.
Display of set diffs is confusing: I’ve opened https://github.com/pulumi/pulumi-terraform-bridge/issues/186 to track improving the display of set diffs where a single item is changing. That would help identify where there are (unexpected) changes happening more easily.

If anyone sees other cases of unexpected diffs with Beanstalk that are not addressed by any of the above, please do open a new issue with a repro!

0reactions

lukehobancommented, Apr 24, 2020

aws:elasticbeanstalk:customoption

It turns out, this kind of option doesn’t appear to get persisted in Beanstalk itself at all - it is not returned by aws elasticbeanstalk describe-configuration-settings. Terraform doesn’t see the constant diff in this case because it automatically refreshes, which removes this setting from the state file entirely. Running pulumi refresh has the same result - and will avoid seeing a diff here. Though only because in both cases, the IaC tool forgets this was ever provided as an input.

Top Results From Across the Web

Elastic Beanstalk rolling environment configuration updates

Rolling configuration update batches can be processed periodically (time-based), with a delay between each batch, or based on health. For time-based rolling ...

aws - elastic-beanstalk-environment - Terraform Registry

Terraform module to provision AWS Elastic Beanstalk environment ... (To suppress the module's rules, set create_security_group to false

beanstalk environment health check always in "red" color

i have an elastic beanstalk environment health issue, always show color "red". i am working with multiple environments 'cause i am dealing ...

AWS Elastic Beanstalk infrastructure in code with Terraform

solution_stack_name is the name of an environment that Elastic Beanstalk will set up on servers it manages. We've just specified that we want...

update-environment — AWS CLI 2.9.6 Command Reference

If specified, AWS Elastic Beanstalk updates the configuration set associated with the running environment and sets the specified configuration options to the ...