Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

Signed-off-by: Lucheng Bao <luchengb@vmware.com>

Go 1.16 deprecated ioutil [0]. This replaces its usage with the
recommended replacements so we don't get errors once this deprecation is
fully enforced or it is removed.

[0] https://go.dev/doc/go1.16#ioutil

Signed-off-by: Sean McGinnis <smcginnis@vmware.com>

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

Bumps [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) from 1.43.30 to 1.44.0.
- [Release notes](https://github.com/aws/aws-sdk-go/releases)
- [Changelog](https://github.com/aws/aws-sdk-go/blob/main/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-go/compare/v1.43.30...v1.44.0

)

---
updated-dependencies:
- dependency-name: github.com/aws/aws-sdk-go
  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>

Minor typo fix.
Signed-off-by: Sean McGinnis <smcginnis@vmware.com>

We've encouraged package authors to have test coverage, but so far we
have not had a common way to run any of these tests. This wires up the
`test-packages` target to run unit testing for all packages in the repo.
It also adds a GitHub Action so these tests are run whenever there are
modifications to the `addons/packages` files.
Signed-off-by: Sean McGinnis <smcginnis@vmware.com>

Signed-off-by: Lucheng Bao <luchengb@vmware.com>

Signed-off-by: John McBride <jmcbride@vmware.com>

Signed-off-by: Marc Khouzam <marc.khouzam@gmail.com>

Signed-off-by: Lucheng Bao <luchengb@vmware.com>

Signed-off-by: Lucheng Bao <luchengb@vmware.com>

Signed-off-by: Lucheng Bao <luchengb@vmware.com>

- Adding configurable params to fluxcd-source-controller
- Updating metadata file

Signed-off-by: Lucheng Bao <luchengb@vmware.com>

2. aligin nsx alb default resource request value
Signed-off-by: Xudong Liu <xudongl@vmware.com>

Bumps [k8s.io/client-go](https://github.com/kubernetes/client-go) from 0.23.5 to 0.23.6.
- [Release notes](https://github.com/kubernetes/client-go/releases)
- [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md)
- [Commits](https://github.com/kubernetes/client-go/compare/v0.23.5...v0.23.6

)

---
updated-dependencies:
- dependency-name: k8s.io/client-go
  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>

We had a placeholder target in the root Makefile for a `test-plugins`
target. This was meant to run unit test coverage for our CLI plugins.

We have since added unit test coverage for our plugins, so now is a good
time to finish wiring this up. This updates our plugins to support their
expected `make test` target, and `make test-plugins` will now invoke
this for all CLI plugins in the repo.

Also added this to the `check-all` GitHub Action so unit tests of the
CLI plugins are included as part of our comprehensive testing.
Signed-off-by: Sean McGinnis <smcginnis@vmware.com>

The current setup causes e2e tests to be run like any normal unit test,
making it difficult to quickly run unit testing.

This separates out the e2e tests so they need to be explicitly invoked
by requiring `-tags=e2e` in the invocation of `go test`.
Signed-off-by: Sean McGinnis <smcginnis@vmware.com>

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

* Add App Toolkit 0.2.0 package

- Use kpack-dependencies 0.0.9
- Use cartographer-catalog 0.3.0
- Bump to cartographer 0.3.0
- Add developer-namespace feature and requirement on secretgen-controller
- Switch App Toolkit Testing framework from go to bash
- Update Readme

* Correct linting errors

* Remove unneccessary kpack_dependencies configs and doc updates

* Fix kpack-dependencies docs link

- Implements a Github Action Workflow with two jobs
  - Get All Images
  - Scan All Images
- Because of Code Scanning Max. File Limits uses matrix to
  parallelize the jobs
- To enable matrix, the image list is broken into 10 parts
  with 12 images each. Max. File limit is 15, so this
  provides some breathing space for new images getting added
- Each image list file is then uploaded as a job artifact
- This job artifact is then downloaded and the matrix
  element relevant image list is scanned.
- Each scan generates a sarif file that is uploaded to GitHub
  Code Scanning as an Alert under Security Tab.
- Only vulnerabilities that are fixable and critical are pushed
  as a security alert

Fixes #4069
Signed-off-by: Patrick Kremer <pkremer@vmware.com>

Signed-off-by: John McBride <jmcbride@vmware.com>

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

- `cartographer-catalog` package

	contents coming from `vmare-tanzu/package-for-cartographer`
	where the packaging of multiple projects under the cartographer
	umbrella takes place.

- add smoke test

	include a smoke test that validate the `cartographer-catalog`'s
	functionality indeed works end-to-end. see README.md under the
	smoke test directory (cartographer-catalog/0.3.0) for directions
	on how to prepare the cluster for running the test.
Signed-off-by: Ciro S. Costa <ciroscosta@vmware.com>

Signed-off-by: github-actions <github-actions@github.com>
Co-authored-by: github-actions <github-actions@github.com>

The unmanaged cluster config unit test coverage was 57.6%. This adds
additional test coverage for some of the methods to cover happy path and
some failure conditions to bring the overall coverage for this module up
to 71.9%.

There is more that could be done to increase the coverage further, but
most of the remaining code lacking coverage would be minimal value
compared to the effort to add more cases.
Signed-off-by: Sean McGinnis <smcginnis@vmware.com>