Describe the bug
A config file with defined profiles but no root [config] section throws an ambiguous message about a missing provider-url when one is supplied in the sub-config level.
To Reproduce
Steps to reproduce the behavior:
- Set up a config with a profile but no root
[config] block
- Run
aws-cli-auth saml --cfg-section foo -s
Expected behavior
It should work and go and get credentials for that profile despite the missing [config] section.
Screenshots
Desktop (please complete the following information):
- OS: N/A (First seen on MacOS, repro'd just now on Windows)
- Version aws-cli-auth version 0.17.2
- Revision a98af8c
Additional context
It seems ini isn't massively well defined but most parsers accept this. At the very least we should see if we can provide a better error message but the ideal would be to fix this and allow an omitted [config] section.
Describe the bug
A config file with defined profiles but no root
[config]section throws an ambiguous message about a missingprovider-urlwhen one is supplied in the sub-config level.[config.foo] ...To Reproduce
Steps to reproduce the behavior:
[config]blockaws-cli-auth saml --cfg-section foo -sExpected behavior
It should work and go and get credentials for that profile despite the missing
[config]section.Screenshots
Desktop (please complete the following information):
Additional context
It seems ini isn't massively well defined but most parsers accept this. At the very least we should see if we can provide a better error message but the ideal would be to fix this and allow an omitted
[config]section.