Skip to content

Update assertion for Docker test

Steve Xuereb requested to merge follow-up-mr-1889 into master

What does this MR do?

Update assertion for Docker test

Why was this MR needed?

In !1889 (merged) we removed the feature flag, so this assertion is not a Maybe but always gets called. Before when the feature flag was turned on it would have not called this method

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Added tests for this feature/bug
  • In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

Small follow up from !1889 (merged)

Merge request reports