Add 'src/code.cloudfoundry.org/routing-acceptance-tests/' from commit…

… '75c688127fdf0f8b7fed76ae89116b0c7fb5ef8b'

git-subtree-dir: src/code.cloudfoundry.org/routing-acceptance-tests
git-subtree-mainline: 1c21156
git-subtree-split: 75c6881

src/code.cloudfoundry.org/routing-acceptance-tests/.github/CONTRIBUTING.md

@@ -0,0 +1,58 @@
+Contributor License Agreement
+---------------
+
+Follow these steps to make a contribution to any of our open source repositories:
+
+1. Ensure that you have completed our CLA Agreement for [individuals](https://www.cloudfoundry.org/wp-content/uploads/2015/07/CFF_Individual_CLA.pdf) or [corporations](https://www.cloudfoundry.org/wp-content/uploads/2015/07/CFF_Corporate_CLA.pdf).
+
+1. Set your name and email (these should match the information on your submitted CLA)
+  ```
+  git config --global user.name "Firstname Lastname"
+  git config --global user.email "your_email@example.com"
+  ```
+
+1. All contributions must be sent using GitHub pull requests as they create a nice audit trail and structured approach.
+
+The originating github user has to either have a github id on-file with the list of approved users that have signed
+the CLA or they can be a public "member" of a GitHub organization for a group that has signed the corporate CLA.
+This enables the corporations to manage their users themselves instead of having to tell us when someone joins/leaves an organization. By removing a user from an organization's GitHub account, their new contributions are no longer approved because they are no longer covered under a CLA.
+
+If a contribution is deemed to be covered by an existing CLA, then it is analyzed for engineering quality and product
+fit before merging it.
+
+If a contribution is not covered by the CLA, then the automated CLA system notifies the submitter politely that we
+cannot identify their CLA and ask them to sign either an individual or corporate CLA. This happens automatically as a
+comment on pull requests.
+
+When the project receives a new CLA, it is recorded in the project records, the CLA is added to the database for the
+automated system uses, then we manually make the Pull Request as having a CLA on-file.
+
+
+Initial Setup
+---------------
+- A running deployment of [routing-release](https://github.com/cloudfoundry/routing-release)
+
+- The latest version of the [rtr CLI](https://github.com/cloudfoundry/routing-api-cli/releases)
+
+- Add required directories
+
+```bash
+# create parent directory
+mkdir -p ~/workspace
+cd ~/workspace
+
+# clone ci
+git clone https://github.com/cloudfoundry/wg-app-platform-runtime-ci.git
+
+# clone repo
+git clone https://github.com/cloudfoundry/routing-release.git --recursive
+cd routing-release
+```
+
+Running Acceptance Tests
+---------------
+
+Set an environment variable `CONFIG` which points to a `.json` file that contains the router api endpoint. Check out [Usage](../docs/01-usage.md) for learning how to generate one.
+
+`CONFIG=<PATH-TO-CONFIG-JSON> ./bin/test.bash`: This will run all tests against a CF installation
+

src/code.cloudfoundry.org/routing-acceptance-tests/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+- name: CloudFoundry slack
+  url: https://cloudfoundry.slack.com
+  about: For help or questions about this component, you can reach the maintainers on Slack

src/code.cloudfoundry.org/routing-acceptance-tests/.github/ISSUE_TEMPLATE/issue-bug.yml

@@ -0,0 +1,42 @@
+name: Bug
+description: Report a defect, such as a bug or regression.
+title: "Start the title with a verb (e.g. Change header styles). Use the imperative mood in the title (e.g. Fix, not Fixed or Fixes header styles)"
+labels:
+  - bug
+body:
+  - type: textarea
+    id: current
+    attributes:
+      label: Current behavior
+    validations:
+      required: true
+  - type: markdown
+    id: current_md
+    attributes:
+      value: |
+        - Explain, in detail, what the current state of the world is
+        - Include code snippets, log output, and analysis as necessary to explain the whole problem
+        - Include links to logs, GitHub issues, slack conversations, etc.. to tell us where the problem came from
+        - Steps to reproduce
+  - type: textarea
+    id: desired
+    attributes:
+      label: Desired behavior
+    validations:
+      required: true
+  - type: markdown
+    id: desired_md
+    attributes:
+      value: |
+        - Describe how the problem should be fixed 
+        - Does this require a new bosh release?
+        - Does it require configuration changes in cf-deployment?
+        - Do we need to have a special release note?
+        - Do we need to update repo documentation?
+  - type: input
+    id: version
+    attributes:
+      label: Affected Version
+      description: Please enter the version
+    validations:
+      required: true

src/code.cloudfoundry.org/routing-acceptance-tests/.github/ISSUE_TEMPLATE/issue-enhance.yml

@@ -0,0 +1,50 @@
+name: Enhance
+description: Propose an enhancement or new feature.
+title: "Start the title with a verb (e.g. Change header styles). Use the imperative mood in the title (e.g. Fix, not Fixed or Fixes header styles)"
+labels:
+  - enhancement
+body:
+  - type: textarea
+    id: change
+    attributes:
+      label: Proposed Change
+    validations:
+      required: true
+  - type: markdown
+    id: change_md
+    attributes:
+      value: |
+        Briefly explain why this feature is necessary in the following format
+
+        **As a** *developer/operator/whatever*
+        **I want** *this ability to do X*
+        **So that** *I can do Y*
+
+        - Provide details of where this request is coming from including links, GitHub Issues, etc..
+        - Provide details of prior work (if applicable) including links to commits, github issues, etc...
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+    validations:
+      required: true
+  - type: markdown
+    id: acceptance_md
+    attributes:
+      value: |
+        Detail the exact work that is required to accept this story in the following format
+
+        **Scenario:** *describe scenario*
+        **Given** *I have some sort of configuration*
+        **When** *I do X*
+        **And** *do Y*
+        **Then** *I see the desired behavior*
+
+  - type: textarea
+    id: related
+    attributes:
+      label: Related links
+      description: Please list related links for this issue
+      placeholder: |
+        - [ ] code.cloudfoundry.org/bbs for links
+        - [x] cloudfoundry/rep#123 for issues/prs

src/code.cloudfoundry.org/routing-acceptance-tests/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+- [ ] Read the [Contributing document](../blob/-/.github/CONTRIBUTING.md).
+
+Summary
+---------------
+<!---
+- Briefly explain why this PR is necessary
+- Provide details of where this request is coming from including links, GitHub Issues, etc..
+- Provide details of prior work (if applicable) including links to commits, github issues, etc...
+--->
+
+
+Backward Compatibility
+---------------
+Breaking Change? **Yes/No**
+<!---
+If this is a breaking change, or modifies currently expected behaviors of core functionality
+
+- Has the change been mitigated to be backwards compatible?
+- Should this feature be considered experimental for a period of time, and allow operators to opt-in?
+- Should this apply immediately to all deployments?
+-->

src/code.cloudfoundry.org/routing-acceptance-tests/.github/TEMPLATE-README.md

@@ -0,0 +1,11 @@
+
+> [!IMPORTANT]
+> Content in this directory is managed by the CI task `sync-dot-github-dir`.
+
+Changing templates
+---------------
+These templates are synced from [these shared templates](https://github.com/cloudfoundry/wg-app-platform-runtime-ci/tree/main/shared/github).
+Each pipeline will contain a `sync-dot-github-dir-*` job for updating the content of these files.
+If you would like to modify these, please change them in the shared group.
+It's also possible to override the templates on pipeline's parent directory by introducing a custom
+template in `$PARENT_TEMPLATE_DIR/github/FILENAME`  or `$PARENT_TEMPLATE_DIR/github/REPO_NAME/FILENAME` in CI repo

src/code.cloudfoundry.org/routing-acceptance-tests/.gitignore

@@ -0,0 +1,6 @@
+*_config.json
+*.config
+results
+*.test
+*config.json
+.idea

src/code.cloudfoundry.org/routing-acceptance-tests/CODEOWNERS

@@ -0,0 +1 @@
+* @cloudfoundry/wg-app-runtime-platform-networking-approvers

src/code.cloudfoundry.org/routing-acceptance-tests/LICENSE

@@ -0,0 +1,176 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

src/code.cloudfoundry.org/routing-acceptance-tests/NOTICE

@@ -0,0 +1,13 @@
+Copyright (c) 2015-Present CloudFoundry.org Foundation, Inc. All Rights Reserved.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.