-
Notifications
You must be signed in to change notification settings - Fork 258
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: delete a project even if the current state is destroyed #1413
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! And the new test setup looks great!
#[test_context(TestProject)] | ||
#[tokio::test] | ||
async fn api_delete_project_that_is_ready(project: &mut TestProject) -> anyhow::Result<()> { | ||
project.router_call(Method::DELETE, "/delete").await; | ||
|
||
Ok(()) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clean! 😍 Can we apply these utilities for the existing tests as well, and break them up into smaller pieces (looking at you api_create_get_delete_projects
)? We can do it in a later PR to not block this for tomorrows release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yip, getting to them in another PR is the plan.... and maybe even adding them to the end of CI after the image builds 😄
Description of change
Causes the delete command to start up destroyed (stopped) projects to be able to delete them.
How has this been tested? (if applicable)
By making new gateway tests. Use the following steps to run them
If your tests take too long to run and eventually errors with
503
then make sure your firewall is not blocking any requests. See comments in the code.