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
README.md claims the following about the region setting:
In order of precedence:
region: in the inventory or config file
ENV['AWS_REGION']
~/.aws/credentials
The Bolt task does not seem to respect the region set in either ~/.aws/credentials or in ~/.aws/config. In general reading the region from the credentials file might or might not work, but it seems incorrect. The official AWS documentation says thats ensitive settings should go to credentials and insensitive to config. That's what "aws configure" command also does.
A related issue is that setting AWS_REGION environment variable (as documented) does not seem to work. You need to explicitly set the region with env_var plugin, e.g. like this:
I would expect the region setting in a named profile in ~/.aws/config to be respected by this inventory plugin. I would also expect AWS_REGION environment parameter to be respected without extra tricks like using the env_var plugin.
Steps to Reproduce
Add an aws_inventory group to inventory.yaml. For example:
Describe the Bug
README.md claims the following about the region setting:
In order of precedence:
The Bolt task does not seem to respect the region set in either ~/.aws/credentials or in ~/.aws/config. In general reading the region from the credentials file might or might not work, but it seems incorrect. The official AWS documentation says thats ensitive settings should go to credentials and insensitive to config. That's what "aws configure" command also does.
A related issue is that setting AWS_REGION environment variable (as documented) does not seem to work. You need to explicitly set the region with env_var plugin, e.g. like this:
Expected Behavior
I would expect the region setting in a named profile in ~/.aws/config to be respected by this inventory plugin. I would also expect AWS_REGION environment parameter to be respected without extra tricks like using the env_var plugin.
Steps to Reproduce
Add an aws_inventory group to inventory.yaml. For example:
Create ~/.aws/credentials:
Create ~/.aws/config:
Set AWS_PROFILE environment variable:
Now try to use the inventory:
Environment
Additional context
Things that did not help:
The text was updated successfully, but these errors were encountered: