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 Isolation Segment #2335

Merged
merged 4 commits into from
Oct 21, 2022
Merged

Add Isolation Segment #2335

merged 4 commits into from
Oct 21, 2022

Conversation

moleske
Copy link
Member

@moleske moleske commented Oct 19, 2022

  • Allows tests that rely on an isolation segment being available to run

Thank you for contributing to the CF CLI! Please read the following:

  • Please make sure you have implemented changes in line with the contributing guidelines
  • We're not allowed to accept any PRs without a signed CLA, no matter how small.
    If your contribution falls under a company CLA but your membership is not public, expect delays while we confirm.
  • All new code requires tests to protect against regressions.
  • Contributions must be made against the appropriate branch. See the contributing guidelines
  • Contributions must conform to our style guide. Please reach out to us if you have questions.

Does this PR modify CLI v6, CLI v7, or CLI v8?

This is only for github integration test configuration

Please see the contribution doc above or review Architecture Guide.

Description of the Change

Add isolation segment for testing

We must be able to understand the design of your change from this description.
Keep in mind that the maintainer reviewing this PR may not be familiar with or
have worked with the code here recently, so please walk us through the concepts.

Why Is This PR Valuable?

Cause the tests will actually have all the pre reqs to run

What benefits will be realized by the code change? What users would want this change? What user need is this change addressing?

Why Should This Be In Core?

n/a

Explain why this functionality should be in the cf CLI, as opposed to a plugin.

Applicable Issues

List any applicable Github Issues here

How Urgent Is The Change?

as fast as we want integration tests to work

Is the change urgent? If so, explain why it is time-sensitive.

Other Relevant Parties

@cloudfoundry/wg-app-runtime-interfaces-cli-approvers
@cloudfoundry/wg-app-runtime-interfaces-cli-reviewers
Who else is affected by the change?

- Allows tests that rely on an isolation segment being available to run
@moleske
Copy link
Member Author

moleske commented Oct 19, 2022

integration test didn't run because we ignore the .github directory in prs/pushes https://github.com/cloudfoundry/cli/blob/master/.github/workflows/integration.yml#L12

Maybe we shouldn't ignore it?

@a-b a-b requested review from a-b and a team and removed request for a team October 20, 2022 17:37
Since we can't manually trigger GHA on remote branch from PR.

Co-authored-by: Michael Oleske <moleske@pivotal.io>
@moleske
Copy link
Member Author

moleske commented Oct 20, 2022

Marking as ready since I tested manually against a claimed environment

@moleske moleske marked this pull request as ready for review October 20, 2022 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants