-
Notifications
You must be signed in to change notification settings - Fork 5
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
This project doesn't work #50
Comments
Hi @donfirst! And thanks for filing this issue. I'm aware of this issue from before, but unfortunately I haven't had the time to get around to it yet. Planning to set aside some time for this next week, and hopefully we can get things back to a working state then. Could you describe the steps you take and where exactly things break and how? I'll make sure to keep you in the loop as I try to find out what's changed here since I worked on this the last time. |
Wanted to say that you are doing an awesome job !!! I have found a couple of issues
should be 3)Following instruction from a) c)cd hooks d) So far so good :-) Now I'm going to lambda -> no function has been created Deploying any cf Check lambda and there is no lambda Seems that this CF file has not been deployed |
Thank you @donfirst! That's really helpful 👍 I'll use your findings as my starting point when I get to this. In the meantime, don't hesitate to submit corrections for any of the issues you've found here or in the OPA docs. Given that this used to work, it's likely "just" some change AWS did that we need to account for. The problem is of course identifying what that change might be :) |
@anderseknert If you. are interested I can participate in that project - fix documentation and explain. how does it work |
That's great! Yes, I'd be very happy for any help I can get here, as it's been quite a while since I worked on this 😃 |
Unfortunately, this project is broken
This is just a warning to everyone who wants to play around with this PLUGIN
using this command
cfn submit --set-default
You can't build the Lambda
So you can build and deploy two stack
CloudFormationManagedUploadInfrastructure
styra-opa-hook-role-stack
You can build and upload one zip file to the S3 (styra-opa-hook-{date}.zip)
But there is a missing step. to deploy lambda and connect that lambda to the hook
So the effect is that after. hook activation ALWAYS you will get an error message during CF deployment that it's impossible to connect to your opa server- hook is not able to connect to lambda ( lambda doesn't exist)
The text was updated successfully, but these errors were encountered: