quiet-wolf-18467
hundreds-lizard-14182
05/08/2020, 8:35 PMDeleting urn:pulumi:aws-eks-validationm::aws-eks-validation::eks:index:Cluster$aws:ec2/securityGroupRule:SecurityGroupRule::my-cluster-eksClusterInternetEgressRule: No security group with ID "sg-0a887d22a0e34ccc4"
What are my options from here?hundreds-lizard-14182
05/08/2020, 8:54 PMPreview failed: refreshing urn:pulumi:aws-eks-validationm::aws-eks-validation::aws:s3/bucket:Bucket::my-bucket: error reading S3 Bucket (my-bucket-50e001c): BucketRegionError: incorrect region, the bucket is not in 'us-east-2' region at endpoint ''
How do I recover from this?chilly-hairdresser-56259
05/08/2020, 9:12 PMcolossal-room-15708
05/09/2020, 1:04 AMerror: could not load plugin for azure provider 'urn:pulumi:incidentdev::azure-incidents::pulumi:providers:azure::default_2_5_0_alpha_1586239871': no resource plugin 'azure-v2.5.0-alpha.1586239871' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource azure v2.5.0-alpha.1586239871`
Just before that however it is installing the correct azure plugin based on our package.json
Logged into 5a66626ce332 as root (***)
> @pulumi/azure@3.4.0 install /github/workspace/node_modules/@pulumi/azure
> node scripts/install-pulumi-plugin.js resource azure v3.4.0
[resource plugin azure-3.4.0] installing
Downloading plugin: 0 B / 47.81 MiB 0.00%
Downloading plugin: 86.06 KiB / 47.81 MiB 0.18% 1m53s
Downloading plugin: 854.06 KiB / 47.81 MiB 1.74% 22s
Downloading plugin: 3.44 MiB / 47.81 MiB 7.19% 7s
Downloading plugin: 12.08 MiB / 47.81 MiB 25.27% 2s
Downloading plugin: 18.15 MiB / 47.81 MiB 37.95% 1s
Downloading plugin: 25.56 MiB / 47.81 MiB 53.46% 1s
Downloading plugin: 32.87 MiB / 47.81 MiB 68.74%
Downloading plugin: 40.58 MiB / 47.81 MiB 84.88%
Downloading plugin: 47.81 MiB / 47.81 MiB 100.00%
Downloading plugin: 47.81 MiB / 47.81 MiB 100.00%
Downloading plugin: 47.81 MiB / 47.81 MiB 100.00%
Downloading plugin: 47.81 MiB / 47.81 MiB 100.00%
Downloading plugin: 47.81 MiB / 47.81 MiB 100.00%
Downloading plugin: 47.81 MiB / 47.81 MiB 100.00%
Downloading plugin: 47.81 MiB / 47.81 MiB 100.00% 2s
Moving plugin... done.
Locally we've updated to the latest pulumi version already.fierce-father-77362
05/09/2020, 9:19 AMwitty-spring-28765
05/09/2020, 8:13 PMsilly-hairdresser-21136
05/10/2020, 9:49 AMpulumi up
results in an error:
[09:32:47] pulumi:providers:random (default_2_2_0):
[09:32:47] error: no resource plugin 'random-v2.2.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource random v2.2.0`
it doesn't seem like upgrading @pulumi/aws should change the random plugin version, and running the install command from the error message results in:
[resource plugin random-2.2.0] installing
error: [resource plugin random-2.2.0] downloading from <https://api.pulumi.com/releases/plugins>: 404 HTTP error fetching plugin from <https://api.pulumi.com/releases/plugins/pulumi-resource-random-v2.2.0-darwin-amd64.tar.gz>
anyone else seen this problem?gifted-ocean-95126
05/10/2020, 2:22 PM-o StrictHostKeyChecking=no
). One way to achieve this is to generate the Droplet host keys locally on my PC then apply them to the Droplets using the user_data
droplet property. I could then add the host public keys to the Pulumi stack output and configure Ansible to check the hosts against those public keys when connecting.
But, running pulumi stack export
shows that the original #cloud-config
file, including the private keys, is being stored in the stack state. Although I understand that the data is encrypted, storing these files is unnecessary and so I would prefer not to store them.
Can I tell Pulumi to store the hashes and not the original contents of resource properties? Thank you.fierce-father-77362
05/10/2020, 3:57 PMproud-optician-56680
05/10/2020, 5:59 PMproud-optician-56680
05/10/2020, 6:03 PMbitter-toddler-22112
05/11/2020, 1:09 PMhundreds-lizard-14182
05/11/2020, 3:44 PMeksctl create cluster --managed
?gray-tailor-20387
05/11/2020, 3:46 PMgifted-ocean-95126
05/11/2020, 5:23 PM#cloud-config
dynamic resource) and my current workflow is that I am just running pulumi up
over an over again to see what actions Pulumi would like to take. This is a difficult way to work, it is a lot of trial and error without little insight.
I would like to try to understand, in detail what resource graph my program is defining so that I can know, for example:
• whether the provisioner is correctly registered on the resource,
• whether the create
resource method will be called when the program-defined graph will be compared to the state-stored graph,
• if I succeeded in writing the program such that the provisioner is able to modify the properties of the resource (or add to its output).
I am aware that there are documents that can help me with this, namely the dynamic resources section in the programming model documentation and the documentation on testing, but... there is quite a lot of information there to absorb.
So, my question is this: what is the recommended workflow for developing dynamic providers? Is it possible to learn useful things about the behaviour of my provisioners code without using the pulumi
command?busy-umbrella-36067
05/11/2020, 7:59 PMpulumi new
templates to add typescript 3.8's export * as ns
syntax?sticky-thailand-14236
05/11/2020, 10:02 PM[1/3] Finding Pods to direct traffic to
when in doing a pulumi up
with my service. the following is my service:
const streamService = new k8s.core.v1.Service(config.appNameStream, {
metadata: {
namespace: namespace.metadata.name,
labels: {
app: config.appNameStream,
service: config.appNameStream
}
},
spec: {
ports: [{name: "grpc", port: 50051}],
selector: {
app: config.appNameStream
}
}
})
What exactly am i doing wrong?creamy-potato-29402
05/11/2020, 10:25 PMsticky-thailand-14236
05/12/2020, 1:33 AMconst kongCustomResourceConsumer = new k8s.apiextensions.CustomResource("developer", {
apiVersion: "<http://configuration.konghq.com/v1|configuration.konghq.com/v1>",
kind: "KongConsumer",
metadata: {
namespace: namespace.metadata.name
},
username: "developer"
});
const kongCustomResourceConsumerKey = new k8s.apiextensions.CustomResource("developer-apikey", {
apiVersion: "<http://configuration.konghq.com/v1|configuration.konghq.com/v1>",
kind: "KongCredential",
metadata: {
namespace: namespace.metadata.name
},
consumerRef: `${kongCustomResourceConsumer.metadata.name}`,
type: "key-auth",
config: {
key: "b362c400-4904-4176-9ae7-74bf03a63619"
}
});
flat-mechanic-75334
05/12/2020, 9:07 AMgcloud compute addresses create helloweb-ip --global
bland-cat-29878
05/12/2020, 10:26 AMcool-egg-852
05/12/2020, 2:36 PMwonderful-dog-9045
05/12/2020, 2:49 PMhelpful-processor-86468
05/12/2020, 2:51 PMservice.Template.Metadata()
I'm getting an error applier must have 1 input parameter assignable
wonderful-dog-9045
05/12/2020, 4:14 PMError: The root stack resource was referenced before it was initialized.
at Object.registerStackTransformation (/home/gsuess/empirica/meteor-deploy/node_modules/@pulumi/pulumi/runtime/stack.js:211:15)
What am I doing wrong?incalculable-whale-36468
05/12/2020, 8:23 PMicy-jordan-58549
05/13/2020, 3:06 AMcold-rocket-35235
05/13/2020, 11:37 AMrough-baker-21016
05/13/2020, 12:22 PMfunction publicReadPolicyForBucket
I need access to both the name of the bucket which has just been created created, AND the arn of a role that has just been created.
Specifically, my policy needs to look like this (the difference from the example is the Principal
which in my case needs to interpolate the role, instead of just being *
function publicReadPolicyForBucket(bucketName: string, roleName: string) {
return JSON.stringify({
Version: "2012-10-17",
Statement: [{
Effect: "Allow",
Principal: "`${role.arn}`",
Action: [
"s3:GetObject"
],
Resource: [
`arn:aws:s3:::${bucketName}/*` // policy refers to bucket name explicitly
]
}]
});
}
The error message I get recommends using the bucket.bucket.apply()
pattern, but I can’t see how this extends to allowing me to interpolate both the bucket name and the role