We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
from this discussion: #417 (comment)
Currently, there is some brittleness around how our AWS resource calls and the id extraction are separated from each other.
This is currently leading to vague and brittle get_resource_id() functions that parameterize uses to get the test id.
get_resource_id()
parameterize
Along side this, there are what amount to hacks for dealing with "resources" that are lists or do not exist (i.e. https://github.com/mozilla/frost/pull/417/files#diff-ee242f021608b58d502ee9c4c6273c6145f18e6703f8329b3799c50db5c8fe95R155)
As a result, it seems like it may make sense to transform the resources.py functions into classes (dataclasses, boto3 classes, etc).
resources.py
The text was updated successfully, but these errors were encountered:
No branches or pull requests
from this discussion: #417 (comment)
Currently, there is some brittleness around how our AWS resource calls and the id extraction are separated from each other.
This is currently leading to vague and brittle
get_resource_id()
functions thatparameterize
uses to get the test id.Along side this, there are what amount to hacks for dealing with "resources" that are lists or do not exist (i.e. https://github.com/mozilla/frost/pull/417/files#diff-ee242f021608b58d502ee9c4c6273c6145f18e6703f8329b3799c50db5c8fe95R155)
As a result, it seems like it may make sense to transform the
resources.py
functions into classes (dataclasses, boto3 classes, etc).The text was updated successfully, but these errors were encountered: