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
@jpatigny made an interesting point in #34 (comment) regarding the use of the provider within a windows container. That could potentially allow the provider to run without having to worry about authenticating.
The general idea would be for the provider to run the powershell commands directly instead of using winRM if :
It's running on Windows.
There are no credentials defined at all.
The text was updated successfully, but these errors were encountered:
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked as resolved and limited conversation to collaborators
May 15, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@jpatigny made an interesting point in #34 (comment) regarding the use of the provider within a windows container. That could potentially allow the provider to run without having to worry about authenticating.
The general idea would be for the provider to run the powershell commands directly instead of using winRM if :
The text was updated successfully, but these errors were encountered: