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
#general
Title
# general
f
full-artist-27215
01/26/2022, 1:58 PM
Is there any formal way to annotate stack inputs and outputs with documentation strings to add additional context for their intention and purpose?
g
great-queen-39697
01/27/2022, 3:13 PM
Apologies for the delay. I don't know of a formal way to do it, but I'm double-checking with some other folks in case...
Turns out we don't. I've taken the liberty of opening an issue:
https://github.com/pulumi/pulumi/issues/8851
f
full-artist-27215
01/28/2022, 2:33 PM
Fantastic
@great-queen-39697
; thanks very much!
🙌 1
4 Views
Post