protocol spec #3049
Draft
protocol spec #3049
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VenelinMartinov
force-pushed
the
vvm/engine_bridge_protocolspec
branch
from
4dc08bb to
a5071f9
Compare
VenelinMartinov
force-pushed
the
vvm/engine_bridge_protocolspec
branch
from
d1d4926 to
89cd14e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is intended as a spec for the interactions between TF providers, the bridge and the engine. I've tried to keep only the essential parts of the various user flows.
tf_protocol_types.gohas the TF protocol - the bridge calls these.pulumi_protocol_types.gohas the pulumi protocol - the engine calls this and the bridge implements it.bridge.gohas the current bridge implementation.current_engine.gohas the current engine behaviourengine_with_run_program.gohas the engine behaviour under---run-program.pulumi_types_v2,bridgev2andenginev2has some ideas on how a simpler protocol might look like.