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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

concourse#5215 fly: add --team flag to set-pipelines #5805

Merged
merged 2 commits into from
Jul 2, 2020
Merged

concourse#5215 fly: add --team flag to set-pipelines #5805

merged 2 commits into from
Jul 2, 2020

Conversation

muang0
Copy link
Contributor

@muang0 muang0 commented Jun 24, 2020

document DCO process

Signed-off-by: jroden [email protected]

What does this PR accomplish?

Feature

closes # .

Changes proposed by this PR:

Currently the only way for users to set pipelines from different teams with Fly is to create multiple targets. With this addition users can now set pipelines against different teams within a target. This is part of the #5215 checklist.

Notes to reviewer:

First time contributor here, thanks for the help! 馃槃 Pretty straightforward addition code-wise. For testing, can run the specific ginkgo case as needed with ginkgo --focus='when setting new pipeline with non-default team'

Contributor Checklist

Reviewer Checklist

  • Code reviewed
  • Tests reviewed
  • Documentation reviewed
  • Release notes reviewed
  • PR acceptance performed
  • New config flags added? Ensure that they are added to the
    BOSH and
    Helm packaging; otherwise, ignored for
    the integration
    tests

    (for example, if they are Garden configs that are not displayed in the
    --help text).

@xtremerui
Copy link
Contributor

Hi thx for the PR. Could you add a release note for this feature?

@muang0
Copy link
Contributor Author

muang0 commented Jun 30, 2020

Just added, good catch! 馃槃

document DCO process

Signed-off-by: jroden <[email protected]>
@muang0
Copy link
Contributor Author

muang0 commented Jul 2, 2020

Rebased commits, added DCO 馃槄

@xtremerui
Copy link
Contributor

@jroden there is conlict in release-notes

@muang0
Copy link
Contributor Author

muang0 commented Jul 2, 2020

Just merged upstream to resolve the conflict-- let me know if there's anything else. Thanks!

Copy link
Contributor

@xtremerui xtremerui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@xtremerui xtremerui merged commit 3e49ee9 into concourse:master Jul 2, 2020
@xtreme-sameer-vohra xtreme-sameer-vohra added the release/undocumented This didn't warrant being documented or put in release notes. label Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement release/undocumented This didn't warrant being documented or put in release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants