Channels
esc
welcome
pulumi-cdk
cloudengineering
yaml
blog-posts
localstack
pulumi-ai
package-authoring
policy-as-code
pulumiup-booth-support
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
gitlab
general
pulumi-kubernetes-operator
jobs
pulumi-deployments
dotnet
aws
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
Powered by
#golang
Title
# golang
b
bland-florist-27487
07/19/2022, 12:35 PM
Hi! Are there any decision documents I can refer to when trying to understand why Pulumi defines its own string- and array-types?
b
billowy-army-68599
07/19/2022, 2:54 PM
https://www.pulumi.com/docs/intro/concepts/inputs-outputs/
This may help you understand why as well:
https://leebriggs.co.uk/blog/2021/05/09/pulumi-apply
Essentially it’s the same reason as the AWS SDK, the types are async in nature and because Go doesn’t have generics, we need a way to represent they’re eventual
b
bland-florist-27487
07/19/2022, 3:41 PM
Ah, so this approach may change with the recent introduction of generics?
(introduced in go 1.18)
b
billowy-army-68599
07/19/2022, 3:54 PM
Yes we’re investigating that at the moment
💯 1
b
bland-florist-27487
07/19/2022, 3:58 PM
Excited to see what you conclude, will keep an eye on the blog 🙂
5 Views
Post