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

[tf] tf change to properly configure lambda functions SA can invoke #197

Merged
merged 2 commits into from
Jun 23, 2017

Conversation

ryandeivert
Copy link
Contributor

@ryandeivert ryandeivert commented Jun 23, 2017

to @austinbyers , @jacknagz
cc @airbnb/streamalert-maintainers
size: small

bug fix

  • With some updates to properly invoke a lambda function with a designated qualifier, we broke terraform's configuration of said function.
    • Previously, tf was creating a policy using the function name combined with the qualifier.
    • This prevented proper invocation with a specific qualifier using boto3
    • The change is to strip off the qualifier, and only use the function name when creating the policy.
  • If a qualifier is not provided in the outputs.json configuration for this lambda, it does not break this logic. The interpolation will still extract the proper function name.
  • Updating the example outputs.json configuration to include a qualifier along with the function name.

Other change

  • Updating the message the lambda output configuration prompts with when asking for a function name. It previously requested an ARN, which should not be used now. It is clarified as requiring a function name and optional qualifier (function_name:qualifier)

@coveralls
Copy link

Coverage Status

Coverage remained the same at 79.307% when pulling 43bd379 on ryandeivert-lambda-tf-fix into ebdda9c on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 79.307% when pulling f3c71ba on ryandeivert-lambda-tf-fix into ebdda9c on master.

Copy link
Contributor

@austinbyers austinbyers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay!

@coveralls
Copy link

Coverage Status

Coverage remained the same at 79.307% when pulling ffbb118 on ryandeivert-lambda-tf-fix into ebdda9c on master.

@ryandeivert ryandeivert merged commit 68ace7f into master Jun 23, 2017
@ryandeivert ryandeivert deleted the ryandeivert-lambda-tf-fix branch June 23, 2017 23:28
@ryandeivert ryandeivert added this to the 1.4.0 milestone Jun 26, 2017
@jacknagz jacknagz added the bug label Jul 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants