You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix:making role session tagging optional
* test:improve test coverage
Add test to cover error thrown if access key exists and no secret key provided
* docs: Update README.md
Add details about skipping session tagging during role assumption
Co-authored-by: KeifferCulbreth <[email protected]>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.md
+8
Original file line number
Diff line number
Diff line change
@@ -157,6 +157,14 @@ The session will have the name "GitHubActions" and be tagged with the following
157
157
158
158
_Note: all tag values must conform to [the requirements](https://docs.aws.amazon.com/STS/latest/APIReference/API_Tag.html). Particularly, `GITHUB_WORKFLOW` will be truncated if it's too long. If `GITHUB_ACTOR` or `GITHUB_WORKFLOW` contain invalid charcters, the characters will be replaced with an '*'._
159
159
160
+
The action will use session tagging by default during role assumption. You can skip this session tagging by providing `role-skip-session-tagging` as true in the action's inputs:
161
+
162
+
```yaml
163
+
uses: aws-actions/configure-aws-credentials@v1
164
+
with:
165
+
role-skip-session-tagging: true
166
+
```
167
+
160
168
## Self-Hosted Runners
161
169
162
170
If you run your GitHub Actions in a [self-hosted runner](https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners) that already has access to AWS credentials, such as an EC2 instance, then you do not need to provide IAM user access key credentials to this action.
0 commit comments