Unverified Commit cbe2176c authored by Aman Sharma's avatar Aman Sharma Committed by GitHub
Browse files

Add Misspell linter github workflow (#1266)


- Install misspelllinter using binaries.
- Refer hack/.misspellignore to see all the files that get ignored from misspell linter.
- All the files in repo other then .misspellignore are corrected.
- Add .github/workflows/check-misspell.yaml github workflow
Signed-off-by: default avatarAman Sharma <amansh@vmware.com>
Signed-off-by: default avatarRajas Kakodkar <rkakodkar@vmware.com>
Co-authored-by: default avatarAman Sharma <amansh@vmware.com>
Co-authored-by: default avatarRajas Kakodkar <rkakodkar@vmware.com>
Co-authored-by: default avatarRajas Kakodkar <rkakodkar@vmware.com>
parent 1bb46788
Showing with 77 additions and 22 deletions
+77 -22
name: Check misspell
on:
pull_request:
types:
- assigned
- opened
- synchronize
- reopened
jobs:
checkmisspell:
name: Check misspell
runs-on: ubuntu-latest
steps:
- name: Config credentials
env:
GITHUB_TOKEN: ${{ secrets.GH_ACCESS_TOKEN }}
run: |
git config --global url."https://git:$GITHUB_TOKEN@github.com".insteadOf "https://github.com"
- name: Check out code
uses: actions/checkout@v1
- name: Run misspell
run: |
make misspell
......@@ -184,7 +184,7 @@ By making a contribution to this project, I certify that:
### Multiple Go Modules
The TCE project is made up of many different, seperate Go modules.
The TCE project is made up of many different, separate Go modules.
Each module has its own `go.mod` and `go.sum` file located in the "root" of that individual, digestible piece of software.
This allows TCE to not have a single dependency graph, but rather, multiple, independent dependency graphs.
Experimental plugins or packages can pull in different versions of the same library without creating conflicts and collisions.
......@@ -214,9 +214,9 @@ it _is_ expected that each Makefile provide the following targets:
- `make e2e-test`: invokes an E2E testing suite
- `make lint`: invokes linting protocols for the individual module. For example, in a Go project, it should call Golangci-lint.
- `make get-deps`: gets the necessary dependencies for running, testing, and building. Typically is `go mod download` in Go modules
- `make build`: builds the individual peice of software
- `make build`: builds the individual piece of software
Some of these targets may be irrelivent to you and your project.
Some of these targets may be irrelevant to you and your project.
The top level TCE Makefile still expects these targets to be present,
but it's ok to simply print a message stating the target is being skipped or is not applicable.
......
......@@ -96,8 +96,8 @@ OCI_REGISTRY := projects.registry.vmware.com/tce
##### IMAGE #####
##### LINTING TARGETS #####
.PHONY: lint mdlint shellcheck check yamllint
check: ensure-deps lint mdlint shellcheck yamllint
.PHONY: lint mdlint shellcheck check yamllint misspell
check: ensure-deps lint mdlint shellcheck yamllint misspell
.PHONY: ensure-deps
ensure-deps:
......@@ -125,6 +125,8 @@ shellcheck:
yamllint:
hack/check-yaml.sh
misspell:
hack/check-misspell.sh
##### LINTING TARGETS #####
......
......@@ -136,7 +136,7 @@ The final step in creating the user is to copy the access keys. These credential
### 3. Hosted Zone
You can follow the instructions in the official [documentation](https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md#set-up-a-hosted-zone), or here. The official documentation creates a subdomain on the hosted zone. You can do this, or just use the hosted zone itself. There is a special step if you choose the subdomain route that is not reflected in the official documentation. This example will follow the offical documentation and call out the additional step.
You can follow the instructions in the official [documentation](https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md#set-up-a-hosted-zone), or here. The official documentation creates a subdomain on the hosted zone. You can do this, or just use the hosted zone itself. There is a special step if you choose the subdomain route that is not reflected in the official documentation. This example will follow the official documentation and call out the additional step.
For this example, we will be using the domain `k8squid.com`, and a subdomain of `external-dns-test`. Create the new hosted zone.
......@@ -253,6 +253,6 @@ NAMESPACE NAME DESCRIPTION SINCE-DEPLOY AGE
my-packages external-dns Reconcile succeeded 26s 26s
```
ExternalDNS should now be installed and running on your cluster. To verify that it works, you can follow the example in the [offical documentation using a service](https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md#verify-externaldns-works-service-example). Be sure to substitute your domain name and hosted zone id in service manifest and relevant AWS CLI commands.
ExternalDNS should now be installed and running on your cluster. To verify that it works, you can follow the example in the [official documentation using a service](https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md#verify-externaldns-works-service-example). Be sure to substitute your domain name and hosted zone id in service manifest and relevant AWS CLI commands.
>⚠️ Note: For more advanced use cases and documentation, see the official ExternalDNS [documentation](https://github.com/kubernetes-sigs/external-dns).
......@@ -114,7 +114,7 @@
"dashes": false,
"datasource": "$datasource",
"decimals": 3,
"description": "How much error budget is left looking at our 0.990% availability gurantees?",
"description": "How much error budget is left looking at our 0.990% availability guarantees?",
"fieldConfig": {
"defaults": {
"custom": {}
......
......@@ -17,7 +17,7 @@ imageInfo:
infrastructure_provider: null
tkg_cluster_role: null
custom_cluster_issuer: "" #! provide if user wants to use a custom ClusterIssuer for both Pinniped and Dex certificates
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the smae name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces.
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the same name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces.
http_proxy: ""
https_proxy: ""
no_proxy: ""
......@@ -74,7 +74,7 @@ dex:
#! value could also be picked up by ytt if no data value overrides it.
connector: null
staticClients: [] #! This is normally provided by the addon Secret
issuerPort: "30167" #! requred only for MGMT_CLUSTER_VIP if provider is vsphere. Default is "30167"
issuerPort: "30167" #! required only for MGMT_CLUSTER_VIP if provider is vsphere. Default is "30167"
oidc:
CLIENT_ID: null #! required if oidc enabled
CLIENT_SECRET: null #! required if oidc enabled
......
......@@ -17,7 +17,7 @@ imageInfo:
infrastructure_provider: vsphere #! required, valid values are [vsphere, aws, azure]
tkg_cluster_role: management #! required
custom_cluster_issuer: "" #! provide if user wants to use a custom ClusterIssuer for both Pinniped and Dex certificates
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the smae name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the same name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces
http_proxy: ""
https_proxy: ""
no_proxy: ""
......
......@@ -14,7 +14,7 @@ imageInfo:
infrastructure_provider: vsphere #! required, valid values are [vsphere, aws, azure]
tkg_cluster_role: management #! required
custom_cluster_issuer: "" #! provide if user wants to use a custom ClusterIssuer for both Pinniped and Dex certificates
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the smae name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces.
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the same name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces.
http_proxy: ""
https_proxy: ""
no_proxy: ""
......
......@@ -15,5 +15,5 @@ infrastructure_provider: vsphere #! required, valid values are [vsphere, aws, az
tkg_cluster_role: workload #! required, valid values are [management, workload]
identity_management_type: oidc #! required, valid values are [oidc, ldap]
pinniped:
supervisor_svc_endpoint: "https://<pinniped-supervisor-svc-host>:<port>" #! requried for workload cluster
supervisor_ca_bundle_data: "LS0tLS1CRxxxxxxxVSVElGSUNBVEUtLS0tLQo=" #! requried for workload cluster. Should be a valid base64 encoded string
supervisor_svc_endpoint: "https://<pinniped-supervisor-svc-host>:<port>" #! required for workload cluster
supervisor_ca_bundle_data: "LS0tLS1CRxxxxxxxVSVElGSUNBVEUtLS0tLQo=" #! required for workload cluster. Should be a valid base64 encoded string
......@@ -17,7 +17,7 @@ imageInfo:
infrastructure_provider: null
tkg_cluster_role: null
custom_cluster_issuer: "" #! provide if user wants to use a custom ClusterIssuer for both Pinniped and Dex certificates
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the smae name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces.
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the same name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces.
http_proxy: ""
https_proxy: ""
no_proxy: ""
......@@ -74,7 +74,7 @@ dex:
#! value could also be picked up by ytt if no data value overrides it.
connector: null
staticClients: [] #! This is normally provided by the addon Secret
issuerPort: "30167" #! requred only for MGMT_CLUSTER_VIP if provider is vsphere. Default is "30167"
issuerPort: "30167" #! required only for MGMT_CLUSTER_VIP if provider is vsphere. Default is "30167"
oidc:
CLIENT_ID: null #! required if oidc enabled
CLIENT_SECRET: null #! required if oidc enabled
......
......@@ -17,7 +17,7 @@ imageInfo:
infrastructure_provider: vsphere #! required, valid values are [vsphere, aws, azure]
tkg_cluster_role: management #! required
custom_cluster_issuer: "" #! provide if user wants to use a custom ClusterIssuer for both Pinniped and Dex certificates
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the smae name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the same name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces
http_proxy: ""
https_proxy: ""
no_proxy: ""
......
......@@ -14,7 +14,7 @@ imageInfo:
infrastructure_provider: vsphere #! required, valid values are [vsphere, aws, azure]
tkg_cluster_role: management #! required
custom_cluster_issuer: "" #! provide if user wants to use a custom ClusterIssuer for both Pinniped and Dex certificates
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the smae name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces.
custom_tls_secret: "" #! provide if user wants to use a custom TLS secret for both Pinniped and Dex, will override the ClusterIssuer above if specified, user should create secret with the same name in both "tanzu-system-auth" and "pinniped-supervisor" namespaces.
http_proxy: ""
https_proxy: ""
no_proxy: ""
......
......@@ -15,5 +15,5 @@ infrastructure_provider: vsphere #! required, valid values are [vsphere, aws, az
tkg_cluster_role: workload #! required, valid values are [management, workload]
identity_management_type: oidc #! required, valid values are [oidc, ldap]
pinniped:
supervisor_svc_endpoint: "https://<pinniped-supervisor-svc-host>:<port>" #! requried for workload cluster
supervisor_ca_bundle_data: "LS0tLS1CRxxxxxxxVSVElGSUNBVEUtLS0tLQo=" #! requried for workload cluster. Should be a valid base64 encoded string
supervisor_svc_endpoint: "https://<pinniped-supervisor-svc-host>:<port>" #! required for workload cluster
supervisor_ca_bundle_data: "LS0tLS1CRxxxxxxxVSVElGSUNBVEUtLS0tLQo=" #! required for workload cluster. Should be a valid base64 encoded string
......@@ -87,7 +87,7 @@ The following configuration values can be set to customize the prometheus / aler
| cadvisor.daemonset.podAnnotations | The cadvisor deployments pod annotations | map | {} |
| cadvisor.daemonset.podLabels | The cadvisor deployments pod labels | map | {} |
| ingress.enabled | Enable/disable ingress for prometheus and alertmanager | boolean | false |
| ingress.virtual_host_fqdn | Hostname for accessing promethues and alertmanager | string | prometheus.system.tanzu |
| ingress.virtual_host_fqdn | Hostname for accessing prometheus and alertmanager | string | prometheus.system.tanzu |
| ingress.prometheus_prefix | Path prefix for prometheus | string | / |
| ingress.alertmanager_prefix | Path prefix for alertmanager | string | /alertmanager/ |
| ingress.prometheusServicePort | Prometheus service port to proxy traffic to | integer | 80 |
......
docs/site/
#!/usr/bin/env bash
# Copyright 2021 VMware Tanzu Community Edition contributors. All Rights Reserved.
# SPDX-License-Identifier: Apache-2.0
set -o errexit
set -o nounset
set -o pipefail
MY_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
# Install tools we need if it is not present
if [[ ! -f "${MY_DIR}/tools/bin/misspell" ]]; then
curl -L https://git.io/misspell | bash
mkdir -p "${MY_DIR}/tools/bin"
mv ./bin/misspell "${MY_DIR}/tools/bin/misspell"
fi
# Spell checking
# misspell check Project - https://github.com/client9/misspell
misspellignore_files="${MY_DIR}/.misspellignore"
ignore_files=$(cat "${misspellignore_files}")
git ls-files | grep -v "${ignore_files}" | xargs "${MY_DIR}/tools/bin/misspell" | grep "misspelling" && echo "Please fix the errors mentioned and try running make misspell" && exit 1 || echo "Misspell check Pass"
......@@ -19,7 +19,7 @@ REPO_NAMESPACE="default"
# TODO: Use stable version of the tce/main repo once https://github.com/vmware-tanzu/community-edition/issues/1250 is fixed
tanzu package repository add ${REPO_NAME} --namespace ${REPO_NAMESPACE} --url ${REPO_URL}
# Wait for reconcilation to happen within ~ 80 x 5 = 400 seconds . 80 iterations, 5 seconds sleep time.
# Wait for reconciliation to happen within ~ 80 x 5 = 400 seconds . 80 iterations, 5 seconds sleep time.
# Check status every ~5 seconds interval
for (( i = 1 ; i <= 80 ; i++))
do
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment