Fix pylint(no-member) when accessing resource.id #4813
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.
Pylint currently reports
E1101: Instance of 'Bucket' has no 'id' member (no-member)
on lines in Pulumi Python programs like:Here's a description of this message from http://pylint-messages.wikidot.com/messages:e1101:
This appears to be a false positive case:
id
isn't set in the constructor (it's set later inregister_resource
) and Pylint isn't able to figure this out statically.urn
has the same problem. (Oddly, Pylint doesn't complain when accessing other resource output properties).This change refactors
register_resource
so thatid
andurn
can be assigned in the resource's constructor, so that Pylint can see it being assigned. The change also does the same withread_resource
.Fixes #3765