orange-australia-91292
12/27/2019, 9:57 AMpython3
and try to do the following at the interactive prompt:
>>> import pulumi
>>> config = pulumi.Config()
and I get “Program run without the Pulumi engine available; re-run using the pulumi
CLI”
The pulumi binary is in PATH, I checked with print(os.environ["PATH"])
What else does it need?broad-dog-22463
12/27/2019, 10:57 AMorange-australia-91292
12/27/2019, 11:41 AMTraceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Users/bgdnlp/khron/.env/lib/python3.7/site-packages/pulumi/config.py", line 46, in __init__
name = get_project()
File "/Users/bgdnlp/khron/.env/lib/python3.7/site-packages/pulumi/metadata.py", line 23, in get_project
return runtime_gp()
File "/Users/bgdnlp/khron/.env/lib/python3.7/site-packages/pulumi/runtime/settings.py", line 126, in get_project
require_test_mode_enabled()
File "/Users/bgdnlp/khron/.env/lib/python3.7/site-packages/pulumi/runtime/settings.py", line 114, in require_test_mode_enabled
raise RunError('Program run without the Pulumi engine available; re-run using the `pulumi` CLI')
pulumi.errors.RunError: Program run without the Pulumi engine available; re-run using the `pulumi` CLI
config = pulumi.Config()
as a valid example in several places, but the code seems to require either a project name or “test mode” set. Maybe I’m missing something. Is it a bug, should I open an issue?glamorous-printer-66548
12/27/2019, 1:42 PMpulumi
CLI command and not via the python3
command as entry-point.orange-australia-91292
12/27/2019, 3:03 PMpulumi config set testkey "testvalue"
and then retrieve it with Config.require(“testkey”) and it says it’s not set, although I can see it in yaml file.
Either it’s quite bugged, or I don’t understand how it should work. Pretty sure it’s bugged. I’ll open an issue.broad-dog-22463
12/27/2019, 4:04 PMglamorous-printer-66548
12/27/2019, 4:46 PMorange-australia-91292
12/27/2019, 6:11 PMbucket = s3.Bucket("bktname")
bucket.lifecycle_policy=[]
gentle-diamond-70147
12/27/2019, 8:07 PMWhich means that everything about that resource should be set when the object is created, otherwise things can get weird. So we shouldn’t expect to be able to do things likeThat's correct - everything must be set when the object is created. You cannot modify resource arguments like
bucket.lifecycle_policy=[]
.glamorous-printer-66548
12/27/2019, 8:17 PMorange-australia-91292
12/27/2019, 8:59 PM