Open ederst opened 1 month ago
Thanks for reporting @ederst and sorry for the inconvenience, I've raised a PR to fix this: Use automatic module mappings in Openstack provider #692
It also automates this for future resources, so we should not see this again.
Ran into some issues with the PR, will try to resolve them early next week, sorry for the delay.
Ran into some issues with the PR, will try to resolve them early next week, sorry for the delay.
Nothing to worry about, we currently use the Loadbalancer resource mapped at index and it works just fine.
Describe what happened
After upgrading to pulumi-openstack v5.0.0
loadbalancer.Loadbalancer
is not available anymore. Instead the resource seems to have been replaced withLbLoadbalancerV2
. The crux here is that this resource is mapped atindex
and not in theloadbalancer
module/package - like for exampleloadbalancer.L7PolicyV2
.This seems to be true for multiple resources - see "Affected Resource(s)".
To fix this, the resources need a proper mapping in
resources.go
. For example like this, I guess:Sample program
Log output
No response
Affected Resource(s)
Output of
pulumi about
Additional context
No response
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).