-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create service accounts in EGI Check-in #664
base: main
Are you sure you want to change the base?
Conversation
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would first describe what a service account is and why it would be used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just added a brief intro, please check
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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