This message was deleted.

is the value exported in Pulumi?

im not sure what you mean, the value is known at the time

pulumi up

is called and I need to get it into the stack

are you calling e.g.

export("build.id", build_id)

in the other stack?

there is no other stack

ah okay, where do you fetch the build id?

the pipeline provides the build id, and the pipeline calls

pulumi up

so the pipeline needs to pass it in. I want to avoid using environment variables because we have plans to migrate to automation API and environment variables do not make sense there. I've been trying to get something like this to work:

internal class MyStack : Stack
{
    [NotNull]
    [Input(nameof(BuildNumber), required: true)]
    public Input<string>? BuildNumber { get; set; }

    public MyStack()
    {
        // use build number here
    }
}

the way that you would do it in other resources but it doesn't appear like that is checked, and I wouldn't know how to pass it to

pulumi up

. So I'm trying to figure out what the pattern should be / is supposed to be

I think you can use

pulumi up -c

hmmm that's config, do you know if that extends existing config or replaces?

probably replaces

it is! I was reading it earlier and actually just commented. Yea it seems runtime inputs are only possible via environment variables currently which seems like a major hole to me