Registry markers cause AWS SDK ProfileFileReader warnings due to invalid config format

[adrian-arapiles]

Description

The Profile Registry feature uses section markers [granted_registry_start <name>] and [granted_registry_end <name>] in the AWS config file to manage synced profiles. These markers violate the AWS config file format specification and cause repetitive warnings from AWS SDKs.

Steps to Reproduce

1. Set up a Profile Registry using granted registry add <repo>
2. Run granted registry sync
3. Use any application that reads the AWS config file via the AWS SDK (Java, Python, JavaScript, etc.)

Expected Behavior

No warnings should be emitted when applications read the AWS config file managed by Granted.

Actual Behavior

AWS SDKs emit warnings because the registry markers are not valid profile sections. Valid AWS config sections must be either [default] or [profile <name>].

Example Warnings (Java AWS SDK v2):

WARN s.a.a.p.internal.ProfileFileReader : Ignoring profile 'granted_registry_start XXXX' on line 4 because it did not start with 'profile ' and it was not 'default'.

These warnings appear multiple times during application startup as the SDK parses the config file repeatedly.

Current Config File Format:

# Auto-generated by Granted (https://granted.dev). DO NOT EDIT.
# Manual edits to this section will be overwritten.
# To stop syncing and remove this section, run 'granted registry remove'.
[granted_registry_start XXX]

[profile XXX]
...

[granted_registry_end XXX]

I don't see any way to achieve that, but a possible approach to that could be:

Proposed solution

# Auto-generated by Granted (https://granted.dev). DO NOT EDIT.
# Manual edits to this section will be overwritten.
# To stop syncing and remove this section, run 'granted registry remove'.
# [granted_registry_start XXX]

[profile XXX]
...

# [granted_registry_end XXX]

Open to any discussion or approach to avoid these warnings.

Thanks in advance 😄 .