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

Bad shell return code after "Validation tables already exist" #44

Open
ThrawnCA opened this issue May 30, 2019 · 0 comments
Open

Bad shell return code after "Validation tables already exist" #44

ThrawnCA opened this issue May 30, 2019 · 0 comments

Comments

@ThrawnCA
Copy link
Contributor

ThrawnCA commented May 30, 2019

When the paster init-db command finds that the validation tables already exist, it returns a shell exit code of 1, indicating failure. However, since the command appears to otherwise be idempotent, this isn't really a failure. The desired end state has been achieved.

This exit code causes problems when the paster command is being run as part of a larger system, like a Chef cookbook. It has to be caught and handled every time to stop the cookbook exiting due to the presumed error.

If it's desirable to detect whether the tables already exist, perhaps there could instead be a separate paster command for this?

@roll roll added this to Software in Frictionless General Jun 3, 2019
@roll roll added the bug label Jun 3, 2019
@roll roll moved this from Software (core) to Software (contrib) in Frictionless General Jul 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Frictionless General
  
Software (wide)
Development

No branches or pull requests

2 participants