Figure out graph queryability about pulumi HOT 4 CLOSED

This came up in a different place just now: resource providers.

The usage of Get APIs for fetching resources currently populates all properties on the resource, and I also expect us to end up with a List API that permits more ad-hoc querying. A more GraphQL like approach here would let you pick and choose which fields you want, possibly cutting down -- in some cases dramatically -- the amount of work required to execute a particular query.

This would be tough to add after the fact (because it changes the internal behavior of resource providers), and so I'm adding to 0.3 so we at least discuss it.

from pulumi.

I'm repurposing this work item to cover only the graph querying aspects -- presumably part of the service API -- and we will continue using #83 for resource APIs specifically.

from pulumi.

@hausdorff implemented a prototype in #2502 of adding checks into the Pulumi deployment process to block or warn on based on rules related to the desired state of a Pulumi deployment. This addresses a few of the issues above, as well as other "gating" scenarios.

This issue is rather old, and doesn't really capture the paths we expect to go down going forward. I suspect we should close this out and open new issues to track the concrete issues we are expect to invest in over coming months.

from pulumi.

We are now pursuing this as part of #2601.

from pulumi.