f65a1e8c1c
The current uplink access register method has the ability to write to AWS credential files. This is caused issues with repeat usage in recent AWS CLI code, and there was concern that it was an unstable solution. This version instead specifies various output formats "env" and "aws". "env" formats the text so that it can be used with 'export'. "Aws" generates "aws configure" commands to persist the credentials to the AWS credential files as the previous version could. Example usages: Setting ephemeral evironment variables in bash: export $(uplink access register $(storj-sim network env GATEWAY_0_ACCESS) --auth-service http://localhost:8000 --format env) Setting persistant configs via AWS CLI in bash: source <(uplink access register $(storj-sim network env GATEWAY_0_ACCESS) --auth-service http://localhost:8000 --format aws --aws-profile storjsim) Change-Id: I5d78d6462a3537780af3717a298bb2bebf9c2799 |
||
|---|---|---|
| .. | ||
| certificates | ||
| identity | ||
| inspector | ||
| internal | ||
| metric-receiver | ||
| multinode | ||
| satellite | ||
| segment-reaper | ||
| storagenode | ||
| storagenode-updater | ||
| storj-admin | ||
| storj-sim | ||
| uplink | ||
| versioncontrol | ||