For granted sso generate/populate commands add support to persist preferences in .granted/config #650
Comments
chrnorm
added a commit
that referenced
this issue
May 3, 2024
…651) * for granted sso command, add storing parameters in input config This reverts commit 00d95e1. * remove println * support multiple section names and remove deprecated source from config * remove println * For profile-template with a default, check IsSet instead of having a value * simplify referencing cfgSSO * add glag to populate * Update pkg/config/config.go * Update pkg/granted/sso.go --------- Co-authored-by: ibottamike <mike.sarver@ibotta.com> Co-authored-by: Chris Norman <17420369+chrnorm@users.noreply.github.com>
|
Implemented in #651! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The granted sso generate/populate commands have input for StartURL, SsoRegion, Prefix, Source, NoCredentialProcess, and ProfileTemplate.
Only having the parameters available as input variables require them to be enter every time the commands are run. In a dynamic environment where AWS accounts are added/removed, this requires the variables to be stored outside of granted configuration.
Add the capability to store the configuration values in
.granted/configto be consistent withregistry add/syncand assume browser preferences.The text was updated successfully, but these errors were encountered: