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

Feature Request: Full support for environments #250

Open
fmms opened this issue Dec 8, 2021 · 3 comments
Open

Feature Request: Full support for environments #250

fmms opened this issue Dec 8, 2021 · 3 comments
Assignees
Labels
backlog Backlog item feature Feature Requests
Milestone

Comments

@fmms
Copy link

fmms commented Dec 8, 2021

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 for dev, 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?

@fmms fmms added the feature Feature Requests label Dec 8, 2021
@marvinbuss
Copy link
Collaborator

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 test and prod environments. Once this is done for one repository, we will implement the same across all the other repositories. We will close this once this is merged.

Any other feedback or expectations from your side regarding the pipelines?

@marvinbuss marvinbuss added this to the v1.3.0 milestone Dec 8, 2021
@marvinbuss marvinbuss added the committed Committed item label Dec 8, 2021
@marvinbuss marvinbuss added backlog Backlog item and removed committed Committed item labels Dec 23, 2021
@marvinbuss
Copy link
Collaborator

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
Once this gets fixed, we will add this.

I will work on repository templates itself for the time being to simplify this for customers.

@MiguelElGallo
Copy link

Hello,
Any news on this?
We need this and we are wondering if we start something, or we wait :)
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Backlog item feature Feature Requests
Projects
None yet
Development

No branches or pull requests

3 participants