diff --git a/content/admin/monitoring-and-managing-your-instance/configuring-clustering/rebalancing-cluster-workloads.md b/content/admin/monitoring-and-managing-your-instance/configuring-clustering/rebalancing-cluster-workloads.md index 91690d079bf3..2c2a75715b77 100644 --- a/content/admin/monitoring-and-managing-your-instance/configuring-clustering/rebalancing-cluster-workloads.md +++ b/content/admin/monitoring-and-managing-your-instance/configuring-clustering/rebalancing-cluster-workloads.md @@ -63,8 +63,7 @@ After you determine which jobs are unbalanced across your cluster's nodes, you c You can schedule rebalancing of jobs on your cluster by setting and applying configuration values for {% data variables.location.product_location %}. -> [!NOTE] -> Currently, you can only schedule reallocation of jobs for the HTTP server, `github-unicorn`. +By default, scheduled rebalancing considers all eligible jobs, including `github-unicorn` and other eligible services. You can apply a job filter with `-j`. 1. To configure automatic, hourly balancing of jobs, run the following command. diff --git a/src/github-apps/lib/config.json b/src/github-apps/lib/config.json index ccac9357558d..84c651f6580a 100644 --- a/src/github-apps/lib/config.json +++ b/src/github-apps/lib/config.json @@ -60,5 +60,5 @@ "2022-11-28" ] }, - "sha": "c66e298030d4070b70a569dcd4268b3a041b5380" + "sha": "320307e220815d528224ca891cf8a9e3c0243678" } \ No newline at end of file diff --git a/src/rest/data/fpt-2022-11-28/users.json b/src/rest/data/fpt-2022-11-28/users.json index e2ec029da94f..d7c69a661817 100644 --- a/src/rest/data/fpt-2022-11-28/users.json +++ b/src/rest/data/fpt-2022-11-28/users.json @@ -9,7 +9,7 @@ "subcategory": "users", "parameters": [], "bodyParameters": [], - "descriptionHTML": "
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
OAuth app tokens and personal access tokens (classic) need the read:user scope, or the broader user scope, for this endpoint to return the private user response. The private user response includes additional fields such as private_gists, total_private_repos, owned_private_repos, disk_usage, collaborators, and two_factor_authentication. Tokens without these scopes receive the public user response.
The private and public user response types are unrelated to the private profile setting. A token without scopes still authenticates as the token's owner, so values subject to private profile visibility, such as followers and following, may differ from an unauthenticated response.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
Lists all of your email addresses, and specifies which one is visible\nto the public.
\nOAuth app tokens and personal access tokens (classic) need the user:email scope to use this endpoint.
For enterprise-managed users, if their email is unverified, this endpoint will return a placeholder email in the format email+shortcode@domain.com instead of their actual email. This placeholder email may cause issues with some third-party apps. Once the user has verified their email address, the endpoint will return their real email.