base64 : The term 'base64' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of
the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:41
+ terraform output admin1-user-password | base64 --decode --ignore-garb ...
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: (base64:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
From this error it seems like you don’t have the base64 program installed on your system, and so PowerShell (I think?) returned an error after trying to run it as a cmdlet, a program, vand various other PowerShell-specific things.
One way to proceed here would be to install the base64 program so that PowerShell can run it. Unix systems often have base64 available as part of GNU CoreUtils, but if you are on Windows then you may need to install GNU CoreUtils or some similar set of utilities yourself.
Alternatively, you may be able to perform base64 encoding using PowerShell-specific features. I don’t know much about PowerShell, but Microsoft.PowerShell.TextUtility seems to have a ConvertFrom-Base64 cmdlet in it which might help.
One Terraform-specific feedback I have is that you can use the -raw option for terraform output to get just the raw string value of that output value, rather than the human-oriented presentation it produces by default:
terraform output -raw admin1-user-password
That’ll hopefully make it easier to decode base64 as a separate step, without needing to resort to --ignore-garbage or other similar functionality of a different base64-decoding mechanism.
Yes you are right the base64 utility was not present on my Windows. However i have installed both gnu and base64 utility. After that now i am getting the following error.
Unfortunately that seems to be a Keybase error code rather than a Terraform error code, so I can’t directly help with that part. It seems like someone else had a similar problem on Windows but I’m not sure if the discussion there actually found a cause:
I managed to decrypt using admin command “cmd” instead of PowerShell. Same command but executed from cmd worked for me. Thanks for your advise and support.