[Request]: Deploy service without Pipeline

zbintliff commented 3 years ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request Deploy a service template (and service) with no pipeline definition.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Working my way through different tutorials trying to replicate a complicated example. My base case is just using the service templates to deploy an ALB and see how powerful the specs and schema can go without having to worry about container definitions. I don't expect any pipeline other than the infrastructure/cloudformation.yaml to be created when I deploy a service. (similar to how environments are handled)

Are you currently working around this issue? I will look into a noop pipeline but the documentation there is very thin.

zbintliff commented 3 years ago

Now that I think about it. Maybe the better request would be a "default" pipeline that follows the same steps as creating an environment?

If I'm misunderstanding something please let me know.

zbintliff commented 3 years ago

I think this is required so I created an "empty" CFN template (same thing I did for importing an environment)

AWSTemplateFormatVersion: '2010-09-09'
Description:  Empty Pipeline that is required
Conditions:
  AlwaysFalse: !Equals
    - true
    - false
Resources:
  EmptyResource:
    Type: "Custom:EmptyResource"
    Condition: AlwaysFalse

rafavallina commented 3 years ago

Thanks for the input @zbintliff! Indeed we intend to remove this restriction. We kept it in for the initial Preview release as we expect people to try the full end-to-end experience of using the service, which includes a pipeline, but it's overly restrictive.

rafavallina commented 3 years ago

This is now live https://aws.amazon.com/about-aws/whats-new/2021/03/aws-proton-supports-services-without-pipelines/

radolang commented 2 years ago

Are there any examples out there in terms of using proton without a popieline? We would like to deploy a Java service using Fargate but without building jar/war files. Could we just get the artifacts from artifactory? Any guidance would be appreciated.

rafavallina commented 2 years ago

@radolang Just to be clear, Proton allows you to create services without pipelines but you will still need a mechanism to make deployments that builds the code, generates a deployment artifact, and triggers the deployment. Being able to use Proton without pipelines means that Proton will not be provisioning a pipeline as part of service creation - leaving the provisioning and managing of the pipeline to the customer

aws / aws-proton-public-roadmap

[Request]: Deploy service without Pipeline #34

Community Note