sparse-intern-71089
06/10/2019, 7:45 PMhandsome-actor-1155
06/10/2019, 7:49 PMconst stackRef = new pulumi.StackReference("accountname/foo-deploy/dev");
boundless-monkey-50243
06/10/2019, 7:50 PMboundless-monkey-50243
06/10/2019, 7:50 PMboundless-monkey-50243
06/10/2019, 7:50 PMdev
stack from it? <s3://pulumi-foo-deploy/dev>
doesn’t work.boundless-monkey-50243
06/10/2019, 7:53 PMNotFoundKey
errors, so it’s looking for something, just can’t find it. Next stop is CloudTrail I guess. 😧handsome-actor-1155
06/10/2019, 7:54 PMboundless-monkey-50243
06/10/2019, 7:55 PMwhite-balloon-205
boundless-monkey-50243
06/11/2019, 2:16 PMboundless-monkey-50243
06/11/2019, 2:17 PMboundless-monkey-50243
06/11/2019, 2:17 PMwhite-balloon-205
boundless-monkey-50243
06/11/2019, 4:22 PMapp-deploy
workspace to be able to acquire data out of, say, the network-base
workspace, keyed to a particular stack.boundless-monkey-50243
06/11/2019, 4:23 PMapp-deploy
does not imply write access to network-base
, regardless of environment (Pulumi stack) being worked on.boundless-monkey-50243
06/11/2019, 4:24 PM.pulumi
directory because it 1) makes for (what I think are) less comprehensible IAM policies, and 2) means then that my developers have to remember--and they will not remember--to do stuff like pulumi stack some-app/dev
in their working directories, rather than pulumi stack dev
.
If it helps, the analogy I'm looking for is to separate terraform.tfstate
files.boundless-monkey-50243
06/11/2019, 4:25 PMdev
stack! I'm going to look for the dev
stack in network-base
and find out my VPC CIDR block!".boundless-monkey-50243
06/11/2019, 4:29 PMshy-receptionist-99213
06/11/2019, 5:47 PMpulumi login <s3://some-bucket/infra>
and services have pulumi login <s3://some-bucket/service>
. How do we reference infra
from service
ones?boundless-monkey-50243
06/11/2019, 6:21 PMpulumi login
at a system level, too. This feels like it should be per-directory.boundless-monkey-50243
06/11/2019, 6:29 PMpulumi stack switch dev.deploy.data-api-v2
and to be aware of eye-popping files like Pulumi.dev.deploy.data-api-v2.yaml
. Admittedly this might be a little vain, but that's just really unpleasant to be throwing in a repo when the file itself lives in data-api-v2/deploy
(because we also have a data-api-v2/build
Pulumi...I keep wanting to call them stacks...workspace?...that contains our CodeBuild, CodePipeline, etc. definitions) .boundless-monkey-50243
06/11/2019, 6:30 PMshy-receptionist-99213
06/11/2019, 6:40 PMname
from pulumi.yaml is not used for file location, similar to pulumi backed where it's used for namespacing.shy-receptionist-99213
06/11/2019, 6:43 PMboundless-monkey-50243
06/11/2019, 6:43 PMshy-receptionist-99213
06/11/2019, 6:44 PMboundless-monkey-50243
06/11/2019, 6:57 PM