-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Epic
7 / 157 of 15 issues completed
Copy link
Labels
kind/epicLarge new features or investmentsLarge new features or investmentsresolution/fixedThis issue was fixedThis issue was fixed
Description
Project: https://github.com/orgs/pulumi/projects/289/views/1
There are a number of use cases where a provider wants to offer resources that share traits of both custom and component resources:
- Component-like -- the resource wants to report children/subresources (as can be done in
Construct
) - Custom-like -- the resource wants to be subjected to the CRUD lifecycle and observe
Create
,Update
and so on.
Presently, it is neither possible for a Construct
ed component to observe the CRUD lifecycle, nor for a custom resource to register children. This epic is about investigating the latter, in which a custom resource may return "virtual" resources as part of its CRUD operations. These resources are not "real" in the sense that they themselves do not receive dedicated lifecycle method calls, but they are still tracked by the engine, reported in diffs and CLI views, and visible in state, for instance.
Sub-issues
Metadata
Metadata
Assignees
Labels
kind/epicLarge new features or investmentsLarge new features or investmentsresolution/fixedThis issue was fixedThis issue was fixed