Skip to content

Optimize logging #70

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.

Sign up for GitHub

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

Jump to bottom
Closed
ckunki opened this issue Jun 26, 2024 · 0 comments · Fixed by #71
Closed

Optimize logging #70

ckunki opened this issue Jun 26, 2024 · 0 comments · Fixed by #71
Assignees
@ckunki
Labels
refactoring Code improvement without behavior change

Comments

@ckunki
Copy link
Collaborator

ckunki commented Jun 26, 2024 •
edited
Loading

Currently creating a database and waiting until it's operational still contains a print statement.

Acceptance criteria

  • print statement is replaced by LOG.info()
@ckunki ckunki self-assigned this Jun 26, 2024
@ckunki ckunki added the refactoring Code improvement without behavior change label Jun 26, 2024
ckunki added a commit that referenced this issue Jun 26, 2024
@ckunki
#70: Optimized logging
0058b8c 
Additionaly changed schedule checking if open api is outdated to 2 am.
@ckunki ckunki mentioned this issue Jun 26, 2024
Merged
ckunki added a commit that referenced this issue Jun 26, 2024
@ckunki
#70: Optimized logging (#71)
9b74483 
* #70: Optimized logging

Additionaly changed schedule checking if open api is outdated to 2 am.

* Used tenacity when checking if a SaaS DB instance has been deleted
* Fixed review finding.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ckunki ckunki

Labels
refactoring Code improvement without behavior change
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#70: Optimized logging exasol/saas-api-python
1 participant
@ckunki