-
Notifications
You must be signed in to change notification settings - Fork 276
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
Assistance Required for max_instances Configuration Issue during Deployment #2663
Comments
The |
Thank you @jianglai, I successfully deployed. I am having issues using both the UI and CLI. Steps I followed:
ls java/google/registry/tools/resources/client_secret.json
Issues:
|
The CLI is at |
The CLI works fine, but regarding the UI, the documentation mentions the following URL: https://[project-id].appspot.com/registrar However, when I try to access it, I get redirected to: https://[project-id].appspot.com/console In the logs, I can see that the request to |
The document is outdated. |
Thanks a lot 1. OAuth Consent Screen Configuration
2. Modified Files
# Add environment-specific configuration here.
gcpProject:
projectId: [project-id]
toolsServiceUrl: https://tools-dot-[project-id].appspot.com # Insert your project ID
isLocal: false # Causes saved credentials to be used
gSuite:
domainName: # Your G Suite domain name
adminAccountAccountEmailAddress: # An admin login for your G Suite account
# Configuration options relevant to the "nomulus" registry tool
registryTool:
# OAuth client ID used by the tool
clientId: 1096782583788- .apps.googleusercontent.com
# OAuth client secret used by the tool
clientSecret: GOCSPX-
auth:
oauthClientId: 1096782583788- .apps.googleusercontent.com
cloudSql:
# JDBC URL for the Cloud SQL database
jdbcUrl: jdbc:postgresql://localhost
# This name is used by Cloud SQL when connecting to the database
instanceConnectionName: [project-id]:asia-south1:nomulus-db IssuesCLIWhen running: nomulus -e alpha login
I get the following output: Feb 05, 2025 3:01:19 PM google.registry.util.YamlUtils mergeYaml
WARNING: Ignoring empty environment configuration YAML file.
Please open the following address in your browser:
https://accounts.google.com/o/oauth2/auth?client_id=YOUR_CLIENT_ID&redirect_uri=http://localhost:39849/Callback&response_type=code&scope=https://www.googleapis.com/auth/cloud-platform%20https://www.googleapis.com/auth/appengine.apis%20https://www.googleapis.com/auth/userinfo.email%20https://www.googleapis.com/auth/appengine.admin The login URL displays UII have activated and configured IAP, added my user with the IAP-secured Web App User role, and successfully authenticated. However, I am encountering a 404 Not Found error, as if nothing has been deployed. I navigated to "serve": {
"options": {
"host": "0.0.0.0"
}
} After running However, when accessing the application via |
For the UI, it should be deployed when you run |
Please, I used an outdated docuement # Build the codebase
./nom_build build --environment=alpha --info --stacktrace
./nom_build :db:flywayMigrate
# Deploy App
./nom_build appengineDeploy --environment=alpha --info --stacktrace
May I replace ./nom_build to ./gradlew ? |
I personally use |
Thank you so much @jianglai |
Hi @jianglai, |
Hello,
I hope this message finds you well. I'm currently working on deploying multiple services within my Nomulus project, specifically
backend
andbsa
, but I'm encountering a recurring issue related to themax_instances
parameter in theapp.yaml
configuration files.Issue Description:
During deployment, I'm receiving the following error message:
Despite updating the
max_instances
value to 25 in theapp.yaml
files forbackend
andbsa
, it seems to reset to 100 during the deployment process. I have attempted to set the correct value in various configuration files includingnomulus-config-alpha.yaml
, but the issue persists.Steps Taken:
Verified and updated
app.yaml
files forbackend
andbsa
:Observations:
max_instances
parameter resets to 100 during the deployment, causing the error.app.yaml
settings.Request for Assistance: I would greatly appreciate any guidance on where else this configuration might be set or any steps I might be missing to ensure the correct
max_instances
value is applied during deployment.Thank you in advance for your help!
The text was updated successfully, but these errors were encountered: