You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will only work, if module.boundary is applied beforehand.
addr and kms information is only known after module.boundary is applied. I'm not sure why isn't the provider deferring the evaluation of these variables until they are known.
Can the boundary provider attempt to contact boundary server during run time?
The text was updated successfully, but these errors were encountered:
We are also seeing this problem. As boundary doesn't support the IAM role chaining that we require for our environment, we are trying to pass the variables in from an external script
I have the following provider declaration:
This will only work, if
module.boundary
is applied beforehand.addr
andkms
information is only known aftermodule.boundary
is applied. I'm not sure why isn't the provider deferring the evaluation of these variables until they are known.Can the boundary provider attempt to contact boundary server during run time?
The text was updated successfully, but these errors were encountered: