[S3] Parse AWS configuration with support for profile section

[mannreis]

Hello 👋!

I've faced a minor problem on my setup when I have a profile section on the configuration file [1] (valid with aws tools). In such case the netcdf library fails to load the AWS config, not critical but not obvious.

This is a quick fix I did for my myself, but looking at the parser and aws config specification I see parsing problems with:

• Token delimiter characters in the values
• Support for comments
• Multiline service configuration

I'm not sure to which extend you want to support loading the AWS config when the building with the internal S3 implementation.

Thanks!

[1]
~/.aws/credentials

[default]
aws_access_key_id=123
aws_secret_access_key=456

[user1]
aws_access_key_id=123
aws_secret_access_key=789

~/.aws/config

[default]
region=us-west-2
output=json

[profile user1]
region=us-east-1
output=text

[DennisHeimbigner]

Let me make sure I understand.

1. When the profile name is specified as e.g "[user1]", the file (either credentials and config) parse correctly.
2. When the profile name is specified as e.g "[profile user1]", the file (either credentials and config) does not parse.

Have I stated the problem correctly?

[mannreis]

Exactly!

[DennisHeimbigner]

The best way to create a file in bash/sh is to use this method:

https://jinnabaalu.medium.com/create-a-file-in-bash-using-eof-af5af33c0d1f

[WardF]

Just checking in @DennisHeimbigner and @mannreis in regards to the latest changes requests. It looks like @mannreis made some changes, how does this look now @DennisHeimbigner ?

[DennisHeimbigner]

One more change, please. Remove the .aws directory at the end of the shell script so that automake distcheck will not fail.