a045e2fb1e
This change includes a lot more functionality. Enough to actually run the webserver-py example through previews, updates, and destroys! * Actually wire up the gRPC connections to the engine/monitor. * Move the Node.js and Python generated Protobuf/gRPC files underneath the actual SDK directories to simplify this generally. No more copying during `make` and, in fact, this was required to give a smoother experience with good packages/modules for the Python's SDK development. * Build the Python egg during `make build`. * Add support for program stacks. Just like with the Node.js runtime, we will auto-parent any resources without explicit parents to a single top-level resource component. * Add support for component resource output properties. * Add get_project() and get_stack() functions for retrieving the current project and stack names. * Properly use UNKNOWN sentinels. * Add a set_outputs() function on Resource. This is defined by the code-generator and allows custom logic for output property setting. This is cleaner than the way we do this in Node.js, and gives us a way to ensure that output properties are "real" properties, complete with member documentation. This also gives us a hook to perform name demangling, which the code-generator typically controls anyway. * Add package dependencies to setuptools.py and requirements.txt.
44 lines
2 KiB
Bash
Executable file
44 lines
2 KiB
Bash
Executable file
#!/bin/bash
|
|
# This script regenerates all Protobuf/gRPC client files.
|
|
#
|
|
# For now, it must be run manually, and the results are checked into source control. Eventually we might choose to
|
|
# automate this process as part of the overall build so that it's less manual and hence error prone.
|
|
#
|
|
# To run this script, the following pre-requisites are necessary:
|
|
#
|
|
# 1) Install the latest Protobuf compiler from https://github.com/google/protobuf/releases.
|
|
# 2) Add the `protoc` binary to your PATH (so that it can be found below).
|
|
# 3) Install the Golang Protobuf compiler by running this command from your Go workspace (also on your PATH):
|
|
# go get -u github.com/golang/protobuf/{proto,protoc-gen-go}
|
|
# 4) Install the Node.js gRPC SDK, which includes the gRPC Node.js compiler plugin
|
|
# npm install -g grpc-tools
|
|
# and add the `grpc_tools_node_protoc_plugin` binary to your PATH.a
|
|
# 5) Install the Python gRPC SDK, which includes the gRPC Python compiler plugin
|
|
# python -m pip install grpcio grpcio-tools
|
|
#
|
|
# The results are checked into bin/; at this moment, they need to be copied to their final destinations manually.
|
|
set -e
|
|
|
|
PROTOC=$(which protoc || { >&2 echo "error: Protobuf compiler (protoc) not found on PATH"; exit 1; })
|
|
|
|
echo Generating Protobuf/gRPC SDK files:
|
|
|
|
GO_PULUMIRPC=./go
|
|
GO_PROTOFLAGS="plugins=grpc"
|
|
echo -e "\tGo: $GO_PULUMIRPC [$GO_PROTOFLAGS]"
|
|
mkdir -p $GO_PULUMIRPC
|
|
$PROTOC --go_out=$GO_PROTOFLAGS:$GO_PULUMIRPC *.proto
|
|
|
|
JS_PULUMIRPC=../nodejs/proto/
|
|
JS_PROTOFLAGS="import_style=commonjs,binary"
|
|
echo -e "\tJS: $JS_PULUMIRPC [$JS_PROTOFLAGS]"
|
|
mkdir -p $JS_PULUMIRPC
|
|
$PROTOC --js_out=$JS_PROTOFLAGS:$JS_PULUMIRPC --grpc_out=$JS_PULUMIRPC --plugin=protoc-gen-grpc=`which grpc_tools_node_protoc_plugin` *.proto
|
|
|
|
PY_PULUMIRPC=../python/lib/pulumi/runtime/proto/
|
|
echo -e "\tPython: $PY_PULUMIRPC"
|
|
mkdir -p $PY_PULUMIRPC
|
|
python -m grpc_tools.protoc -I./ --python_out=$PY_PULUMIRPC --grpc_python_out=$PY_PULUMIRPC *.proto
|
|
|
|
echo Done.
|