-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] How to configure optional-computed properties? #21278
Comments
Hi @dikhan! Your idea is the right one: the meaning of The analogy to Please note that we use GitHub issues for tracking bugs and enhancements rather than for questions. While we may be able to help with certain simple problems here it's generally better to use one of the community forums where there are far more people ready to help, whereas the GitHub issues here are generally monitored only by our few core maintainers. |
Hello again! We didn't hear back from you, so I'm going to close this in the hope that a previous response gave you the information you needed. If not, please do feel free to re-open this and leave another comment with the information my human friends requested above. Thanks! |
Hi, sorry for the late response here. Yep, the response helped a lot, thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hi guys,
Quick question:
What would be the best way to represent in the resource schema a property that is optional but may be computed by the API if the value is not provided by the user? Wondering if setting the property as both Optional = true AND Computed = true would be the way to go.
I see the resource schema has a Default field, that if populated will make terraform assign that value to the property if not provided as input by the user...However, if the API is already computing the value if it's not provided, why should Terraform push the value instead? That means that a change in the API to update the default value to a different one, will also require a change in the provider too.
Thanks!
Dani
The text was updated successfully, but these errors were encountered: