gorgeous-translator-67757
11/08/2021, 9:44 PMcurved-summer-41191
11/08/2021, 9:52 PMsparse-beach-51011
11/08/2021, 10:30 PMsparse-beach-51011
11/08/2021, 10:31 PMabundant-book-94104
11/08/2021, 11:27 PMlittle-cartoon-10569
11/09/2021, 2:13 AMcolossal-furniture-61502
11/09/2021, 2:33 AMsparse-tomato-5980
11/09/2021, 3:38 AMpulumi login --local
?
If I try to do a pulumi stack init myusername/something
I get back a error: stack names may not contain slashes
My understanding is that stack init
respects org names, and under file:// your org name is just your username.steep-portugal-37539
11/09/2021, 4:53 AMnpm install
a pulumi repo via a github url? I keep getting error SyntaxError: Cannot use import statement outside a module
when running pulumi in the repo that installed the pulumi package.
It seems i may need to set the “main” field in package.json to point to the compiled entrypoint .js file. However, that then messes up pulumi when i try and run it locally from the repo. As now pulumi tries to invoke the index.js file instead of the index.ts file.
I’m trying to mimic how an installed pulumi npm module works. There are .js, .js.map, and .d.ts files. No .ts files. I’m not sure how to replicate this so that the install via github url works, as well as running pulumi within the pulumi pkg repo itself (I do that for testing)
I can’t figure this out 🙂 Any advice would be much appreciatedbored-barista-23480
11/09/2021, 11:45 AMException: 'dependsOn' was passed a value that was not a Resource.
, but I don't explicitly set the dependsOn
parameter. I boiled it down to one specific parameter creating the problem. I create an EKS cluster in my first project, export cluster.core
, import it in my second project and use it as the cluster
input to a ManagedNodeGroup
. Currently it's the only resource created in the second project and every other input is given explicitly (= not as an Output
type). Does any one have a clue where the error could originate or even how to solve it?future-refrigerator-88869
11/09/2021, 6:52 PMconst stackArgs: InlineProgramArgs = {
stackName: 'some name',
projectName: "org/project",
program: inlineProgram,
};
However, when executing this i get error: could not create stack: provided project name "org-project" doesn't match Pulumi.yaml
. However, there's no pulumi.yaml
file within the folder I run this so I'm a bit confused. everything works fine if i don't use the org
but that creates the project within the devops user environment. Any ideas ?limited-rainbow-51650
11/09/2021, 7:30 PMconfig:
<your-project-name>:<key>: <value>
Providers often look up their config with another "project-name", e.g.:
config:
aws:region: eu-west-1
<your-project-name>:<key>: <value>
If I create an abstraction in a reusable library, I could for example use a separate project key to store all the config for my component.
config:
aws:region: eu-west-1
<your-project-name>:<key>: <value>
<my-component-name>:<key1>: <value1>
<my-component-name>:<key2>: <value2>
Do other Pulumi developers use this ability for such use cases? Would this be a good pattern to use, or rather an anti-pattern?wide-jackal-86020
11/10/2021, 3:22 AMnpm build
inside pulumi? Here's the use case:
We need to build and deploy a frontend REACT application to S3. And we need to know which stack to deploy while building the application, so we can set up the environment variables properly. For example, if we are deploying to dev
, we should run ENV=dev npm build
. Since we can easily get the stack name in pulumi, it would be convenient if I can run npm build
inside pulumi.steep-portugal-37539
11/10/2021, 4:22 AMbusy-magazine-48939
11/10/2021, 9:57 AMsquare-coat-62279
11/10/2021, 10:18 AMnutritious-shampoo-16116
11/10/2021, 10:56 AMgreat-breakfast-56601
11/10/2021, 11:55 AMnew CustomResourceOptions { Protect }
option should be preventing destruction of resources by my pulumi up script or not?great-breakfast-56601
11/10/2021, 11:56 AMgreat-breakfast-56601
11/10/2021, 12:01 PMable-camera-57198
11/10/2021, 3:16 PMsparse-student-54516
11/10/2021, 3:21 PMbored-barista-23480
11/10/2021, 3:50 PMpulumi_eks
package to set up an EKS cluster in a project. I have to import the cluster in a second project and ran into a problem: pulumi_eks.Cluster
does not provide a get()
method. Under the hood there is a child resource of type pulumi_aws.eks.Cluster
with a static get()
method but it does not work ,Pulumi can't find it. Did I miss something or is there no way of importing the cluster if using the pulumi_eks
package to deploy it?able-camera-57198
11/10/2021, 4:56 PM.yaml
file in the current folder?
(I plan on using --config-file
)bulky-policeman-29913
11/10/2021, 8:44 PM@pulumi/vault
provider yet by any chance? I am not finding good examples/documentation around this on retrieving secrets from Hashicorp Vault.freezing-sugar-24066
11/10/2021, 9:08 PMdata
block. I saw that this can be done by aws.ec2.getVpc()
. However, this returns a Promise<aws.ec2.GetVpcResult>
instead of a Vpc
(which has pulumi.Output<string>
properties) and the two objects are very different. Am I barking up the right tree, here?
I see the static Vpc.get()
method, but it has parameters I don’t know the meaning of, such as `id: pulumi.Input<pulumi.ID>`… what would I pass in there?
If I go down the getVpc()
route with the Promise, could I end up having any kind of race condition issue between the time the details of that VPC are fetched and the actual stack deploys?full-dress-10026
11/10/2021, 11:06 PMconst provider = new aws.Provider(`${acctName}-provider`, {
region: "us-west-2",
assumeRole: {
roleArn: pulumi.interpolate`arn:aws:iam::${args.id}:role/${args.roleName}`
}
});
I later create a resource by passing the provider as the 3rd arg to the resource {provider: provider}
. After running pulumi up
, I receive the following message:
aws:iam:Role (access):
error: 1 error occurred:
* error configuring Terraform AWS Provider: IAM Role (arn:aws:iam::<<account id>>:role/<<role name>>) cannot be assumed.
There are a number of possible causes of this - the most common are:
* The credentials used in order to assume the role are invalid
* The credentials do not have appropriate permission to assume the role
* The role ARN is not valid
Error: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
How can I go about further debugging this?lemon-lamp-41193
11/11/2021, 1:16 AMbackend=auto.ProjectBackend(url="<s3://pulumistate/>")
)? I have a central bucket for managing state but it throws an error when deploying a new instance in another region.
could not create stack: could not list bucket: blob (code=Unknown): BucketRegionError: incorrect region, the bucket is not in 'us-west-1' region
white-train-9300
11/11/2021, 2:39 AMkubernetes:core/v1:PersistentVolume storage-3 refreshing warning: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: the server has asked for the client to provide credentials
abundant-book-94104
11/11/2021, 3:26 AMabundant-book-94104
11/11/2021, 3:26 AMlittle-cartoon-10569
11/11/2021, 3:32 AMup
. I think I saw that enum in code once... let me browse..abundant-book-94104
11/11/2021, 3:57 AMlittle-cartoon-10569
11/11/2021, 4:41 AMabundant-book-94104
11/11/2021, 12:43 PM