That's not the best explanation. I'm trying to build a framework for reviewing the objects with types from
pulumi_aws
in a Pulumi stack and providing users a way to what constructor parameters they'll need to enter for those objects.
For example, with
aws.organizations.Organization
, I'd want to know that I'd need to set the parameters of
aws_service_access_principals
,
enabled_policy_types
,
feature_set
are available (
source). We want to fill these parameters with values from a data store. So for
aws.organizations.Organization
, we should be able to retrieve the values of
aws_service_access_principals
from a document.
We want to have configuration provider similar to the secrets provider that are available with Pulumi. The way that configuration is currently tied to a stack, it seems that the intended association should be environment yaml to stack. This becomes limiting when we want to deploy multiple versions of the stack (for example, multiple RDS/Aurora instances) with different configuration.