Scorecard supply-chain security / Scorecard analysis (push) Failing after 4m35s
Post / images (amd64) (push) Failing after 6m0s
Post / images (arm64) (push) Failing after 5m36s
Post / image manifest (push) Has been skipped
Post / trigger clusteradm e2e (push) Has been skipped
Post / coverage (push) Failing after 27m33s
* Add the awscli volume mount to klusterlet-work, klusterlet-agent, klusterlet-registration deployment manifests if the registration auth type is awsirsa.
Update the test util function to check for both .aws and /awscli volume mounts.
Signed-off-by: dtclxy64 <70486866+dtclxy64@users.noreply.github.com>
* Update the conditions to only check the registration driver auth type because the nil checks are done on the klusterlet CRD.
Signed-off-by: dtclxy64 <70486866+dtclxy64@users.noreply.github.com>
---------
Signed-off-by: dtclxy64 <70486866+dtclxy64@users.noreply.github.com>
Co-authored-by: Amrutha <amrutha.hari12@gmail.com>
* Regenerate the hub kubeconfig secret if the cluster name of the current context changes
Signed-off-by: zhujian <jiazhu@redhat.com>
* Add an integration test
Signed-off-by: zhujian <jiazhu@redhat.com>
---------
Signed-off-by: zhujian <jiazhu@redhat.com>
* 🌱 add a verify rule for golang files import order
This PR uses the [gci tool](https://github.com/daixiang0/gci) to make all go files' import section with a specific order, it will organize import with group with order：
1. standard library modules
2. 3rd party modules
3. modules in OCM org, like the `open-cluster-management.io/api`
4. current project `open-cluster-management.io/ocm` modules
developers can use the `make fmt-imports` to format the import automatically and the `make verify-fmt-imports` to check for any violation.
Signed-off-by: zhujian <jiazhu@redhat.com>
* 🌱 format the go files import
Signed-off-by: zhujian <jiazhu@redhat.com>
---------
Signed-off-by: zhujian <jiazhu@redhat.com>
