mirror of
https://github.com/patrickchugh/terravision.git
synced 2026-05-09 08:25:25 +02:00
[GH-ISSUE #107] Add support for different AWS profiles #53
Labels
No labels
bug
enhancement
enhancement
good first issue
good first issue
good first issue
pipeline
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/terravision#53
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jacopobr on GitHub (Feb 25, 2024).
Original GitHub issue: https://github.com/patrickchugh/terravision/issues/107
Currently, Terravision utilizes AWS APIs through the default AWS profile located in .aws/credentials. However, it would greatly enhance the functionality if users could select the profile through which to run the AWS commands. This would provide greater flexibility and control over AWS resources for Terravision users.
An AWS CLI example is the following:
aws ec2 describe-instances --profile user1@gothrek22 commented on GitHub (Mar 11, 2024):
If it uses boto, then you can probably set AWS_PROFILE=desired_profile_name.
@patrickchugh commented on GitHub (Apr 4, 2026):
Closing as feature is not controlled by terravision and can be override with environment variables and config files