proud-spoon-58287
08/05/2020, 11:00 AMnutritious-battery-42762
08/05/2020, 12:57 PMastonishing-quill-88807
08/05/2020, 4:31 PM__main__.py
and I'm creating separate stacks for each of them using an S3 backend. Currently I've been creating the stack definitions inside the modules, but I accidentally ended up with one at the root of the project and it automatically added a line to the config with a path to the module. I just wanted to double check whether my initial approach is the "correct" way, or if I should be creating the stack definition yaml in the root of the repository?
Repository: https://github.com/mitodl/ol-infrastructure/
Root level stack definition: https://github.com/mitodl/ol-infrastructure/blob/main/Pulumi.infrastructure.aws.dns.yaml
Module level stack definition: https://github.com/mitodl/ol-infrastructure/blob/main/src/ol_infrastructure/infrastructure/aws/dns/Pulumi.infrastructure.aws.dns.yamlastonishing-quill-88807
08/05/2020, 8:34 PMup
command. Is there something I need to do to get it to recognize the fact that I've already got the KMS secret management set up?many-egg-6856
08/05/2020, 8:46 PMpulumi.yaml
override the backend set by pulumi login
?proud-spoon-58287
08/05/2020, 9:48 PMpulumi.interpolate`"org.apache.kafka.common.security.plain.PlainLoginModule required username=\\"${config.requireSecret('kafkaApiKey')}\\" password=\\"${config.requireSecret('kafkaApiSecret')}\\";"`
thankful-holiday-28161
08/05/2020, 10:53 PMimport ipdb; ipdb.set_trace()
for Python or debugger;
for TypeScript?thankful-holiday-28161
08/05/2020, 10:56 PMthankful-holiday-28161
08/05/2020, 10:56 PMA key for signing Cloud CDN signed URLs for BackendBuckets. To get more information about BackendBucketSignedUrlKey, see: * [API documentation](<https://cloud.google.com/compute/docs/reference/rest/v1/backendBuckets>) * How-to Guides * [Using Signed URLs](<https://cloud.google.com/cdn/docs/using-signed-urls/>) > **Warning:** All arguments including `keyValue` will be stored in the raw state as plain-text. #### Example Usage - Backend Bucket Signed Url Key ```typescript import * as pulumi from "@pulumi/pulumi"; import * as gcp from "@pulumi/gcp"; const bucket = new gcp.storage.Bucket("bucket", {location: "EU"}); const testBackend = new gcp.compute.BackendBucket("testBackend", { description: "Contains beautiful images", bucketName: bucket.name, enableCdn: true, }); const backendKey = new gcp.compute.BackendBucketSignedUrlKey("backendKey", { keyValue: "pPsVemX8GM46QVeezid6Rw==", backendBucket: testBackend.name, }); ```
damp-elephant-82829
08/06/2020, 7:51 AMastonishing-quill-88807
08/06/2020, 1:27 PMdamp-elephant-82829
08/06/2020, 2:07 PMdamp-elephant-82829
08/06/2020, 2:07 PMastonishing-quill-88807
08/06/2020, 2:07 PMproud-spoon-58287
08/06/2020, 2:13 PMk8s.helm.v3.Chart
nutritious-battery-42762
08/06/2020, 2:25 PMgifted-student-18589
08/06/2020, 4:12 PMPulumi.yaml
files, meaning two Pulumi projects, one in the api
folder (in the sshot letter A
) and the other in the apps/admin
folder (in the sshot letter B
). What is surprising to me is that when I go to A
and run pulumi up
, it deploys stuff fine, but when I go to B
, then it’s actually still working with A
but it’s using the index.ts
from B
. Is this normal? So for example, in A
I have a simple IAM role, and running pulumi up
in there deploys it. But then, cd-ing to B
, where index.ts
contains as simple S3 bucket, and running again pulumi up
says that it will remove the IAM role, and deploy the bucket.
Maybe I’m not using projects as they are meant to be used, and I should just handle this situation with different stack names, and a single Pulumi project?nutritious-battery-42762
08/06/2020, 5:01 PMcareful-engine-71229
08/06/2020, 6:55 PMcareful-engine-71229
08/06/2020, 6:55 PMcareful-engine-71229
08/06/2020, 6:55 PMcareful-engine-71229
08/06/2020, 6:55 PMcareful-engine-71229
08/06/2020, 6:55 PMcareful-engine-71229
08/06/2020, 6:56 PMfull-dress-10026
08/06/2020, 8:17 PMfast-dinner-32080
08/06/2020, 8:31 PMminiature-megabyte-76794
08/06/2020, 10:43 PMeb setenv KEY=VALUE
for AWS Elastic Beanstalk? I am trying to create an aws.elasticbeanstalk.Environment
, and want to make an environment variable with CNAME
as a value. I've tried to pass CNAME
in as a setting, but because I can only access it when the resource itself is fully created, I've seem to run into a sort of "The Chicken or the Egg" problem in which I need the output of a resource in order to make the inputs for it.elegant-window-55250
08/07/2020, 7:32 AMmaster
, develop
branch). The services are kept in smaller repositories, the CI/CD builds and deploys Docker images. I’d like to deploy versions based on branch, and for develop branch I’d like to deploy latest version. I’ve considered adding another GitOps tool, such as Flux or otherwise, but I don’t really want to introduce that into the stack, I’d like to keep using Pulumi, Pulumi should know the state at all times. I don’t really want to add Pulumi to the services repositories (to keep things separated). Any ideas?bland-ice-32467
08/07/2020, 9:01 AMdelightful-controller-41497
08/07/2020, 9:57 AM