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

Add --team flag to fly destroy-pipeline command #5924

Merged
merged 1 commit into from
Jul 30, 2020

Conversation

khng
Copy link
Contributor

@khng khng commented Jul 30, 2020

Allow for users to destroying pipelines for different teams
without switching targets

#5215

Signed-off-by: Ka Hin Ng [email protected]

What does this PR accomplish?

Feature

Changes proposed by this PR:

  • Add --team flag for fly destroy-pipeline command.

Notes to reviewer:

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).

@khng khng force-pushed the destroy-pipeline-team-command branch 2 times, most recently from bb3d8de to 781b9ea Compare July 30, 2020 00:58
@khng khng changed the title fly: behaviour: add team option to destroy-pipeline command fly: add team option to destroy-pipeline command Jul 30, 2020
Copy link
Contributor

@aoldershaw aoldershaw left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution! Looks great, and works exactly as I'd expect.

One small thing - could you remove your release note from release-notes/latest.md? There's currently a merge conflict. I would normally suggest just rebasing onto master, but we're actually changing our release note process to have the release notes auto generated by the PRs that were merged into master - so, having a release note in release-notes/latest.md actually has no effect!

By default, the release note is just the PR title (along with your GitHub username). If you want to add more context to your PR in the release note, you could add a ## Release Note header to your PR description and put whatever markdown under there - but I think your PR title is pretty descriptive already!

Allow for users to destroying pipelines for different teams
without switching targets

concourse#5215

Signed-off-by: Ka Hin Ng <[email protected]>
@khng khng force-pushed the destroy-pipeline-team-command branch from 781b9ea to ecd4b78 Compare July 30, 2020 13:56
@khng
Copy link
Contributor Author

khng commented Jul 30, 2020

Thanks for taking a look!

I have removed the release note change. I'll make note of that for future PRs! :)

@khng khng requested a review from aoldershaw July 30, 2020 15:53
@khng
Copy link
Contributor Author

khng commented Jul 30, 2020

On a side note, should I be able to view the details of the checks?

@aoldershaw
Copy link
Contributor

aoldershaw commented Jul 30, 2020

@khng thanks!

On a side note, should I be able to view the details of the checks?

We have a PR bot that should invite anyone who opens a PR to the concourse/contributors team (which has access to the checks), though I think it's been misbehaving as of late. I'll invite you manually for now.

Looks like the test just timed out (been seeing that a bit more recently, should probably look into that...) - I retriggered it, hopefully it'll pass this time around! Doesn't seem related to your change

@aoldershaw aoldershaw merged commit 3857c0d into concourse:master Jul 30, 2020
@khng khng deleted the destroy-pipeline-team-command branch July 31, 2020 01:28
@aoldershaw aoldershaw changed the title fly: add team option to destroy-pipeline command Add --team option to fly destroy-pipeline command Aug 18, 2020
@aoldershaw aoldershaw changed the title Add --team option to fly destroy-pipeline command Add --team flag to fly destroy-pipeline command Aug 18, 2020
@aoldershaw aoldershaw added the release/undocumented This didn't warrant being documented or put in release notes. label Aug 18, 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

2 participants