Tariq Ibrahim
83e6d56393
|
5 years ago | |
|---|---|---|
| .. | ||
| internal | 5 years ago | |
| urlfetch | ||
| .travis.yml | 6 years ago | |
| CONTRIBUTING.md | 6 years ago | |
| LICENSE | ||
| README.md | 5 years ago | |
| appengine.go | 5 years ago | |
| appengine_vm.go | 6 years ago | |
| errors.go | ||
| go.mod | 5 years ago | |
| go.sum | 5 years ago | |
| identity.go | ||
| namespace.go | ||
| timeout.go | ||
| travis_install.sh | 6 years ago | |
| travis_test.sh | 6 years ago | |
README.md
Go App Engine packages
This repository supports the Go runtime on App Engine standard.
It provides APIs for interacting with App Engine services.
Its canonical import path is google.golang.org/appengine.
See https://cloud.google.com/appengine/docs/go/ for more information.
File issue reports and feature requests on the GitHub's issue tracker.
Upgrading an App Engine app to the flexible environment
This package does not work on App Engine flexible.
There are many differences between the App Engine standard environment and the flexible environment.
See the documentation on upgrading to the flexible environment.
Directory structure
The top level directory of this repository is the appengine package. It
contains the
basic APIs (e.g. appengine.NewContext) that apply across APIs. Specific API
packages are in subdirectories (e.g. datastore).
There is an internal subdirectory that contains service protocol buffers,
plus packages required for connectivity to make API calls. App Engine apps
should not directly import any package under internal.
Updating from legacy (import "appengine") packages
If you're currently using the bare appengine packages
(that is, not these ones, imported via google.golang.org/appengine),
then you can use the aefix tool to help automate an upgrade to these packages.
Run go get google.golang.org/appengine/cmd/aefix to install it.
1. Update import paths
The import paths for App Engine packages are now fully qualified, based at google.golang.org/appengine.
You will need to update your code to use import paths starting with that; for instance,
code importing appengine/datastore will now need to import google.golang.org/appengine/datastore.
2. Update code using deprecated, removed or modified APIs
Most App Engine services are available with exactly the same API. A few APIs were cleaned up, and there are some differences:
appengine.Contexthas been replaced with theContexttype fromgolang.org/x/net/context.- Logging methods that were on
appengine.Contextare now functions ingoogle.golang.org/appengine/log. appengine.Timeouthas been removed. Usecontext.WithTimeoutinstead.appengine.Datacenternow takes acontext.Contextargument.datastore.PropertyLoadSaverhas been simplified to use slices in place of channels.delay.Callnow returns an error.search.FieldLoadSavernow handles document metadata.urlfetch.Transportno longer has a Deadline field; set a deadline on thecontext.Contextinstead.aetestno longer declares its own Context type, and uses the standard one instead.taskqueue.QueueStatsno longer takes a maxTasks argument. That argument has been deprecated and unused for a long time.appengine.BackendHostnameandappengine.BackendInstancewere for the deprecated backends feature. Useappengine.ModuleHostnameandappengine.ModuleNameinstead.- Most of
appengine/fileand parts ofappengine/blobstoreare deprecated. Use Google Cloud Storage if the feature you require is not present in the new blobstore package. appengine/socketis not required on App Engine flexible environment / Managed VMs. Use the standardnetpackage instead.