8000
add service_name attribute to AssetDirectory #9125
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
In the
StateVisitor
implementations that handle cloud pod state, there is currently no way to know which service theAssetDirectory
being visited belongs to, unlikeAccountRegionBundle
andBackendDict
which both have aservice_name
attribute.Knowing the service name for an
AssetDirectory
is required for technical reasons for s3 v3 persistence.Changes
StateContainer
a protocol and makeservice_name
a mandatory attributeAssetDirectory
to correctly use the service name