Repository navigation
feat: add Python inline/local hybrid example - #87
Open
tomatotomata wants to merge 1 commit into
Open
tomatotomata wants to merge 1 commit into
tomatotomata wants to merge 1 commit into
Conversation
|
PR is now waiting for a maintainer to run the acceptance tests. |
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
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.
What this adds
Issue #30 asks for a Python equivalent of the existing Go inline/local hybrid example. This PR adds that parity example:
python/inline_local_hybrid/infraPulumi.yamlThe two drivers intentionally share the same
website_deployfunction, so the example demonstrates the requested hybrid workflow rather than duplicating infrastructure code.Validation
python -m compileall -q python/inline_local_hybridgit diff --checkI could not run a cloud deployment here because the environment has no Pulumi AWS provider or AWS credentials. The example keeps the same AWS v4 dependency range and resource shape as the existing Go counterpart.
Let me know what you think.