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

nvidia-input #589

Merged
merged 3 commits into from
Dec 17, 2023
Merged

nvidia-input #589

merged 3 commits into from
Dec 17, 2023

Conversation

yarongol
Copy link
Collaborator

No description provided.

@@ -7,7 +7,7 @@ The following document explains how to authenticate with Run:ai APIs.
Run:ai APIs are accessed using _bearer tokens_. A token can be obtained in several ways:

* When logging into the Run:ai user interface, you enter an email and password (or authenticated via single sign-on) which are used to obtain a token.
* When using the Run:ai command-line, you use a Kubernetes profile and are authenticated by pre-running `runai login` (or oc login with OpenShift). The command attachs a token to the profile and allows you access to Run:ai functionality.
* When using the Run:ai command-line, you use a Kubernetes profile and are authenticated by pre-running `runai login` (or oc login with OpenShift). The command attaches a token to the profile and allows you access to Run:ai functionality.
Copy link
Contributor

Choose a reason for hiding this comment

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

[markdownlint] reported by reviewdog 🐶
MD013/line-length Line length [Expected: 80; Actual: 238]

url = "https://" + COMPANY_URL + "/auth/realms/" + \
COMPANY_REALM + "/protocol/openid-connect/token"

payload = 'grant_type=client_credentials&scope=openid&response_type=id_token&client_id=' + \
Copy link
Contributor

Choose a reason for hiding this comment

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

[markdownlint] reported by reviewdog 🐶
MD013/line-length Line length [Expected: 80; Actual: 100]

j = json.loads(response.text)
return j["access_token"]
else:
print(json.dumps(json.loads(response.text), sort_keys=True, indent=4, separators=(",", ": ")))
Copy link
Contributor

Choose a reason for hiding this comment

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

[markdownlint] reported by reviewdog 🐶
MD013/line-length Line length [Expected: 80; Actual: 106]

docs/developer/rest-auth.md Outdated Show resolved Hide resolved
docs/developer/rest-auth.md Outdated Show resolved Hide resolved
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@@ -7,7 +7,7 @@ The following document explains how to authenticate with Run:ai APIs.
Run:ai APIs are accessed using _bearer tokens_. A token can be obtained in several ways:

* When logging into the Run:ai user interface, you enter an email and password (or authenticated via single sign-on) which are used to obtain a token.
* When using the Run:ai command-line, you use a Kubernetes profile and are authenticated by pre-running `runai login` (or oc login with OpenShift). The command attachs a token to the profile and allows you access to Run:ai functionality.
* When using the Run:ai command-line, you use a Kubernetes profile and are authenticated by pre-running `runai login` (or oc login with OpenShift). The command attaches a token to the profile and allows you access to Run:ai functionality.
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 [vale] reported by reviewdog 🐶
[Microsoft.Passive] 'are authenticated' looks like passive voice.

@@ -7,7 +7,7 @@ The following document explains how to authenticate with Run:ai APIs.
Run:ai APIs are accessed using _bearer tokens_. A token can be obtained in several ways:

* When logging into the Run:ai user interface, you enter an email and password (or authenticated via single sign-on) which are used to obtain a token.
* When using the Run:ai command-line, you use a Kubernetes profile and are authenticated by pre-running `runai login` (or oc login with OpenShift). The command attachs a token to the profile and allows you access to Run:ai functionality.
* When using the Run:ai command-line, you use a Kubernetes profile and are authenticated by pre-running `runai login` (or oc login with OpenShift). The command attaches a token to the profile and allows you access to Run:ai functionality.
Copy link
Contributor

Choose a reason for hiding this comment

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

🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'oc'?

@@ -7,7 +7,7 @@ The following document explains how to authenticate with Run:ai APIs.
Run:ai APIs are accessed using _bearer tokens_. A token can be obtained in several ways:

* When logging into the Run:ai user interface, you enter an email and password (or authenticated via single sign-on) which are used to obtain a token.
* When using the Run:ai command-line, you use a Kubernetes profile and are authenticated by pre-running `runai login` (or oc login with OpenShift). The command attachs a token to the profile and allows you access to Run:ai functionality.
* When using the Run:ai command-line, you use a Kubernetes profile and are authenticated by pre-running `runai login` (or oc login with OpenShift). The command attaches a token to the profile and allows you access to Run:ai functionality.
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 [vale] reported by reviewdog 🐶
[Microsoft.Vocab] Verify your use of 'allows' with the A-Z word list.

print(json.dumps(json.loads(response.text), sort_keys=True, indent=4, separators=(",", ": ")))
return
import requests
import json
Copy link
Contributor

Choose a reason for hiding this comment

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

🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'json'?

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@jasonnovichRunAI jasonnovichRunAI merged commit 783b422 into v2.15 Dec 17, 2023
1 of 2 checks passed
jasonnovichRunAI added a commit to jasonnovichRunAI/docs that referenced this pull request Dec 17, 2023
jasonnovichRunAI added a commit that referenced this pull request Dec 17, 2023
Merge pull request #589 from run-ai/auth-python-revamp
@yarongol yarongol deleted the auth-python-revamp branch August 13, 2024 08:07
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.

2 participants