Skip to content

fix: 🐛 Add permission boundary to static deploy lambda #38

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

Merged
merged 1 commit into from
Jan 18, 2021
Merged

fix: 🐛 Add permission boundary to static deploy lambda #38

merged 1 commit into from
Jan 18, 2021

Conversation

maael
Copy link
Contributor

@maael maael commented Jan 18, 2021

This is the last place that this should be needed. Sorry for staggering this boundary change over multiple PRs, and thanks for being so responsive and all your work on this module.

This is the last place that this should be needed. Sorry for staggering
this boundary change over multiple PRs, and thanks for being so
responsive and all your work on this module.
Copy link
Member

@ofhouse ofhouse left a comment

Choose a reason for hiding this comment

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

No worries, it is hard to land a feature with a single PR on first try in a foreign code base.
Thanks for fixing it 👍

@ofhouse ofhouse merged commit 332fc52 into milliHQ:main Jan 18, 2021
@ofhouse
Copy link
Member

ofhouse commented Jan 18, 2021

Now released in v0.6.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants