Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to set cloud endpoint name #504

Closed
mikhailshilkov opened this issue Jun 3, 2018 · 3 comments
Closed

Ability to set cloud endpoint name #504

mikhailshilkov opened this issue Jun 3, 2018 · 3 comments
Assignees
Labels
kind/enhancement Improvements or new features resolution/wont-fix This issue won't be fixed
Milestone

Comments

@mikhailshilkov
Copy link
Member

mikhailshilkov commented Jun 3, 2018

Looking at e.g. hello-aws-javascript template, endpoint.get syntax is nice but it doesn't seem to expose a property to set explicit name for created Lambda. So, the name will always have a random suffix - similar to hello66382ec5.

I would like to be able to set the name, e.g.

endpoint.get(
    { path: "/source", name: "hellofunc" }, 
    (req, res) => res.json({name: "AWS"})
);

(The exact API is up to you to figure out.)

While I understand that you try to keep things as simple as possible, I don't feel very good about having many meaningless names in Cloud account.

My company has explicit policy of naming cloud resources. It also includes properties like description, tags etc. Not being able to follow it could be a showstopper. We are in Azure, but that shouldn't matter much.

@lukehoban
Copy link
Member

This is important, but will require a large set of changes to all components in the cloud package. Since we have several other things we will likely do as part of a large cross cutting change like this, we'll hold off on this until we can do a redesign of the API surface that takes this into consideration.

@lukehoban lukehoban modified the milestones: 0.19, 0.21 Nov 20, 2018
@lukehoban lukehoban removed this from the 0.21 milestone Jan 28, 2019
@CyrusNajmabadi CyrusNajmabadi removed their assignment Jan 8, 2020
@infin8x infin8x added kind/enhancement Improvements or new features and removed kind/feature labels Jul 10, 2021
@chicagobuss
Copy link

uh, 5 years and nothing on this? Is there any way to set my GCP resource names explicitly? This is extremely important in a few specific areas like database names when you're managing hundreds of databases - you don't want each instance to have a different unique database name.

@lukehoban
Copy link
Member

@chicagobuss This issue is about the @pulumi/pulumi-cloud package, which is a preview package for multi-cloud container/serverless applications built on top of Pulumi. It sounds like you are referring to a different issue/need related to the pulumi-gcp library? You can in general explicitly name your resources by passing the name property to them (though the name of that property may depend on the resource in some cases). If you cannot identify the right property to use to explicitly name your resource, you can open an issue in that repo or ask in the Pulumi Community Slack.

@mjeffryes mjeffryes added the resolution/wont-fix This issue won't be fixed label Jun 28, 2024
@mjeffryes mjeffryes self-assigned this Jun 28, 2024
@mjeffryes mjeffryes added this to the 0.107 milestone Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/wont-fix This issue won't be fixed
Projects
None yet
Development

No branches or pull requests

7 participants