Skip to content

remove 'outputs' from 'finish' calls#244

Open
valentin-grisel wants to merge 1 commit intothunderbird:mainfrom
valentin-grisel:remove-'outputs'-from-'finish'-calls
Open

remove 'outputs' from 'finish' calls#244
valentin-grisel wants to merge 1 commit intothunderbird:mainfrom
valentin-grisel:remove-'outputs'-from-'finish'-calls

Conversation

@valentin-grisel
Copy link

Description of the Change

Removed 'outputs' from 'finish' calls.

Benefits

Ready for next version.

Applicable Issues

pulumi/pulumi#242

self.resources = resources
if len(outputs) > 0:
pulumi.warn(FINISH_OUTPUTS_DEPRECATION_MESSAGE)
self.register_outputs(outputs)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The documentation still indicates that calling register_outputs is necessary because it "signals to the Pulumi engine that the component resource has finished registering all its child resources and should be considered complete," even if we are not using it for actual outputs. I think this call still needs to happen, but with no outputs in the parameters.

@ryanjjung
Copy link
Collaborator

This thread is pretty enlightening. The Pulumi devs seem to not really understand why this should be called, at least to some extent. Sounds like maybe some tech debt. No biggie. The consensus there is that there is some minimum convenience created by making the register_outputs call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants