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
Please add support for the ResilienceHub API #7438
Comments
Hi @StevenCaswellVR, I'll mark it as an enhancement. Is it just the one method that you need? |
Actually there are several methods I need:
It would be nice to have all of the list_* methods but those above are the most critical. Thanks. |
Moto >= 5.0.4.dev7 now contains the following methods:
Note that the If I'm understanding the workflow correctly, the following methods would need to be called (at minimum) to start an assessment:
So before we can show actual data in the Let me know if that's desired, and/or if you're running into any issues so far. |
I will start checking out the 5.0.4.dev7 later today. I think more likely the workflow sequence that would work would be:
I'm somewhat guessing as I've not used this particular flow, as I've been mostly focused on the import_resources_to_draft_app_version followed by resolve_app_version_resources flow. Unfortunately I think this flow might be too difficult to mock as the import reads live resources (i.e., from a terraform state file) and populates the app structure based on that content. While I'd love to be able to have that flow mocked, it feels like that could be difficult. Thanks. |
Hi @StevenCaswellVR! Moto >= 5.0.4.dev19 now also has support for:
|
moto >= 5.0.8.dev5 now has the ability to configure the results of the As far as I can tell, that covers everything, so I'll close this. Feel free to open new issue if you run into problems though, or would like to see support for other features. |
I am using moto 5.0.2, Python mocks with Python 3.11.3, boto3 1.26.68, botocore 1.29.165.
I have the following code:
When running this code I get the following error:
The text was updated successfully, but these errors were encountered: