JustinGrote / JustinGrote/JAz.PIM
DateTime Properties Are Not Localized
- Dominant language
- PowerShell
- Stars
- 48
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The confirmation for activated roles displays the `StartDateTime` and `EndDateTime` properties as UTC instead of local time. This makes it unclear what the actual start/end time is.
```PowerShell
PS > Get-Date; Get-Date -AsUTC
Wednesday, July 27, 2022 1:23:00 PM
Wednesday, July 27, 2022 5:23:00 PM
PS > Enable-ADRole 'Global Reader (LJnv8vs6uUa3z6Em7nTEUZY-Uygeo0pJj_wBT3Lkhj8-1-e)' -Justification 'foo' -Hours 1
Action Status PrincipalDisplayName RoleName Scope StartDateTime EndDateTime
------ ------ -------------------- -------- ----- ------------- -----------
selfActivate Provisioned bmkaiser Global Reader Directory 7/27/2022 5:23:30 PM 7/27/2022 6:23:00 PM
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the `Enable-ADRole ... -Justification 'foo' -Hours 1` command and comparing its confirmation output with `Get-Date` and `Get-Date -AsUTC`. Trace how the confirmation formats `StartDateTime` and `EndDateTime`; done when both values display in local time rather than UTC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, localization
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100