-
Notifications
You must be signed in to change notification settings - Fork 85
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
Feature Request: Full support for environments #250
Comments
Thanks @fmms for reaching out. We are already working on such an enhancement as you might have seen here: Azure/data-product-streaming#86 This enhancement will include deploy pipelines to Any other feedback or expectations from your side regarding the pipelines? |
We would like to move towards workflow templates to fully showcase this, but sadly, this will break all workflows as soon as users fork the repo because of this https://github.community/t/ref-head-in-reusable-workflows/203690/22 I will work on repository templates itself for the time being to simplify this for customers. |
Hello, |
Looking at the current solution and the documentation that I have seen so far, the handling of environments is not yet clear for me.
The repo contains
params.<env>.json
fordev
,test
,prod
.Describe the solution you'd like
I would hope for a build pipeline to build the code on any commit and creating an artifact and then a release pipeline that deploys this release to certain environments.
Did I miss any documentation or idea in the code so far?
The text was updated successfully, but these errors were encountered: