Skip to content

Conversation

@shayshim
Copy link
Collaborator

@shayshim shayshim commented Feb 8, 2026

  • The pull request is targeting the main branch.
  • The code has been validated to compile successfully by running go vet ./....
  • The code has been formatted properly using go fmt ./....
  • All static analysis checks passed.
  • All tests have passed. If this feature is not already covered by the tests, new tests have been added.
  • All E2E tests have passed.
  • All changes are detailed at the description.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2026

Test Results

18 tests  ±0   17 ✅ ±0   1m 47s ⏱️ +11s
 2 suites ±0    1 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit f006882. ± Comparison against base commit de92ba6.

♻️ This comment has been updated with latest results.

}

if response.StatusCode != http.StatusCreated {
// Dry run returns http.StatusOK
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After Yuri's PR is merged, let's make sure it's valid also when async == true.

expectedError: "",
},
{
name: "success with dry-run (201 Created)",
Copy link
Collaborator

@asafgabai asafgabai Feb 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to test both 200 and 201? Does this request return 201 sometimes?

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

Successfully merging this pull request may close these issues.

2 participants