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
CFn: allow for pro resource provider overrides #9333
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!!
0f14be8
to
980dd44
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not 100% sure I like the approach with two different plugin managers, since it feels like we shouldn't need it.
An alternative could be appending a certain suffix the the plugin name when coming from ext and then handling that logic in the community plugin manager directly.
For now I don't really want to block this too much, especially since we can re-evaluate this setup at a later stage without any user-facing changes. So feel free to merge as is!
LOG.debug( | ||
( | ||
"Failed to load resource type %s from pro as a ResourceProvider. " | ||
"Maybe this resource is implemented in community." | ||
), | ||
resource_type, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like this is a bit too noisy for community usage.
b5f4c84
to
40bb7fe
Compare
40bb7fe
to
926cee0
Compare
Motivation
We disabled AWS::ECR::Repository in #9315 because we did not have an override system for resource providers in community vs pro. In particular, we had:
GenericBaseModel
subclassResourceProvider
GenericBaseModel
subclassIn this case, the community resource provider was being chosen, rather than the pro
GenericBaseModel
subclass.Changes
Most of the changes to allow us to revert #9315 have been made in the pro repository. In addition, we are trying to handle the case where we have pro and community resource providers.
TODO