No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Screenshot 2022-01-04 at 3.05.39 PM.png

This option in the UI doesn't map directly to a property on the underlying resource, but I think it just uses the default values of:
```minTtl: 0,
defaultTtl: 86400,
maxTtl: 31536000,```

if we set minTtl = 0 , will not be considered as a non-caching scenario. we saw in one of the documentations -<https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-managed-cache-policies.html>

Our scenario is as below,
/pathname/123 - for this cache control headers is set from the servers itself,
but /pathname/abc - will not have any cache-control header from the server,
is there way to add different behaviours for this scenario?

<@U02S63BJFUP> there isn't always an API call that maps to to every console setting. you'll need to create a resource that has these values set and examine the created value to figure out what to set in the API