aws / aws/aws-toolkit-azure-devops
AWS Service Connector
- Dominant language
- TypeScript
- Stars
- 258
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Description
Whenever you experience an issue with the AWS Service Connector there is no possible way to open a ticket with AWS as they claim they didn't write the AWS Service Connector.
We have experienced the Session Token (optional) bug many times and the fix is when resetting Secret Access Key or creating a new Access Key ID is to enter a space in the Session Token (optional) field, then backspace before saving.
There really needs to be better support from AWS and Azure DevOps when there is an issue.
Contributor guide
Research direction
Start by reproducing the Session Token (optional) behavior in the AWS Service Connector when resetting the Secret Access Key or creating a new Access Key ID. Trace the connector's Azure DevOps configuration path and document a failing test or precise reproduction; done means the token saves without the space/backspace workaround and the support ownership is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100