user
: handle unknown superuser passwords
#59
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, it's not possible to define configuration like this:
Given this configuration, the provider returns an error:
Upon further investigation, this error is returned from
CustomizeDiff
. This hook runs before a plan is rendered. This means that on first run, before theCreate
method forrandom_password
has run, the value forresult
is not yet known.GetOk
will still return_, true
, because it is known that some value is set. When the value is unknown,Get
will return the zero value. Any plan time inspection can only occur when the new value is known at plan time.While I didn't set up real cluster credentials to run the acceptance tests to success for this, I did execute them to ensure that the added test case fails with the original error and proceeds to a connection error with the fix.