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

Change to endpoints managed rollout #576

Merged

Conversation

simonz130
Copy link

We introduce a new feature where we can specify in YAML that service configuration for Endpoints is going to be managed. This means that the service will pull latest deployed service configuration automatically, rather than requiring customer to specify specific version of service configuration.

New flag:
--rollout_strategy=managed
Previously the only way to specify a version was using the following flag:
--version=SERVICE_CONFIG_ID

@simonz130 simonz130 requested review from wmwong and jmdobry March 8, 2018 03:34
@simonz130 simonz130 added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Mar 8, 2018
```
$ gcloud endpoints services deploy api.pb api_config.yaml
...
Service Configuration [SERVICE_CONFIG_ID] uploaded for service [SERVICE_NAME]
Copy link
Contributor

Choose a reason for hiding this comment

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

This was the only place where we define what SERVICE_NAME is. Without this, users may be confused about what SERVICE_NAME is.

I think we should leave this here, even if we don't end up using SERVICE_CONFIG_ID.

@@ -44,11 +44,10 @@ $ protoc \

1. In `api_config.yaml`, replace `MY_PROJECT_ID` and `SERVICE-ACCOUNT-ID` with your Project ID and your service account's email address respectively.

1. Deploy your service's configuration to Endpoints. Take note of your service's config ID and name once the deployment completes.
1. Deploy your service's configuration to Endpoints.
Copy link
Contributor

Choose a reason for hiding this comment

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

We should still say:
Take note of your service's name once the deployment completes.

@@ -107,7 +106,7 @@ $ gcloud components install kubectl
$ gcloud container clusters get-credentials [YOUR_CLUSTER_NAME] --zone [YOUR_CLUSTER_ZONE]
```

1. Edit the `container_engine.yaml` file, and replace `GCLOUD_PROJECT`, `SERVICE_NAME`, and `SERVICE_CONFIG` with your Project ID and your Endpoints service's name and config ID respectively.
1. Edit the `container_engine.yaml` file, and replace `GCLOUD_PROJECT` and `SERVICE_NAME` with your Project ID and your Endpoints service's name.
Copy link
Contributor

Choose a reason for hiding this comment

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

Change "Project ID" -> "GCloud Project ID".
Change "Endpoints service's name" -> "service's name respectively".

This matches the instructions above.

@codecov
Copy link

codecov bot commented Apr 3, 2018

Codecov Report

Merging #576 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #576   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           1      1           
  Lines           3      3           
=====================================
  Hits            3      3

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 48c625e...8a570e3. Read the comment docs.

@simonz130
Copy link
Author

circleci timeout failure is due to functions emulator and has nothing to do with these changes.

@simonz130 simonz130 changed the title [DO NOT MERGE] Change to endpoints managed rollout Change to endpoints managed rollout Apr 3, 2018
@simonz130 simonz130 removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Apr 3, 2018
@simonz130 simonz130 merged commit 3cac032 into GoogleCloudPlatform:master Apr 3, 2018
@simonz130 simonz130 deleted the newdeploymentrollout branch April 3, 2018 22:30
ace-n pushed a commit that referenced this pull request Nov 11, 2022
ace-n pushed a commit that referenced this pull request Nov 11, 2022
ace-n pushed a commit that referenced this pull request Nov 14, 2022
ace-n pushed a commit that referenced this pull request Nov 15, 2022
ace-n pushed a commit that referenced this pull request Nov 15, 2022
ahrarmonsur pushed a commit that referenced this pull request Nov 16, 2022
ahrarmonsur pushed a commit that referenced this pull request Nov 16, 2022
ahrarmonsur pushed a commit that referenced this pull request Nov 16, 2022
ahrarmonsur pushed a commit that referenced this pull request Nov 16, 2022
ahrarmonsur pushed a commit that referenced this pull request Nov 16, 2022
ace-n pushed a commit that referenced this pull request Nov 17, 2022
ace-n pushed a commit that referenced this pull request Nov 17, 2022
ace-n pushed a commit that referenced this pull request Nov 17, 2022
ahrarmonsur pushed a commit that referenced this pull request Nov 17, 2022
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