{"version":"2.1.247","anchor":"aws-auth-refresh-accepts-a-structured-command","canonical_anchor":"aws-auth-refresh-accepts-a-structured-command","heading":"AWS auth refresh accepts a structured command","tier":"use","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/aws-auth-refresh-accepts-a-structured-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### AWS auth refresh accepts a structured command\n\nawsAuthRefresh now accepts a structured file, args and env form so no shell is involved.\n\n**What**\n\nThe `awsAuthRefresh` setting, which runs a command to refresh AWS credentials, now takes either the old shell string or a structured `{file, args, env}` form that avoids a shell.\n\n**Details**\n\n- For the structured form the executable is resolved and rejected unless it sits in a safe directory: \"AWS auth refresh: executable not found in a safe directory\".\n- `.cmd` and `.bat` targets are quoted and run through a shell.\n- Failure and timeout messages now name the command that was run instead of pointing at the settings key.\n\n**Evidence**\n\n`AWS auth refresh: executable not found in a safe directory`\n\n- Area: Auth\n- Names: `awsAuthRefresh`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}