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

Empty commit to trigger PR workflows #4

Open
wants to merge 262 commits into
base: main
Choose a base branch
from

Conversation

weresch
Copy link
Owner

@weresch weresch commented Jun 28, 2024

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.

Note: Please create separate PR for every branch (main, v8 and v7) as needed.

Description of the Change

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?

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

Applicable Issues

List any applicable GitHub Issues here

How Urgent Is The Change?

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

Other Relevant Parties

Who else is affected by the change?

sweinstein22 and others added 30 commits February 7, 2022 09:10
We noticed the constant for minimum v3 versioning was not being used
anywhere and also did not accurately reflect the minimum CAPI version
required for the V8 CLI, which the CLI version that supports V3 only
uses. We replaced it with the accurate minimum version based on a
version checker that is being used in login and auth and consolidated
references to only use the minimum version constant.

Co-authored-by: Sarah Weinstein <sweinstein@pivotal.io>
Co-authored-by: Mona Mohebbi <mmohebbi@pivotal.io>
[reason] Renaming "protocol" column to "app-protocol"
in the destination table of the cf route command

Co-authored-by: Hector Calderon <hecalderon@vmware.com>
Currently the cli already has a flag named destination-protocol
and in order to have consistency we need to rename it to app-protocol

Co-authored-by: Hector Calderon <hecalderon@vmware.com>
…2234)

Currently we do not show the app-protocol in the output
of the cf routes command, so a new column must be added
to the output. Also, the apps mapped to the route should
be displayed in the apps column and must be separated with commas.

Co-authored-by: Hector Calderon <hecalderon@vmware.com>
…kporting-to-v8.1

[Sustaining] Backporting to v8 branch
When users have dynamic ASG's feature enabled they don't need to
restart/restage their application for security group updates to take and
effect.
… issues have been solved in the newer versions of go. Moreover, there are some security enhancements coming from 1.17.
Co-authored-by: Shwetha Gururaj <gururajsh@vmware.com>
…2260)

* Adds new update-destination command

update destination app-protocol for a route
so that the new protocol is used for all
communication from and to the app using that route

* Upgrades bundler version in integration go_ruby app

Co-authored-by: Cristhian Pena <cpena@vmware.com>
Co-authored-by: George Gelashvili <ggelashvili@vmware.com>
It was implemented everything for this feature but the error handler when
CAPI V3 answered with a 422 status code with the message
the service instance name is taken.
Authored-by: Matt Royal <mroyal@vmware.com>
- Extract "Authorization" header logic for CFonK8s into
  api/shared/WrapForCFOnK8sAuth and refactor existing code to use this
- Move LogCache client into api/logcache to avoid a cyclic import
- Bubble out error from logcache.NewClient
- New selfcontained tests for logcache request changes

Co-authored-by: Matt Royal <mroyal@vmware.com>
Co-authored-by: Dave Walter <walterda@vmware.com>
Co-authored-by: Ashwin Krishna <krishnaas@vmware.com>
Authored-by: Matt Royal <mroyal@vmware.com>
Add auth header to logcache API requests for cf-on-k8s
Bumps [github.com/docker/distribution](https://github.com/docker/distribution) from 2.6.0-rc.1.0.20171109224904-e5b5e44386f7+incompatible to 2.8.0+incompatible.
- [Release notes](https://github.com/docker/distribution/releases)
- [Commits](https://github.com/docker/distribution/commits/v2.8.0)

---
updated-dependencies:
- dependency-name: github.com/docker/distribution
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
* Add Build-Sign-Release workflow

Commit summary below

Current state of CF CLI release infrastructure is offline and quite
outdated. To make our release process more transparent and inclusive we
decided to move build, signing and release processes online to Github Actions.
* Split out release/upload part of workflow
* Add capabilities to release workflow

At this point working in a workflow separate from build, for separation
of concerns between building&signing, and releasing.

This is a squashed commit of the gha-allplatforms branch, consisting of
the following changes :

- Upload mac installer to S3
- include mac installer in github release
- retrieve mac binaries in release job
- add write permission to github release job
- Add linux packages, and simplify CLAW upload steps
- Switch to sync action to support simpler CLAW S3 upload step
- Add linux packages to GH Release
- Update artifact names in release jobs
- aws s3 ls to debug s3 upload
- bump aws s3 sync to non-default-region change

* Updated for build, release, and units workflows
* Add update-repos workflow

Update-repos workflow is in charge of updating and signing on a
repository level. This workflow should be triggered towards the end of
the release process after all packages are available via distribution
network (after CLAW update). It will update the following repositories:

- Homebrew formula in homebrew-tap git repository
- RPM repo hosted on S3
- Debian repo hosted on S3

Current implementations of the update-repos workflow is matching offline
release process.

Following updates are recommended:

- Implement backup and disaster recovery procedure

- Debian
  - fill license and vendor fields
- RPM
  - sign on the repo level
- Homebrew
  - add arm architecture

* Release pipelines updates
* Removes/Cleans comments

Also, small change to sign-windows-binary.ps1 as
that step was already being done in the sign job

* Update github actions secrets template

for use with the set-github-actions-env-vars.sh script,
or the github cli's 'secret set' subcommand directly

Co-authored-by: Alexander Berezovsky <aberezovsky@vmware.com>
Co-authored-by: George Gelashvili <ggelashvili@vmware.com>
Co-authored-by: Juan Diego Gonzalez <gojuan@vmware.com>
Signed-off-by: Pete Levine <lpete@vmware.com>
Support other CLI major versions
Major Build-Sign-Upload workflow refactor

Co-authored-by: Shwetha Gururaj <gururajsh@vmware.com>
Co-authored-by: Juan Diego Gonzalez <gojuan@vmware.com>
Signed-off-by: Juan Diego Gonzalez <gojuan@vmware.com>
Co-authored by: George Gelashvili <ggelashvili@vmware.com>
….2.0"

This reverts commit 14792b6.

We will follow the PR flow as always.
Starting golang 1.18 system APIs are used for certificate verification
on macOS instead of built-in go verifier. Which makes behavior similar
to Windows. Since we are skipping this test for Windows due to
difficulties with execution order we believe it's fair to skip it in
macOS too and rely on Linux test.

References:
- [Changes to x509 in Go 1.18 conversation](https://groups.google.com/g/golang-nuts/c/RGghq2gTWss/m/7GsudTfCAgAJ)
- https://cs.opensource.google/go/go/+/master:src/crypto/x509/root_darwin.go;l=52
- https://cs.opensource.google/go/go/+/master:src/crypto/x509/verify.go;l=766

Co-authored-by: Alexander Berezovsky <aberezovsky@vmware.com>
Co-authored-by: Alexander Berezovsky <aberezovsky@vmware.com>
We want to use single source of truth go.mod, instead of configuration
scattered across multiple places.

Co-authored-by: Alexander Berezovsky <aberezovsky@vmware.com>
This command is used for sharing a route in between two spaces
in order to facilitate the movement of apps in between
spaces.

Co-authored-by: Juan Diego Gonzalez <gojuan@vmware.com>
ctlong and others added 29 commits April 30, 2024 14:18
Shows the new CPU Entitlement metric in the app process table, under the
heading `cpu entitlement`. If CPU Entitlement metrics are not available
(e.g. deployment does not support it, app is stopped, etc.) for a
process instance, then that row will show an empty value.

Signed-off-by: Rebecca Roberts <rebecca.roberts@broadcom.com>
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.22.0 to 0.24.0.
- [Commits](golang/net@v0.22.0...v0.24.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…udfoundry#2870)

Bumps [code.cloudfoundry.org/go-loggregator/v9](https://github.com/cloudfoundry/go-loggregator) from 9.2.0 to 9.2.1.
- [Release notes](https://github.com/cloudfoundry/go-loggregator/releases)
- [Commits](cloudfoundry/go-loggregator@v9.2.0...v9.2.1)

---
updated-dependencies:
- dependency-name: code.cloudfoundry.org/go-loggregator/v9
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.17.1 to 2.17.3.
- [Release notes](https://github.com/onsi/ginkgo/releases)
- [Changelog](https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md)
- [Commits](onsi/ginkgo@v2.17.1...v2.17.3)

---
updated-dependencies:
- dependency-name: github.com/onsi/ginkgo/v2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.33.0 to 1.33.1.
- [Release notes](https://github.com/onsi/gomega/releases)
- [Changelog](https://github.com/onsi/gomega/blob/master/CHANGELOG.md)
- [Commits](onsi/gomega@v1.33.0...v1.33.1)

---
updated-dependencies:
- dependency-name: github.com/onsi/gomega
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.24.0 to 0.25.0.
- [Commits](golang/net@v0.24.0...v0.25.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…foundry#2904)

Bumps [github.com/cyphar/filepath-securejoin](https://github.com/cyphar/filepath-securejoin) from 0.2.4 to 0.2.5.
- [Release notes](https://github.com/cyphar/filepath-securejoin/releases)
- [Commits](cyphar/filepath-securejoin@v0.2.4...v0.2.5)

---
updated-dependencies:
- dependency-name: github.com/cyphar/filepath-securejoin
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- dependabot doesn't do well with non versioned dependencies
- will resolve the annyoing cve warning in goland ide
* Install ginkgo "out of the box"

This change installs the version of Ginkgo specified in go.mod, modifies
the Makefile to do this before each flavor of test, and simplifies the
CI tasks that invoke these tests.

Prior to this change, the Makefile assumes the presence of a
system-level installation of Ginkgo. That installation of Ginkgo will
not necessarily match the version specified in our go.mod.

This introduces the (slight) possibility of subtle differences in the
behavior of the test library. It also complicates spinning up a new
environment, either for a developer or in CI.

* No longer install gomega matchers as a system-level dependency

These matchers are imported as needed in the test files that need them.
There is no need to install them as a system-level dependency, so let's
not.
Bumps [github.com/fatih/color](https://github.com/fatih/color) from 1.16.0 to 1.17.0.
- [Release notes](https://github.com/fatih/color/releases)
- [Commits](fatih/color@v1.16.0...v1.17.0)

---
updated-dependencies:
- dependency-name: github.com/fatih/color
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Ignore non-existent files when deleting temp-files

* Only delete files older than 5min
- Add new action that will be responsible for running the linter
- Fix all the linter issues
- Remove deprecated linters

Signed-off-by: João Pereira <joaod@vmware.com>
Bumps [golangci/golangci-lint-action](https://github.com/golangci/golangci-lint-action) from 3 to 6.
- [Release notes](https://github.com/golangci/golangci-lint-action/releases)
- [Commits](golangci/golangci-lint-action@v3...v6)

---
updated-dependencies:
- dependency-name: golangci/golangci-lint-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…dry#2947)

Bumps [github.com/distribution/reference](https://github.com/distribution/reference) from 0.5.0 to 0.6.0.
- [Release notes](https://github.com/distribution/reference/releases)
- [Commits](distribution/reference@v0.5.0...v0.6.0)

---
updated-dependencies:
- dependency-name: github.com/distribution/reference
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
updated-dependencies:
- dependency-name: github.com/onsi/ginkgo/v2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.18.0 to 2.19.0.
- [Release notes](https://github.com/onsi/ginkgo/releases)
- [Changelog](https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md)
- [Commits](onsi/ginkgo@v2.18.0...v2.19.0)

---
updated-dependencies:
- dependency-name: github.com/onsi/ginkgo/v2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Enable tests against minimum version of capi
* Enable dispatching workflows via github UI

Signed-off-by: João Pereira <joaod@vmware.com>
Co-authored-by: Shwetha Gururaj <gururajsh@vmware.com>
Bumps [golang.org/x/text](https://github.com/golang/text) from 0.15.0 to 0.16.0.
- [Release notes](https://github.com/golang/text/releases)
- [Commits](golang/text@v0.15.0...v0.16.0)

---
updated-dependencies:
- dependency-name: golang.org/x/text
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Ensure correct pool is being used for PRs

* Use integration workflow directly from unit tests

* Provide secret directly instead of using env variable

* Remove check for Server header in curl request tests

Starting on version 1.181.0, capi will no longer report the version of
the nginx server to ensure that no information is leaked.
For more information check cloudfoundry/capi-release#406

* Change in response from UAA

Starting on version 76.26.0 of UAA a change was made that changes the
behavior more context in cloudfoundry/uaa#2545

Signed-off-by: João Pereira <joaod@vmware.com>
@weresch weresch changed the base branch from v8 to main June 28, 2024 16:25
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.