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

Make it easy to add a custom domain to HttpEndpoint and cloud.Service #462

Closed
lindydonna opened this issue Apr 17, 2018 · 2 comments
Closed
Assignees
Labels
kind/enhancement Improvements or new features resolution/wont-fix This issue won't be fixed

Comments

@lindydonna
Copy link
Contributor

Per @chrsmith's feedback here:

  • In the pulumi-cloud suite of packages, can we make it easy to create cloud.Service and cloud.HttpEndpoint that is served from a user-controlled domain. This means providing ways to configure the load balancer, DNS, and maybe certificates in a "as much as possible" cloud provider agnostic manner.

This isn't a critical improvement, so I'm just assigning to M16. But, it may be useful to consider the scenario as part of the current design work.

@lindydonna lindydonna added this to the 0.16 milestone Apr 17, 2018
@lukehoban lukehoban modified the milestones: 0.16, 0.18 Jul 12, 2018
@lukehoban lukehoban modified the milestones: 0.18, 0.20 Sep 12, 2018
@c0bra
Copy link

c0bra commented Oct 19, 2018

After having just gone through creating a service at AWS, this would be very handy. Especially being able to stand up an ALB automatically with routing so you don't have to be running a separate balancer per service at $16/mo.

@lukehoban lukehoban modified the milestones: 0.20, 0.22 Dec 6, 2018
@lukehoban
Copy link
Member

We are adding AWS-specific libraries for working with ECS Services and APIGateways as part of pulumi/pulumi-awsx#53. In the near term, those will offer greater flexibility to control details like this for users who are working with AWS. We'l continue to think about how to add cross-cloud support for this as part of the cloud package.

@lukehoban lukehoban removed this from the 0.22 milestone Mar 17, 2019
@infin8x infin8x added kind/enhancement Improvements or new features and removed kind/feature labels Jul 10, 2021
@mjeffryes mjeffryes added the resolution/wont-fix This issue won't be fixed label Jun 28, 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

5 participants