anyone have success in using the `aliases` feature to move a

Question

anyone have success in using the `aliases` feature to move a resource from one child library to another

little-cartoon-10569 · Answer

Library Aliases allow effective repositioning within state It s not related to libraries modules classes or similar

little-cartoon-10569 · Answer

Yes I ve used `aliases` to move resource within state It s an effective remediation for planning after the fact slightly smiling face

little-cartoon-10569 · Answer

Which I do all too often

elegant-crayon-4967 · Answer

yes in state but referencing imported libraries is what I mean

elegant-crayon-4967 · Answer

trying to change the parent of an s3 bucket Work is done in a separate library that I m linking locally

elegant-crayon-4967 · Answer

I tried referencing by urn directly parent name and nothing

little-cartoon-10569 · Answer

Importing from libraries doesn t overlap the problem domain that aliases solve as far as I can tell

little-cartoon-10569 · Answer

If the resource isn t moving between state files you don t need to any import related stuff And if it s not moving within the state s hierarchy of resources you don t need to do any aliasing

little-cartoon-10569 · Answer

You can move the code into a new location in your code including to new libraries and if the resource remains in the same place in the state i e same parent resource then you don t need to do anything

elegant-crayon-4967 · Answer

removing any library from conversation a simplified attempt

elegant-crayon-4967 · Answer

``` aliases name `$ config autoscalingConfig autoscalingGroupConfig name codedeploy bucket` ```

elegant-crayon-4967 · Answer

that s the change I made to an existing bucket

elegant-crayon-4967 · Answer

previously it was ` parent codeDeploy `

elegant-crayon-4967 · Answer

my goal is to just to remove the parent pulumi wants to destroy and create the bucket

elegant-crayon-4967 · Answer

so I m clearly not using the aliases correctly

little-cartoon-10569 · Answer

Ah So what you need is to find the old URN under codeDeploy which you can do by searching the output of `pulumi stack show urns`

elegant-crayon-4967 · Answer

I shouldn t have to use the urn though

elegant-crayon-4967 · Answer

and I tried the urn previously with no luck

elegant-crayon-4967 · Answer

I might be on to something here adding the old name AND old parent might work

little-cartoon-10569 · Answer

Yes you don t need to it s just a habit I use to ensure I get the right name since I have often renamed a resource at the same time as moving it which I probably shouldn t

little-cartoon-10569 · Answer

Yes the more info you put into the alias description the better The docs explain what the properties are for <https www pulumi com docs reference pkg nodejs pulumi pulumi Alias>

little-cartoon-10569 · Answer

The name in the alias is obviously the old name not the current new name

little-cartoon-10569 · Answer

I have got that wrong in the past

little-cartoon-10569 · Answer

And that s where show urns is helpful

elegant-crayon-4967 · Answer

yea I can t really use the URN outside of troubleshooting because that s where the library comes in It s used in multiple projects so the dependent repo s will have different S3 Bucket URNS

little-cartoon-10569 · Answer

If you re moving the code into a library and therefore the code will now be used when creating multiple resources where before it was creating one then I think aliasing isn t appropriate

little-cartoon-10569 · Answer

You might be better off importing it s a messy solution requiring at least 2 calls to `pulumi up` but it should get your state in better shape

elegant-crayon-4967 · Answer

so I ended up figuring it out by specifying the name and the parent urn needing both of those

elegant-crayon-4967 · Answer

thanks for the help

elegant-crayon-4967 · Answer

luckily the urn name is consistent so I just manipulated that to work with proper string interpolation so it s universal