I m struggling with handing outputs I have `const proj = new

Question

I m struggling with handing outputs I have `const proj = new gitlab Project ` and I want to get `proj id` to use in a string literal typescript The documentation seems to be indicating that I can do this `console log proj id apply v = gt `$ v ` ` however it doesn t like it

bored-oyster-3147 · Answer

Outputs work like promises So the following code `Output lt string gt apply v = gt $ v ` would return `Output lt string gt ` The same way that `Promise lt string gt then v = gt $ v ` returns `Promise lt string gt ` If you need to interpolate it into a string literal then your literal needs to be part of the promise `var result = proj id apply id = gt My project ID is $ id ` now `result` is `Output lt string gt ` and your `proj id` has been interpolated and can be passed to an `Input lt string gt `

tall-beard-99429 · Answer

Ah I want to be able to use the string as part of the name of a future task

tall-beard-99429 · Answer

```new gitlab BranchProtection `BranchProtection $ proj id $ project defaultBranch ` ```

tall-beard-99429 · Answer

and the names don t take `Input lt string gt `

bored-oyster-3147 · Answer

you cannot do that

bored-oyster-3147 · Answer

nor should you

tall-beard-99429 · Answer

How should I name these then I have ~ 50 git repos being configured with pulumi for each of those there may be ~2 3 branches that need configuring the project ID and branch name was a way to give these a unique identifier

bored-oyster-3147 · Answer

well you know what the branch is and you have a name that you already provided to `gitlab Project` so why not ` projectName branchprotection branchName `

tall-beard-99429 · Answer

Project names aren t guaranteed to be unique a project ID is

tall-beard-99429 · Answer

Actually I do have a unique name for it since i use a name for `new gitlab Project `

bored-oyster-3147 · Answer

a pulumi name must be unique for a given stack so how could the name you provided to `new gitlab Project name ` not be unique

tall-beard-99429 · Answer

Hmm okay i ll do that thanks

bored-oyster-3147 · Answer

yea that s what I was getting at

tall-beard-99429 · Answer

Is there a way to make it only run the `delete` or to at least run them first

tall-beard-99429 · Answer

Currently its failing a lot of the create steps

bored-oyster-3147 · Answer

so by default for a `replace` action pulumi does `create new delete old` but for some types of resources that have unique constraints that default behavior doesn t work so you set `deleteBeforeReplace true` in the resource options which makes a `replace` action do `delete current create new`

bored-oyster-3147 · Answer

There are scenarios where it may be dangerous to set that so the default is what it is for a reason But for instance like a pulumi controlled DNS record or something needs to be deleted first before the new one can be created since there can only be 1 with a certain value

bored-oyster-3147 · Answer

You might need to do a `destroy` first though since you are actually changing the pulumi names of theses resources so pulumi no longer sees them as the same entity and thus is doing the create and destroy separately

bored-oyster-3147 · Answer

Or if you can t do a full destroy because you don t want to destroy other resources you would comment out the resources whose names you are changing and then run a `pulumi up` so that it deletes them first since they are no longer declared then uncomment them with the new names

bored-oyster-3147 · Answer

Or alternatively you could use pulumi aliases and make the old name an alias and it wouldn t need to recreate them at all

tall-beard-99429 · Answer

I ended up going with commenting out But aliases are a good one to know do they accept Input lt String gt as a value otherwise i d have the same problem correct

bored-oyster-3147 · Answer

I believe they do but I don t think that would do anything for you

bored-oyster-3147 · Answer

it s just a pulumi name so the only reason you would use them is if the old pulumi name needed to be changed so it doesn t really make sense to make aliases pre emptively IMO they would have no function