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

Pivot Yaml template file could not be found on Amazon S3 bucket #95

Closed
cfregly opened this issue Jul 20, 2022 · 4 comments
Closed

Pivot Yaml template file could not be found on Amazon S3 bucket #95

cfregly opened this issue Jul 20, 2022 · 4 comments
Labels
type: bug Something isn't working

Comments

@cfregly
Copy link

cfregly commented Jul 20, 2022

Describe the bug

An error occurred (AWSResourceNotFound) when calling GET_PIVOT_ROLE_TEMPLATE operation: Pivot Yaml template file could not be found on Amazon S3 bucket

How to Reproduce

Pivot Yaml template file could not be found on Amazon S3 bucket

Expected behavior

No response

Your project

No response

Screenshots

image

OS

Mac

Python version

3.9

AWS data.all version

latest

Additional context

No response

@cfregly cfregly added the type: bug Something isn't working label Jul 20, 2022
@dlpzx
Copy link
Contributor

dlpzx commented Aug 2, 2022

Hello @cfregly, Can you give more details on the user that was performing the action, the groups that it belongs to, organisation and organisation admin groups?

@ouchl
Copy link

ouchl commented Aug 16, 2022

Hello @cfregly, Can you give more details on the user that was performing the action, the groups that it belongs to, organisation and organisation admin groups?

The pivot role template file is deployed by CDK. So the dev environment i.e. docker cannot find it.

@dlpzx
Copy link
Contributor

dlpzx commented Sep 6, 2022

Thank you @cfregly , so this is when you are working as a developer with the docker-compose deployment. Since you are not deploying anything, the developer environment has limitations, such as in this case when it tries to access resources that are available when you deploy data.all.

There are a few options here:

  • provide those resources in the AWS account whose credentials you are using (it is one of the requirements of the developer environment). These would include the yaml file and some secrets and parameters in Secrets Manager.
  • deploy data.all and use the credentials for the infra account with docker

At the end, a local developer environment does not completely substitute data.all deployment

@dlpzx dlpzx closed this as completed Sep 6, 2022
@github-actions
Copy link

github-actions bot commented Sep 6, 2022

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants