alert-horse-34916
06/15/2021, 10:40 AMicy-jordan-58549
06/15/2021, 1:41 PMcrd2pulumi --nodejsPath=src/ crds/actions.summerwind.dev_horizontalrunnerautoscalers.yaml crds/actions.summerwind.dev_runnerreplicasets.yaml crds/actions.summerwind.dev_runnerdeployments.yaml --force && rm src/tsconfig.json && rm src/package.json
panic: fatal: error An assertion has failed: could not parse Pulumi package. source error: could not import spec: binding types: failed to bind type kubernetes:actions.summerwind.dev/v1alpha1:RunnerReplicaSetSpecTemplateSpecInitContainers: unknown required property name
goroutine 1 [running]:
<http://github.com/pulumi/pulumi/sdk/v2/go/common/util/contract.failfast(...)|github.com/pulumi/pulumi/sdk/v2/go/common/util/contract.failfast(...)>
/Users/fed/go/pkg/mod/github.com/pulumi/pulumi/sdk/v2@v2.9.2/go/common/util/contract/failfast.go:23
boundless-angle-56560
06/15/2021, 2:06 PMnice-airport-15607
06/15/2021, 3:37 PMnote
things like
During some program executions, apply doesn't run. For example, it won't run during a preview, when resource output values may be unknown. Therefore, you should avoid side-effects within the callbacks. For this reason, you should not allocate new resources inside of your callbacks either, as it could lead to pulumi preview being wrong.
☝️ then you should also show examples of what should be expected as an example of “how to do this” otherwise it’s kind of tiresome to pulumi up
a bunch of times just to fail…agreeable-eye-87399
06/15/2021, 5:22 PMbrash-kite-78002
06/15/2021, 6:28 PMbumpy-summer-9075
06/15/2021, 7:24 PM--color raw
option for?brash-flag-57291
06/15/2021, 8:32 PMconst lambdaFunction = new aws.lambda.CallbackFunction("foo-function", {
callback: handler,
runtime: "nodejs14.x",
})
const apis = await aws.apigatewayv2.getApis({ name: "my-existing-api" })
const apiId = apis.ids[0]
const api = await aws.apigatewayv2.getApi({ apiId })
const integration = new aws.apigatewayv2.Integration("foo-integration", {
apiId: api.id,
integrationType: "AWS_PROXY",
integrationMethod: "POST",
integrationUri: lambdaFunction.invokeArn,
})
const route = new aws.apigatewayv2.Route("foo-route", {
apiId: api.id,
routeKey: "POST /foo",
target: pulumi.interpolate`integrations/${integration.id}`,
})
salmon-mechanic-4571
06/16/2021, 12:07 PMbusy-honey-73811
06/16/2021, 2:23 PMnice-airport-15607
06/16/2021, 3:31 PMsparse-tomato-5980
06/16/2021, 3:36 PMsparse-tomato-5980
06/16/2021, 3:36 PMmillions-umbrella-34765
06/16/2021, 5:33 PMcuddly-leather-18640
06/16/2021, 7:17 PMcache-from
feature of the pulumi docker go implementation is broken: https://github.com/pulumi/pulumi-docker/issues/238
I can hack around this by:
1. pulling the image I want to use as a cache
2. manually running docker build --cache-from my-image
3. executing `pulumi preview`/`pulumi up`
My intuition tells me that the manual docker build
step should populate the layer cache and therefore speed up the pulumi commands which build the docker image but I’m finding that even with this workflow pulumi recreates the docker image from scratch.
Is my intuition incorrect? If so how? Is there another way I can hack around the current bug with cache-from in the go implementation?orange-byte-86458
06/17/2021, 4:59 AMpulumi state delete
command successfully? I need to fix a broken stack but every time I try to delete something by URN it tells me this resource doesn’t exist. What am I doing wrong here (see attached screenshot)? Thanks!tall-beard-99429
06/17/2021, 9:28 AMhelpful-morning-53046
06/17/2021, 10:59 AMpulumi preview
. It fails to delete due to deletion protection luckily. I can't seem to find a way around it as the cause is not reported, just a failed message as below.
aws:ec2:LaunchConfiguration (ecs-cluster-test):
error: Preview failed: refusing to delete protected resource 'urn:pulumi:orchestration-infrastructure::orchestration-infrastructure::aws:ec2/launchConfiguration:LaunchConfiguration::ecs-cluster-test'
Has anyone else come across this before or know how to work around it?bored-continent-69206
06/17/2021, 12:21 PMfierce-angle-25551
06/17/2021, 2:20 PMripe-oil-46657
06/17/2021, 3:15 PMhelm3 --create-namespace
argument in the helm.NewChart
function in Go? I would like to create a new namespace as part of the chart deployment.cuddly-leather-18640
06/17/2021, 3:38 PM{"Namespace":"default","Signal":"terminated","TaskQueue":"main-task-queue","WorkerID":"34276@Paymahns-Air@","level":"error","msg":"Worker has been stopped.","time":"2021-06-17T10:33:39-05:00"}
(notice the Signal
field) when it receives a SIGTERM or SIGINT. I’ve noticed that when I perform pulumi up
(with a new docker image) the pod gets killed without ever emitting the above log message which suggests to me that the pod is getting a SIGKILL without having the option to shutdown gracefully.
Is this how pulumi up
is intended to behave? Do I have something misconfigured? Is there another explanation?bumpy-summer-9075
06/17/2021, 7:35 PMts-node
and typescript
in my dependencies (they're in my node_modules
folder), but Pulumi throws error: Error: Cannot find module 'typescript'
which is driving me crazy.purple-lawyer-35555
06/18/2021, 9:17 AMsetConfig('aws:region', {value: 'myValue'})
aws.config.region or aws.getRegion() // in this way I can somehow obtain the configuration
// also with const awsConfigRegion = new pulumi.Config('aws').get('region')
Example2:
If I do not have them defined with setConfig/yaml file but in aws.Provider and pass this provider to my CustomResource, I haven't found a clear way to access these values_._
// file1.ts
const awsProvider = new aws.Provider(
'aws-provider',
{region: 'eu-west-1', profile: 'some-profile'}
)
const myCustomResource = new MyCustomComponentResource(
{},
{ provider: awsProvider, parent: awsProvider }
)
// file2.ts
export class MyCustomComponentResource extends pulumi.ComponentResource{
constructor(
args: {},
opts?: pulumi.ComponentResourceOptions | undefined
) {
super('resource-type', 'resource-name', {}, opts)
// how to correctly access here the parent provider config if setConfig has not been called?
// I could pass here the aws provider config as an argument, but it doesn't seem like the intended way to access these values
}
}
billowy-army-68599
06/18/2021, 10:01 AMbored-activity-40468
06/18/2021, 12:58 PMregister_stack_transformation
regardless of language be used to change the resource's name? I'm guessing no but want to verify.brash-kite-78002
06/18/2021, 1:45 PMfull-island-88669
06/18/2021, 2:32 PMERROR: Could not find a version that satisfies the requirement grpcio==1.38.0
But locally, there is no such problembright-stone-12333
06/18/2021, 6:32 PMfreezing-sugar-4269
06/18/2021, 8:30 PMfreezing-sugar-4269
06/18/2021, 8:30 PMfaint-table-42725
06/19/2021, 1:52 AMfreezing-sugar-4269
06/19/2021, 3:58 AM