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
{{ message }}
This repository has been archived by the owner on Feb 5, 2020. It is now read-only.
AWS key, secret, & STS token are currently in environment vars. This makes it really hard to apply/destroy a cluster that a user created with the GUI installer. These should be TF vars like region.
The text was updated successfully, but these errors were encountered:
ggreer
added this to the
Theme: Overall cleanup and stability milestone
May 10, 2017
This opens up the same conversation like we had for the tectonic license and quay pull secreted.
I don't think credentials in configuration are any kind of good practice. Region is not a part of the credentials set.
In the case of using an impersonated role, Terraform itself can do that impersonation, so there's no need to struggle with injecting these three values. They're also refreshed on every run, so no more annoying expired sessions.
If we want to streamline the credentials injection story, I think this is a better path to follow. Ask users to have a role available and put that role in tfvars to be passed to the provider.
Did I mention that credentials in configuration are bad practice? :)
There is some friction, but it sounds like this is normal. Of course, throwing secrets in the file needs to be very controlled. Sounds like we should skip for now.
AWS key, secret, & STS token are currently in environment vars. This makes it really hard to apply/destroy a cluster that a user created with the GUI installer. These should be TF vars like region.
The text was updated successfully, but these errors were encountered: