https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
s
would really appreciate any guidance and apologies if I'm doing something silly!
also, if i only specify 
routingRules
but not 
redirectAllRequestsTo
, then i get 
Must specify either index_document or redirect_all_requests_to.
upon executing 
pulumi up
😕
b
try running 
pulumi refresh
after changing the value in the Web UI
s
that worked, thanks! is there anyway to handle this completely within pulumi?
im nervous about changing anything in the web UI because it could be a source of inconsistencies between staging/prod
b
I would look at the detailed diff and see what values changed
try to match the interfaces
if you look at some of the examples it looks like they treat the JSON object as a string https://www.pulumi.com/docs/reference/pkg/aws/s3/bucket/#static-website-hosting
s
okay gotcha, thanks! btw, i was wondering if there's continued investment on import. we found it super useful for migrating our infrastructure to code, and would be excited about a way to specify an arn and have pulumi output the inputs it expects. was wondering what you think? also lmk if i missed it or if it doesnt make sense 😛
b
I think if you try to import a resource that doesn’t match the spec you wrote pulumi will error and provide you with the diff
it doesn’t necessarily write the code for you, but it will at least tell you what needs to change before the resource can be imported into state
s
oh let me look into it more next time! i remember seeing which fields were different, but not the expansion of those fields...thanks for clarifying 🙂
7 Views
Open in Slack
PreviousNext
Powered by