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

[Bug] data.all created database during dataset importing #1753

Open
TejasRGitHub opened this issue Jan 24, 2025 · 0 comments
Open

[Bug] data.all created database during dataset importing #1753

TejasRGitHub opened this issue Jan 24, 2025 · 0 comments

Comments

@TejasRGitHub
Copy link
Contributor

Describe the bug

In data.all, while importing a dataset, a database can be specified which can then be imported.

While running the dataset stack, a custom resource ( which uses a lambda created at the time of environment stack creation ) runs a lambda , which does the work of creating a database if it doesn't exist in the aws account.

When a dataset is imported and a database is specified which doesn't exists, then this lambda creates this database. In case if a database is not specified then data.all creates a database while importing the dataset.

As a user, I don't want data.all to create any database, or delete any imported database

How to Reproduce

*P.S. Please do not attach files as it's considered a security risk. Add code snippets directly in the message body as much as possible.*

Import a dataset with an S3 and KMS but specify incorrect database

Expected behavior

Data.all should not create the database and leave it as it is

Your project

No response

Screenshots

No response

OS

MacOS

Python version

3.9

AWS data.all version

2.6

Additional context

No response

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

No branches or pull requests

1 participant