Backport add Rake task to show token expiration info
What does this MR do and why?
This is a backport for release 16-5-stable-ee
for this script be provided in earlier release. Admin can update a PAT expiry date using this script
Related MR - !157855 (merged)
Related Issue - gitlab-org/release/tasks#11508 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. -
The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes). -
This MR has a severity label assigned (if applicable). -
Set the milestone of the merge request to match the target backport branch version. -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:package-and-test-ee
job has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releases
Slack channel (internal only).
Merge request reports
Activity
assigned to @sgarg_gitlab
added devopsgovern groupauthentication sectionsec typefeature labels
added backend typebug labels and removed typefeature label
- Resolved by Smriti Garg
- Resolved by Smriti Garg
- Resolved by Smriti Garg
- Resolved by Smriti Garg
- Resolved by Smriti Garg
- Resolved by Smriti Garg
- Resolved by Smriti Garg
3 Warnings There were no new or modified SaaS feature YAML files detected in this MR. For guidance on when to use a SaaS feature, please see the SaaS feature documentation.
Backporting to older releases requires an exception request process The e2e:package-and-test-ee
job needs to succeed or have approval from a Software Engineer in Test.
Read the "QA e2e:package-and-test-ee" section for more details.1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/administration/raketasks/tokens/index.md
(Link to current live version) -
doc/raketasks/index.md
(Link to current live version) -
doc/security/token_overview.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend @srajadas
(UTC-7, 12.5 hours behind
@sgarg_gitlab
)@dskim_gitlab
(UTC+10, 4.5 hours ahead of
@sgarg_gitlab
)Please check reviewer's status!
Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
Rubygems
This merge request adds, or changes a Rubygems dependency. Please review the Gemfile guidelines.
QA
e2e:package-and-test-ee
@sgarg_gitlab, the
package-and-test
job must complete before merging this merge request.*If there are failures on the
package-and-test
pipeline, ping your team's associated Software Engineer in Test (SET) to confirm the failures are unrelated to the merge request. If there's no SET assigned, ask for assistance on the#quality
Slack channel.If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
mentioned in issue gitlab-org/release/tasks#11508 (closed)
- A deleted user
added database label
Allure report
allure-report-publisher
generated test report!e2e-package-and-test:
test report for dba13b32expand test summary
+-----------------------------------------------------------------------+ | suites summary | +------------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +------------------+--------+--------+---------+-------+-------+--------+ | Create | 523 | 0 | 115 | 80 | 638 | ❗ | | Govern | 298 | 0 | 9 | 12 | 307 | ❗ | | Systems | 8 | 0 | 0 | 0 | 8 | ✅ | | Package | 169 | 0 | 72 | 36 | 241 | ❗ | | Growth | 0 | 0 | 6 | 0 | 6 | ➖ | | Manage | 39 | 1 | 10 | 5 | 50 | ❌ | | Plan | 235 | 0 | 16 | 0 | 251 | ✅ | | GitLab Metrics | 2 | 0 | 1 | 0 | 3 | ✅ | | Data Stores | 110 | 0 | 6 | 0 | 116 | ✅ | | Analytics | 7 | 0 | 0 | 0 | 7 | ✅ | | Fulfillment | 8 | 0 | 69 | 0 | 77 | ✅ | | Monitor | 28 | 0 | 7 | 0 | 35 | ✅ | | Verify | 147 | 0 | 18 | 3 | 165 | ❗ | | Release | 15 | 0 | 3 | 0 | 18 | ✅ | | Configure | 1 | 0 | 9 | 0 | 10 | ✅ | | Secure | 6 | 0 | 3 | 0 | 9 | ✅ | | ModelOps | 0 | 0 | 6 | 0 | 6 | ➖ | | Framework sanity | 0 | 0 | 3 | 0 | 3 | ➖ | +------------------+--------+--------+---------+-------+-------+--------+ | Total | 1596 | 1 | 353 | 136 | 1950 | ❌ | +------------------+--------+--------+---------+-------+-------+--------+