Create service accounts in EGI Check-in#664
Create service accounts in EGI Check-in#664sebastian-luna-valero wants to merge 4 commits intomainfrom
Conversation
sebastian-luna-valero
added
the
safe for preview
This comment has been minimized.
This comment has been minimized.
Documentation preview deployed!Available at https://docs.egi.eu/documentation/664 |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/664 |
sebastian-luna-valero
requested review from
andrea-manzi,
enolfc,
glarocca,
gwarf and
vardizzo-lab
as code owners
brucellino
left a comment
brucellino
left a comment
There was a problem hiding this comment.
Provide some context of who would want a service account, what it's used for typically.
| description: > | ||
| Create a Service Account using EGI Check-in | ||
| --- | ||
|
|
There was a problem hiding this comment.
I would first describe what a service account is and why it would be used.
There was a problem hiding this comment.
I just added a brief intro, please check
There was a problem hiding this comment.
Thanks, looks better! We still leave too much room for confusion though. We should provide specific scenarios - a concrete example (maybe the one in the business requirement).
Documentation preview deployed!Available at https://docs.egi.eu/documentation/664 |
|
This PR is related to the request tracked inthe ticket EGIREQ-156 and will follow the evaluation and resolution process. |
|
@sebastian-luna-valero Can we put this into draft while we're still reviewing it just to avoid accidentally merging? |
| description: > | ||
| Create a Service Account using EGI Check-in | ||
| --- | ||
|
|
There was a problem hiding this comment.
Thanks, looks better! We still leave too much room for confusion though. We should provide specific scenarios - a concrete example (maybe the one in the business requirement).
| description: > | ||
| Create a Service Account using EGI Check-in | ||
| --- | ||
|
|
There was a problem hiding this comment.
This is currently a deprecated feature. We can document it, but it should explicitly be annotated as deprecated since we do not support it in general availability. @sebastian-luna-valero can you see if there is a Docusaurus feature which allows us to add such a warning or admonition to make it clear to readers that this feature is deprecated and unsupported?
There was a problem hiding this comment.
Shall we better wait for the resolution of EGIREQ-156 to move forward? If the feature is deprecated and unsupported, and the plan is to stop there, I would not even add this new page.
🦙 MegaLinter status:
|
| Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
|---|---|---|---|---|---|
| ✅ EDITORCONFIG | editorconfig-checker | 3 | 0 | 0.01s | |
| markdownlint | 2 | 1 | 0.27s | ||
| ✅ MARKDOWN | markdown-link-check | 2 | 0 | 10.2s | |
| ✅ MARKDOWN | markdown-table-formatter | 2 | 0 | 0.21s | |
| ✅ REPOSITORY | checkov | yes | no | 16.25s | |
| ✅ REPOSITORY | gitleaks | yes | no | 0.06s | |
| ✅ REPOSITORY | git_diff | yes | no | 0.05s | |
| ✅ REPOSITORY | secretlint | yes | no | 2.71s | |
| ✅ REPOSITORY | trivy-sbom | yes | no | 0.24s | |
| ✅ SPELL | lychee | 3 | 0 | 2.58s |
See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by
Documentation preview deployed!Available at https://docs.egi.eu/documentation/664 |
Documentation preview deployed!Available at https://docs.egi.eu/documentation/664 |
|
@sebastian-luna-valero bump -- is this PR still in progresS? |
|
Yes, waiting for progress on the EGIREQ-156 internal ticket as described above. |
4 participants
Summary
Add a page on how to create service accounts, following discussion via:
https://ggus.eu/?mode=ticket_info&ticket_id=161888#update#10
Related issue :
Business Requirement: EGIREQ-156