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
> Please read through [the code of conduct](https://github.com/common-fate/granted/blob/main/CODE_OF_CONDUCT.md), and check for both existing [Discussions](https://github.com/common-fate/granted/discussions?discussions_q=) and [Issues](https://github.com/common-fate/granted/issues?q=sort%3Areactions-desc) prior to opening a new Discussion.
8
+
- type: markdown
9
+
attributes:
10
+
value: "# Issue Details"
11
+
- type: textarea
12
+
attributes:
13
+
label: Issue Description
14
+
description: |
15
+
Provide a detailed description of the issue. Include relevant information, such as:
16
+
- The feature or configuration option you encounter the issue with.
17
+
- Terminal logs, screenshots, screen recordings, or other supporting media (as needed).
18
+
- If this is a regression of an existing issue that was closed or resolved, please include the previous item reference (Discussion, Issue, PR, commit) in your description.
19
+
placeholder: |
20
+
When using `assume` to get AWS credentials for a profile, I try to use the --profile flag but receive an error: "Token has expired and refresh failed". The same command works fine when I assume the role directly without the --profile flag.
21
+
validations:
22
+
required: true
23
+
- type: textarea
24
+
attributes:
25
+
label: Expected Behavior
26
+
description: |
27
+
Describe how you expect Granted to behave in this situation. Include any relevant documentation links.
28
+
placeholder: |
29
+
AWS credentials are successfully loaded for the specified profile and AWS commands work correctly.
30
+
validations:
31
+
required: true
32
+
- type: textarea
33
+
attributes:
34
+
label: Actual Behavior
35
+
description: |
36
+
Describe how Granted actually behaves in this situation. If it is not immediately obvious how the actual behavior differs from the expected behavior described above, please be sure to mention the deviation specifically.
37
+
placeholder: |
38
+
An error is received: "Token has expired and refresh failed" when using the --profile flag.
39
+
validations:
40
+
required: true
41
+
- type: textarea
42
+
attributes:
43
+
label: Reproduction Steps
44
+
description: |
45
+
Provide a detailed set of step-by-step instructions for reproducing this issue.
46
+
placeholder: |
47
+
1. Create a script that uses `aws s3 ls --profile codev`.
48
+
2. Run `assume codev` to get credentials.
49
+
3. Execute the script.
50
+
4. Observe the token expiration error.
51
+
validations:
52
+
required: true
53
+
- type: textarea
54
+
attributes:
55
+
label: Granted Logs
56
+
description: |
57
+
Provide any captured Granted logs or stacktraces during your issue reproduction in this field. You can enable debug logging by setting the `GRANTED_LOG=debug` environment variable before running Granted commands.
58
+
render: text
59
+
- type: textarea
60
+
attributes:
61
+
label: Granted Version
62
+
description: Paste the output of `granted --version` here.
63
+
placeholder: |
64
+
Granted version: 0.37.0
65
+
render: text
66
+
validations:
67
+
required: true
68
+
- type: input
69
+
attributes:
70
+
label: OS Version Information
71
+
description: |
72
+
Please tell us what operating system (name and version) you are using.
73
+
placeholder: Ubuntu 24.04.1 (Noble Numbat)
74
+
validations:
75
+
required: true
76
+
- type: textarea
77
+
attributes:
78
+
label: Minimal Granted & AWS Config Configuration
79
+
description: |
80
+
Please provide the **minimum** configuration needed to reproduce this issue. Relevant configuration files are `~/.aws/config` and `~/.granted/config`. If you can still reproduce the issue with one of the lines removed, do not include that line. If and **only** if you are not able to determine this, paste the contents of your configuration file here. Please redact any account IDs or ARNs in your answer.
81
+
placeholder: |
82
+
[profile codev]
83
+
sso_start_url = https://myorg.awsapps.com/start
84
+
sso_region = us-east-1
85
+
sso_account_id = 123456789012
86
+
sso_role_name = DeveloperAccess
87
+
region = eu-north-1
88
+
render: ini
89
+
validations:
90
+
required: true
91
+
- type: textarea
92
+
attributes:
93
+
label: Additional Relevant Configuration
94
+
description: |
95
+
If your issue involves other programs, tools, or applications in addition to Granted (e.g. AWS CLI, SSO configurations, shell scripts, etc.), please provide the minimum configuration and versions needed for all relevant programs to reproduce the issue here.
96
+
placeholder: |
97
+
#### `~/.aws/credentials`
98
+
```
99
+
[default]
100
+
aws_access_key_id = AKIAEXAMPLE
101
+
aws_secret_access_key = secret
102
+
```
103
+
104
+
#### `assume` shell script
105
+
```bash
106
+
#!/bin/bash
107
+
aws s3 ls --profile codev
108
+
```
109
+
validations:
110
+
required: false
111
+
- type: markdown
112
+
attributes:
113
+
value: |
114
+
# User Acknowledgements
115
+
> [!TIP]
116
+
> Use these links to review the existing Granted [Discussions](https://github.com/common-fate/granted/discussions?discussions_q=) and [Issues](https://github.com/common-fate/granted/issues?q=sort%3Areactions-desc).
117
+
- type: checkboxes
118
+
attributes:
119
+
label: "I acknowledge that:"
120
+
options:
121
+
- label: I have reviewed the FAQ and confirm that my issue is NOT among them.
122
+
required: true
123
+
- label: I have searched the Granted repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
124
+
required: true
125
+
- label: I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (` ``` `) on separate lines.
0 commit comments