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
When more than one provider is configured, listing VMs will abruptly halt on the first ec2 provided VM if a ~/.fog file is not found, regardless of whether or not there are additional non-ec2 VMs to be listed.
For example, we currently see:
alias |provider |ip-address
--------------------------------------------------------------------------------
alias1 |provider |
Missing Credentials
Create the file /home/username/.fog with the following content:
===================== snippet begin =====================
---
:xxxxxxxxx:
:aws_access_key_id: <your aws_access_key_id>
:aws_secret_access_key: <your aws_secret_access_key>
===================== snippet end =====================
Note the absence of "alias3". With a ~/.fog file, we might expect to see:
When more than one provider is configured, listing VMs will abruptly halt on the first ec2 provided VM if a ~/.fog file is not found, regardless of whether or not there are additional non-ec2 VMs to be listed.
For example, we currently see:
Note the absence of "alias3". With a ~/.fog file, we might expect to see:
The text was updated successfully, but these errors were encountered: