-
Notifications
You must be signed in to change notification settings - Fork 12
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
Interpret JSON Config values #269
Conversation
…emas This is preperation for introducing a complex configuration middleware. The middleware will impose the additional requirement that infer based providers must serve a valid schema for CheckConfig to be called on them.
334fa8c
to
ea8d6ff
Compare
cf5b103
to
bd67f7e
Compare
Does this need to cover old config in DiffConfig or CheckConfig suffices? Perhaps as a follow-up. |
`complexconfig` is marked as deprecated so that we can safely remove it in a later version.
ed79b84
to
6a7a911
Compare
I think it should be ok 🤞: From message DiffRequest {
...
// the new input values of resource to diff, copied from CheckResponse.inputs.
google.protobuf.Struct news = 4;
...
} I'll double check that this applies for providers as well. |
Check config is definitely called on new provider config before diff is called, so I think this should work by just overriding CheckConfig. |
This PR has been shipped in release v0.22.0. |
This PR has been shipped in release v0.23.0. |
This PR adds a middleware to handle decoding JSON encoded config values. The middleware is marked as deprecated, since we would like to remove this functionality as soon as pulumi/pulumi#15032 closes.
Fixes #171