Attributes in applicationloadbalancing reference types from alb #2362
Labels
area/providers
kind/bug
Some behavior is incorrect or out of spec
resolution/fixed
This issue was fixed
What happened?
I'm working on a project that involves schema traversal and I noticed something peculiar in the schema. There are two Identical data types declared for
ipAddressType
, one for thealb
module and one for theapplicationloadbalancing
module. This is also the same forloadBalanderType
and both cases expected and consistent with documentation. What is unusual is, schema for "aws:applicationloadbalancing/loadBalancer:LoadBalancer" starts at line 413732 and then describes the propertyipAddressType
at line 413787 with the$ref
as "#/types/aws:alb/ipAddressType:IpAddressType". It then describes the propertyloadBalancerType
at line 413792 with the$ref
as "#/types/aws:alb/loadBalanderType:LoadBalancerType". meanwhile "#/types/aws:applicationloadbalancing/ipAddressType:IpAddressType", and "#/types/aws:applicationloadbalancing/LoadBalancerType:LoadBalancerType" never get used at all in the schema.This does not cause any issues with conventional usage of Pulumi but can be troubling for people trying to use unsupported languages against the YAML runtime.
line 1033
line 9012
line 413787
line 2344
line 10323
line 413792
Expected Behavior
The
ipAddressType
property under "aws:applicationloadbalancing/loadBalancer:LoadBalancer" should reference the ipAddressType type fromapplicationloadbalancing
, notalb
example:
The
loadBalancerType
property under "aws:applicationloadbalancing/loadBalancer:LoadBalancer" should reference the loadBalanderType type fromapplicationloadbalancing
, notalb
example
Steps to reproduce
N/A
Output of
pulumi about
N/A
Additional context
I filed an issue with schema last week that is a little different but am linking here for visibility.
#2358
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: