Skip to content
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

docs(updates): update precommit and fix whitespace, comments/updates/… #289

Merged
merged 12 commits into from
Dec 13, 2024

Conversation

Avantol13
Copy link
Contributor

@Avantol13 Avantol13 commented Dec 9, 2024

…suggestions throughout

I only truly reviewed gen3/docs/gen3-resources. All other changes are automated by precommit to fix whitespace.

Link to JIRA ticket if there is one:

New Features

Breaking Changes

Bug Fixes

Improvements

  • update precommit and fix whitespace
  • various grammar updates
  • various comments/suggestions
  • various reformatting/rewording

Dependency updates

Deployment changes

@Avantol13 Avantol13 requested review from a team as code owners December 9, 2024 16:55
Avantol13 and others added 7 commits December 9, 2024 10:57
formatting update
* Update using-api.md

change the code so users are not told to paste their API key into their code, but instead reference the file

* Update using-api.md

update environment reference to https://gen3.datacommons.io
The Gen3 workspace token service acts as an OIDC client which acts on behalf of users to request refresh tokens from Fence. This happens when a user logs into a workspace from the browser. WTS then stores the refresh token for that user, and manages access tokens and refresh tokens for workers that belong to specific users in the workspace.
A simple list of most relevant microservices are included below. For a description of each service and links to their respective repositories please visit the [Developer's Guide][Microservices].

* Aggregated Metadata Service (AggMDS)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't a separate service, so I wouldn't include it in this list. This case is actually what makes it difficult to describe our offerings as services rather than APIs. There's only 1 service, the MDS, which exposes the MDS API and the aggMDS API.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re: this -- although it's technically not a separate service, i think we think about and talk about it as though it is a separate service. especially because they have the 2 endpoints. maybe we can talk more about that in a asterisky way -- but it feels like something that should be treated differently, even if technically it isn't

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you be comfortable with it if we explained a bit more that ack-chu-ally, it's all part of the metadata service -- but it is kinda special, and has its own endpoint?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Notably -- arguing more for you -- there is only one Helm chart (called metadata) that covers both of these

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I would ask whether everything an operator might need to know is located in the MDS repo. I do see an AggMDS link within that repo: https://github.com/uc-cdis/metadata-service/blob/865f83015f7a30a35b58d00054a1950eb0ecb48b/docs/agg_mds.md

If, however, the AggMDS repo (https://github.com/uc-cdis/agg-metadata) contains documentation that is useful to someone creating a mesh then we should link to it separately in some way.

In other words, my goal for listing out services is to make sure operators or developers who need to have access to repo-specific documentation can find what they need.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upon further discussion, we will remove the AggMDS repo since the code governing the AggMDS is actually all within the MDS repo.

@@ -49,7 +46,7 @@ import json, requests
api = "https://gen3.datacommons.io"
key_file = "/put_path_to/credentials.json"

# Read the key from the file and
# Read the key from the file and
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

incomplete sentence

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

@@ -5,7 +5,6 @@ Gen3 features and functionality are enabled by independent and modular microserv
While the average user does not need to know the details and names of each microservice, if you are interested in adding new features or modifying your Gen3 system in some way it may be helpful to have a deeper understanding of a specific microservice. We have included brief descriptions below along with a link to their documentation in GitHub.

## [Aggregated Metadata Service (AggMDS)][aggmds github]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still worry about having this separated from the MDS. At least we should put them together

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AggMDS was consolidated under MDS

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the authorization section, but it would be good for you to review again.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I have addressed most of your comments although I left the potentially duplicated information for the Query Page

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the description of the microservices in the glossary to avoid the problem of the content getting out of sync with the developer's guide

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have mentioned this workflow (discovery -> access approval -> exploration), but with the caveat that not every system will have a discovery page so it is not universal. I also mentioned that the SDK has a CLI.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change to API instructions were made

The Gen3 workspace token service acts as an OIDC client which acts on behalf of users to request refresh tokens from Fence. This happens when a user logs into a workspace from the browser. WTS then stores the refresh token for that user, and manages access tokens and refresh tokens for workers that belong to specific users in the workspace.
A simple list of most relevant microservices are included below. For a description of each service and links to their respective repositories please visit the [Developer's Guide][Microservices].

* Aggregated Metadata Service (AggMDS)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I would ask whether everything an operator might need to know is located in the MDS repo. I do see an AggMDS link within that repo: https://github.com/uc-cdis/metadata-service/blob/865f83015f7a30a35b58d00054a1950eb0ecb48b/docs/agg_mds.md

If, however, the AggMDS repo (https://github.com/uc-cdis/agg-metadata) contains documentation that is useful to someone creating a mesh then we should link to it separately in some way.

In other words, my goal for listing out services is to make sure operators or developers who need to have access to repo-specific documentation can find what they need.

The Gen3 workspace token service acts as an OIDC client which acts on behalf of users to request refresh tokens from Fence. This happens when a user logs into a workspace from the browser. WTS then stores the refresh token for that user, and manages access tokens and refresh tokens for workers that belong to specific users in the workspace.
A simple list of most relevant microservices are included below. For a description of each service and links to their respective repositories please visit the [Developer's Guide][Microservices].

* Aggregated Metadata Service (AggMDS)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upon further discussion, we will remove the AggMDS repo since the code governing the AggMDS is actually all within the MDS repo.

@michaelfitzo michaelfitzo merged commit df04533 into master Dec 13, 2024
2 checks passed
@michaelfitzo michaelfitzo deleted the docs/updates branch December 13, 2024 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants