terraform-aws-elastic-beanstalk-environment
terraform-aws-elastic-beanstalk-environment copied to clipboard
Bring back the SSHSourceRestriction setting.
what
- Bring back the SSHSourceRestriction
why
- This got accidentally removed in a previous commit https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/commit/fe6d0d7242dff18928cc204fb3c693e104978b17#diff-7a370d8342e7203b805911c92454f0f4L494
references
- Open ticket: https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/issues/123
/test all
/test all
/rebuild-readme
@DangerDawson could you please rebuild the readme by running make readme
or allow access to your branch?
@joe-niland I am curious, what does a readme rebuild have to do with adding a single Beanstalk setting
?
@razorsedge technically nothing. Normally it's required when variables.tf is changed. In this case, the test is failing, perhaps because a previous PR was merged without making sure tests pass. We should fix it on this PR.
@DangerDawson please resolve the conflicts
How can I help to get this issue with ssh_source_restriction
resolved?
/rebuild-readme
/terratest
Thanks @DangerDawson for creating this pull request!
A maintainer will review your changes shortly. Please don't be discouraged if it takes a while.
While you wait, make sure to review our contributor guidelines.
[!TIP]
Need help or want to ask for a PR review to be expedited?
Join us on Slack in the
#pr-reviews
channel.