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

Use the ops._private.harness.ActionFailed object #201

Open
tonyandrewmeyer opened this issue Sep 23, 2024 · 0 comments
Open

Use the ops._private.harness.ActionFailed object #201

tonyandrewmeyer opened this issue Sep 23, 2024 · 0 comments
Assignees
Labels

Comments

@tonyandrewmeyer
Copy link
Collaborator

@benhoyt and I decided that rather than monkey(patch) about with having an ActionFailed object in both Harness and Scenario and then trying to merge them when using Scenario via ops.testing, it would be better to just have the Harness object support a state attribute (always None when using with Harness).

This means that the object can be removed from Scenario (I guess re-exporting the name for backwards compatibility) and the ops._private.harness one used instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant