red-match-15116
05/12/2021, 5:04 PMripe-knife-11053
05/12/2021, 5:37 PMcurved-cartoon-90054
05/12/2021, 6:02 PMcuddly-father-4905
05/12/2021, 7:13 PMProject
from `@pulumi/gcp/organizations`: new Project('project:dev', { ...config })
is invalid, whereas IAMBinding
from `@pulumi/gcp/projects`: new IAMBinding('iam:my-role', { ...config })
is validcolossal-australia-65039
05/12/2021, 8:39 PMpulumi preview --diff
does not actually show the diff but only within arrays, e.g.
~ spec: {
~ template: {
~ spec: {
~ containers: [
~ [0]: {
// there should be something here but it's empty!!
}
]
}
}
}
rough-window-15889
05/12/2021, 10:48 PMrough-window-15889
05/12/2021, 11:21 PMbrash-airline-37413
05/13/2021, 6:33 AMimport { Vpc } from '@pulumi/awsx/ec2';
import { describe, it } from 'mocha';
describe('Network', () => {
const myvpc: Vpc = new Vpc('test', {
cidrBlock: '10.0.0.0/16',
});
it('should use correct cidr address', (done) => {
myvpc.vpc.cidrBlock.apply(vpc => {
done();
});
});
});
full error is
Network
(node:84386) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 3)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:84386) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 4)
Does anybody know what is happening here?early-truck-24471
05/13/2021, 11:43 AM└── project
├── __main__.py
├── Pulumi.yaml
└── environments
└──PROD
├── Pulumi.prod1.yaml
├── Pulumi.prod2.yaml
└──STG
├── Pulumi.stg1.yaml
├── Pulumi.stg2.yaml
dazzling-kilobyte-32990
05/13/2021, 12:45 PMbrash-kite-78002
05/13/2021, 1:06 PMlemon-machine-35564
05/13/2021, 4:11 PMaws.cloudwatch.MetricAlarm
to create a resource and I keep getting Type 'string' is not assignable to type 'Input<number>'.
for many of the inputs. Note, this is just the example listed on https://www.pulumi.com/docs/reference/pkg/aws/cloudwatch/metricalarm/green-musician-49057
05/13/2021, 5:32 PMpulumi config set
do anything aside from updating the yaml file? Is it safe to update the yaml directly? (I've been assuming it is safe)fast-vegetable-68654
05/13/2021, 5:40 PMComponentResource
and a function wrapping a group of resources? Why would you reach for one over the other?lively-wire-16126
05/13/2021, 6:01 PMaws-sdk
because I want to use a feature that isn't available in the terraform/pulumi resources yet. I'm using explicitly created providers to assume roles to manage resources in multiple AWS accounts, but I can't figure out how to make sure my component resource is using credentials for the correct AWS account. I found this: https://www.pulumi.com/blog/dynamic-providers/#provider-credentials
But I don't actually understand what that means in terms of, like, how to actually instantiate the AWS sdk resources with the correct credentials. Does anyone have an example of what this looks like in practice?lively-wire-16126
05/13/2021, 6:02 PM{ provider: myProvider }
as the CustomResourceOptions
but that doesn't seem to do it.full-dress-10026
05/13/2021, 7:19 PMfull-artist-27215
05/13/2021, 8:42 PMself.register_outputs({
"endpoint":
pulumi.Output.concat(
"redis://",
self.cluster.cache_nodes[0].address,
":",
str(self.cluster.cache_nodes[0].port)
)
})
but when I go to use it like this:
cache.endpoint
I end up with the following:
AttributeError: 'Cache' object has no attribute 'endpoint'
(this is all Python, BTW). Thanks in advance 🙇full-artist-27215
05/13/2021, 9:37 PMrole.arn.apply(lambda arn: json.dumps({"foo": arn}))
When you have multiple things that need to be interpolated, things get a little more complicated:
pulumi.Output.all(
foo.arn,
bar.arn,
baz.arn
).apply(
lambda args: json.dumps({
"foo": args[0],
"bar": args[1],
"baz": args[2]
})
)
While that's awkward, it's doable when you have all the `pulumi.Output`s that you need readily at hand.
I'm using `ComponentResource`s to model my domain. In general, I'd like to be able to pass a dictionary of values into my ComponentResource
, and then have it merge that with another dictionary of default values within the ComponentResource
itself. Then, this merged dictionary would need to be converted into a JSON string to pass to the low-level Resource.
env = {
"foo": "my_foo",
"message": "hello world"
}
pulumi.Output.all(
foo.arn,
bar.arn,
baz.arn
).apply(
lambda args: json.dumps({
"foo": args[0],
"bar": args[1],
"baz": args[2],
**env
})
)
If that inner "default values" dictionary is the one that contains the pulumi.Output
values, then I can control things with pulumi.Output.all
, as shown above. If I've got pulumi.Output
values in that dictionary that I'm merging in, though, it's not clear how I can generically manage things.
I'm curious if others have run into similar situations, or if people have some patterns for managing such data (generic, if possible; Python-specific works too). Thanks in advance.gorgeous-minister-41131
05/13/2021, 9:51 PMgorgeous-minister-41131
05/13/2021, 10:03 PMpulumi config
or pulumi update
etc?gorgeous-minister-41131
05/13/2021, 10:04 PMgorgeous-minister-41131
05/13/2021, 10:05 PMenough-truck-34175
05/13/2021, 11:31 PMlittle-cartoon-10569
05/14/2021, 4:45 AMwarning: urn😛ulumi:stack😛roject:aws:PublicProxy$cloudinit:index/config:Config::stack verification warning: Deprecated ResourceI can't see it in the code anywhere, and there's no additional info.
gorgeous-country-43026
05/14/2021, 9:31 AMastonishing-monitor-96741
05/14/2021, 12:26 PMecrblahblah/repo:38989f9f92096e33d3d8505a833f7cf4aaf30a12afec448f895394aefc1e4372-570125e6816fe0b91a5e7c432a3cc0581d864ad49a3f68a7074e00369321cac4
orange-lawyer-86718
05/14/2021, 12:33 PMbig-architect-71258
05/14/2021, 6:55 PMpulumi preview
.
https://github.com/pulumi/pulumi-azure/issues/890green-knife-34770
05/15/2021, 2:22 PMawsx.ecs.Image.fromDockerBuild
and when the image gets running on AWS it throws standard_init_linux.go:219: exec user process caused: exec format error
. So I found this article where using dockers buildx resolves the issue. My question is, how can I use buildx with pulumi? (Even better exactly within awsx.ecs.Image.fromDockerBuild
) I saw only mention for a new Pulumi blog article exactly about that, but it hasn’t come up yet. Thank you for your time!green-knife-34770
05/15/2021, 2:22 PMawsx.ecs.Image.fromDockerBuild
and when the image gets running on AWS it throws standard_init_linux.go:219: exec user process caused: exec format error
. So I found this article where using dockers buildx resolves the issue. My question is, how can I use buildx with pulumi? (Even better exactly within awsx.ecs.Image.fromDockerBuild
) I saw only mention for a new Pulumi blog article exactly about that, but it hasn’t come up yet. Thank you for your time!proud-art-41399
05/15/2021, 3:05 PMdocker buildx install
before pulumi up.
In my case this was via a setup-buildx-action in GitHub Actions workflow.