icy-controller-6092
10/01/2023, 1:59 AMbrave-lizard-56518
10/09/2023, 5:29 PMbrash-solstice-49151
10/10/2023, 1:53 PMdry-sugar-28823
10/12/2023, 8:40 AMbrash-solstice-49151
10/13/2023, 9:13 AMpublic class MyStack : Stack
{
[Input(nameof(MyInput)]
public string MyInput {get; set;}
public MyStack()
{
// use MyInput when declaring a resource
}
}
All C# if it wasn't clear. Is this possible, or am I stuck to using config by calling SetConfigAsync
?brash-solstice-49151
10/16/2023, 11:18 AMnamespace:key[0].property
but not having any luck so far 😕bored-activity-40468
10/18/2023, 3:41 PMWorkspace.InstallPluginAsync
not required? I I added the TLS provider to some code and forgot to add it to my bit that calls InstallPluginsAsync
but it was downloaded to .plugins
for me.brash-solstice-49151
10/18/2023, 3:55 PMGetOutputsAsync()
then passing those to the config of the inline program, but I'd like to clean things up and make the inline program re-useable with the CLI should I need direct pulumi CLI access. Any ideas what the error might be?curved-morning-41391
10/23/2023, 10:17 PMcurved-morning-41391
10/24/2023, 10:14 PMbrash-solstice-49151
10/30/2023, 2:29 PMproud-pizza-80589
11/06/2023, 3:55 PM<@UDNQQGNJF>/pulumi/cmd/dynamic-provider
. Weirdly enough this is backend dependent. Using cloud it works, but on an s3 backend it does not. Only difference between the code is adding this to the createOrSelectStack. Any idea's on the cause (or the solution obviously ;))
projectSettings: {
name: `bpaas`,
runtime: `nodejs`,
backend: {
url: `<s3://xxx-xxxx-xxxxx?region=eu-central-1>`,
},
},
little-apartment-7708
11/13/2023, 9:42 AM--config-file
and it is workingbrash-finland-19802
11/15/2023, 9:34 PMcolossal-vr-62639
11/22/2023, 9:12 AMpublic Output<MyPoco[]> Items {get;set;}
I see the following error when running a preview
System.InvalidOperationException: [Output] Items contains invalid type Item[]. Allowed types are:
String, Boolean, Int32, Double,
proud-pizza-80589
11/24/2023, 4:00 PMhigh-kilobyte-6384
12/04/2023, 6:47 AMhigh-kilobyte-6384
12/07/2023, 10:00 AMawait stack.workspace.stack()
, and the result indicates that updateInProgress
is false. However, when I execute await stack.up()
, it fails. The output states that "the stack is currently locked by 1 lock(s)".high-kilobyte-6384
12/07/2023, 10:01 AMsparse-intern-71089
12/08/2023, 12:17 AMfew-electrician-82432
12/08/2023, 5:32 PMicy-controller-6092
12/08/2023, 11:54 PMlocal.Command
usage to manage custom resources that aren't supported by existing plugins, e.g. deploying a schema to a schema registry
I have a lot of micro-stacks, and sometimes the existing resources are no longer applicable if I remove a service from the cluster - but the micro-stacks may still have resources from that service in their state, e.g.
new local.Command('xyz', {
delete: 'curl --fail -X DELETE <http://some.retired.service.local/...>'
})
If you retire the service before removing the resource from the state of every mini-stack, following deployments will fail because the delete command fails. To solve this, I've started using migration scripts to stack.exportStack()
-> manual modifications -> stack.importStack(newState)
which can be used to manually filter out resources from state.deployment.resources
worried-helmet-23171
01/17/2024, 11:10 AMaloof-doctor-77911
01/19/2024, 2:37 PMpulumi login s3://
command in the code ?aloof-doctor-77911
01/23/2024, 5:50 AMlimited-window-74907
01/25/2024, 12:00 AMpulumi login
(to Pulumi Cloud) via the automation API? I have a use case where I sometimes am using Pulumi Cloud and sometimes S3, code in threadancient-solstice-53934
02/05/2024, 7:30 PMdazzling-salesclerk-51689
02/26/2024, 10:52 AMpulumi automation API
to create resources on GCP and AWS.
There is a daily cron that triggers pulumi execution - there are about 15 stacks that being executed one by one.
Typescript code, pulumi version v3.107.0
We see two troubling behaviors:
1. Silent failures
a. The code is doing stack.refresh()
and stack.up()
afterwards
b. Statistically and without any recognized pattern, either one of the above actions can simply stop without throwing an error.
c. The side-effect is the lock file isn’t being deleted, thus leaving the stack locked.
d. It’s very hard to reproduce, as locally, per stack execution, we see it running as expected.
e. Are you familiar with such a behavior? What can cause that?
2. Aggressive crashes
a. Sometimes, we see many errors like failed to register new resource X: Resource monitor is terminating
b. The above errors cannot be caught which in turn, crash the microservice completely
c. We saw on Github a PR that meant to prevent this behavior. Around 2 months ago there was a change that might affected this behavior (line 522). I’m not sure.
d. What can cause the resource monitor to fail registering resources in the first place?
e. Are you aware of such situation?
Thanks!
@crooked-cat-6983, @dazzling-salesclerk-51689adamant-advantage-14270
03/07/2024, 2:22 PM# code here
_up = stack.up(on_output=print, color='always', target=target)
#output here
@ updating.......
pulumi:providers:kubernetes render-yaml-gateway-partners
gcp:storage:Bucket bananabucket
gcp:compute:Address proxy-xlb-static-ip-partners
gcp:compute:RegionUrlMap xlb-proxy-partners-http
brash-solstice-49151
03/18/2024, 11:41 AMpulumi refresh
, not necessarily tied directly to Automation API, but it is the context that we're currently working in. I've raised an issue on the .NET repo (https://github.com/pulumi/pulumi-dotnet/issues/244) now that the --preview-only
flag is available via the CLI, but not yet for .NET. It's raised some questions internally in my workplace as to how pulumi refresh
should fit into the workflow of stack updates. It's not super clear to us how best to manage state drift (auto apply, expect no changes etc), so if anyone else has come across something similar, I'd be super keen to hear how you are incorporating it.