[v2] Add ability to set properties in subsections by kdaily · Pull Request #10109 · aws/aws-cli

kdaily · 2026-02-26T20:19:28Z

This change adds new parameters to the aws configure set command to specify a sub-section for setting a property. These parameters are analogous to the existing --profile parameter. A parameter will be added for each sub-section type and take a value of the subsection name. Following is the generic pattern for the aws configure set command:

aws configure set
  --<sub-section-type> <sub-section-name> \
  <property> <value>

For example, the following command should set the property sso_region to the value us-west-2 in the sso-session sub-section named my-sso-session:

aws configure set
  --sso-session my-sso-session \
  sso_region us-west-2

Following is an example setting a nested property in a sub-section:

aws configure set \
  --<sub-section-type> <sub-section-name> \
  <nested-section>.<property> value

The only sub-section types allowed are services and sso-session.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

awscli/customizations/configure/__init__.py

This change adds new parameters to the `aws configure set`` command to specify a sub-section for setting a property. These parameters are analogous to the existing `--profile` parameter. A parameter will be added for each sub-section type and take a value of the subsection name. Following is the generic pattern for the `aws configure set` command: ``` aws configure set --<sub-section-type> <sub-section-name> \ <property> <value> ``` For example, the following command should set the property `sso_region` to the value `us-west-2` in the `sso-session` sub-section named `my-sso-session`: ``` aws configure set --sso-session my-sso-session \ sso_region us-west-2 ``` Following is an example setting a nested property in a sub-section: ``` aws configure set \ --<sub-section-type> <sub-section-name> \ <nested-section>.<property> value ``` The only sub-section types allowed are `services` and `sso-session`.

ashovlin

Can we also add a new example or two?

ashovlin · 2026-03-04T19:15:04Z

awscli/customizations/configure/set.py

        },
+        {
+            'name': 'sso-session',
+            'help_text': 'The name of the SSO session sub-section to configure.',


This reads odd via aws configure set help. We might need to make this help_text more generic if there isn't a way to separate the two new options better?

OPTIONS varname (string) The name of the config value to set. value (string) The value to set. --sso-session | --services (string) The name of the SSO session sub-section to configure.

Ah, I see the issue. The intention was to highlight the mutual exclusivity of the parameter. I think updating the wording is probably the best resolution, but I could split them as well and then rely on the implementation erorring if more than one is provided:

OPTIONS varname (string) The name of the config value to set. value (string) The value to set. --services (string) The name of the services sub-section to configure. --sso-session (string) The name of the SSO session sub-section to configure.

Fixed in 1271886. I kept them in the same parameter group and updated the wording.

ashovlin · 2026-03-04T19:40:51Z

awscli/customizations/configure/set.py

+            if hasattr(args, section_properties['param_name']):
+                param_value = getattr(args, section_properties['param_name'])
+                if param_value is not None:
+                    if not re.match(r"[\w\d_\-/.%@:\+]+", param_value):


This is different than the regex in the internal spec [A-Za-z0-9_\-/.%@:\+]+ - is accepting unicode via \w okay?

It doesn't look like aws configure sso validates this, just RequiredInputValidator. Is there a chance someone has already configured something invalid? Though since this is brand new workflow, I think it's okay to start by matching the spec, and relaxing if needed.

Can you add a comment explaining what we're validating here? By the time I got to the regex, I wasn't sure what param_value was anymore.

This is different than the regex in the internal spec [A-Za-z0-9_-/.%@:+]+ - is accepting unicode via \w okay?

We currently accept profile and SSO session names with unicode.

Can you add a comment explaining what we're validating here? By the time I got to the regex, I wasn't sure what param_value was anymore.

Yep, will update.

Updated in 827edb3

ashovlin · 2026-03-04T19:43:47Z

awscli/customizations/configure/set.py

+        if '.' in varname:
+            parts = varname.split('.')
+            if len(parts) > 2:
+                return 0


Could we add a comment explaining this validation?

And if it's what I assume, that we don't have any valid properties deeper than --services <name> s3.endpoint_url, should we raise a validation error rather than silently not writing?

Agree we could raise validation error. The current implementation silently sets the parameter at the first level. For example:

aws --profile brandbrandnew configure set foo.bar.baz "qux"

Results in:

[profile brandbrandnew] foo = qux

Raising error now, fixed in c1a63ba

Remove the mapping between the subsection type and the parameter name. This is a transformation between '-' separated and '_' separated, so use a utility method to do this. Rename parameters to improve understanding of the code.

Only one level of nested properties is supported, e.g. 'aaa.bbb'. If the user supplies more than that (.aaa.bbb.ccc') an error is raised.

kdaily · 2026-03-16T20:55:56Z

Can we also add a new example or two?

Added in be92fb1

kdaily commented Feb 26, 2026

View reviewed changes

awscli/customizations/configure/__init__.py Outdated Show resolved Hide resolved

kdaily commented Feb 26, 2026

View reviewed changes

awscli/customizations/configure/__init__.py Outdated Show resolved Hide resolved

kdaily force-pushed the add-configure-set-subsections branch 2 times, most recently from 4aa4c78 to 7eddac8 Compare February 26, 2026 22:41

kdaily marked this pull request as draft February 27, 2026 17:26

kdaily force-pushed the add-configure-set-subsections branch from 7eddac8 to dc2611d Compare February 27, 2026 17:49

kdaily mentioned this pull request Feb 27, 2026

[v2] Add ability to get values from properties in subsections #10112

Open

kdaily force-pushed the add-configure-set-subsections branch from dc2611d to 3360369 Compare February 27, 2026 17:56

kdaily marked this pull request as ready for review February 27, 2026 18:08

AndrewAsseily requested a review from ashovlin March 2, 2026 19:44

ashovlin reviewed Mar 4, 2026

View reviewed changes

kdaily added 2 commits March 16, 2026 10:53

Improved readability of subsection valdiation

827edb3

Remove the mapping between the subsection type and the parameter name. This is a transformation between '-' separated and '_' separated, so use a utility method to do this. Rename parameters to improve understanding of the code.

Return error if configuring deeply nested properties

c1a63ba

Only one level of nested properties is supported, e.g. 'aaa.bbb'. If the user supplies more than that (.aaa.bbb.ccc') an error is raised.

kdaily force-pushed the add-configure-set-subsections branch from 2f42777 to a1d5d81 Compare March 16, 2026 20:46

Update documentation string for sub-section name parameter

1271886

kdaily force-pushed the add-configure-set-subsections branch from a1d5d81 to 1271886 Compare March 16, 2026 20:48

Added examples

be92fb1

kdaily requested a review from ashovlin March 16, 2026 20:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[v2] Add ability to set properties in subsections#10109

[v2] Add ability to set properties in subsections#10109
kdaily wants to merge 5 commits intofeature-configure-subsectionsfrom
add-configure-set-subsections

kdaily commented Feb 26, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

ashovlin left a comment

Uh oh!

ashovlin Mar 4, 2026

Uh oh!

kdaily Mar 12, 2026

Uh oh!

kdaily Mar 16, 2026 •

edited

Loading

Uh oh!

ashovlin Mar 4, 2026

Uh oh!

kdaily Mar 12, 2026

Uh oh!

kdaily Mar 16, 2026

Uh oh!

ashovlin Mar 4, 2026

Uh oh!

kdaily Mar 12, 2026

Uh oh!

kdaily Mar 16, 2026

Uh oh!

kdaily commented Mar 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

kdaily commented Feb 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ashovlin left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kdaily Mar 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kdaily commented Mar 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

kdaily commented Feb 26, 2026 •

edited

Loading

kdaily Mar 16, 2026 •

edited

Loading