You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when pass apiary_producer_iam_role to bucket policy, it only looks up the value of the variable, but when we define the producer role, we have a schema name(key) specified, that is not considered when we passing roles, which will cause all iam roles lists here will have permission to all schemas.
To Reproduce
Steps to reproduce the behaviour ideally including the configuration files you are using (feel free to rename any sensitive information like server and table names etc.)
Expected behavior
A clear and concise description of what you expected to happen.
Logs
Please add the log output from Apiary when the terraform error occurs, full stack traces are especially useful.
Versions (please complete the following information):
Apiary Version:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
in here: https://github.com/ExpediaGroup/apiary-data-lake/blob/master/common.tf#L35C3-L35C30
when pass
apiary_producer_iam_role
to bucket policy, it only looks up thevalue
of the variable, but when we define the producer role, we have a schema name(key) specified, that is not considered when we passing roles, which will cause all iam roles lists here will have permission to all schemas.To Reproduce
Steps to reproduce the behaviour ideally including the configuration files you are using (feel free to rename any sensitive information like server and table names etc.)
Expected behavior
A clear and concise description of what you expected to happen.
Logs
Please add the log output from Apiary when the terraform error occurs, full stack traces are especially useful.
Versions (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: