-
Notifications
You must be signed in to change notification settings - Fork 67
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
Update branch set-label/v0.1 to the desired layout #219
Update branch set-label/v0.1 to the desired layout #219
Conversation
* implement starlark function * drop path and url support, update doc and add another test * update error message according to the guideline * code review * update example
Also tweak Dockerfile to speed up build speed by avoiding repeatly downloading go modules
* set-setter function * Address docs and other comments * Suggested changes 2
…ls#194) * Example and output for search replace * Add README for example and punt usage docs * Rename function to search-replace
…tainerTools#196) * Search replace README and generated docs * Apply setters README and godocs * Suggested changes: generate docs for all funcitons via looping * Suggested changes: apply-setters docs * Update image name to full image path * Suggested changes: remove sh and func-generate to docs-generate * kpt-fns to kpt-fn
* add a template for usage doc * move the usage doc template into functions/go dir * put it in comments * code review * update examples section * update Synopsis section * Update README.md Co-authored-by: Frank Farzan <[email protected]>
…#197) * Initial commit * Add short flags and usage to gatekeeper function. Also add a release workflow for pushing to gcr. * Upgrade OPA constraint framework (GoogleContainerTools#132) * Upgrade OPA constraint framework * Change revision -> version in Gopkg.toml Signed-off-by: Max Smythe <[email protected]> * Log violated constraint * Move validate.go to the desired dir after running git filter-branch * Migrate policy-controller-validate to use kyaml * code review * rename fn to gatekeeper-validate * Support different enforcement levels * code review * code review Co-authored-by: Frank Farzan <[email protected]> Co-authored-by: Max Smythe <[email protected]> Co-authored-by: Prachi Pendse <[email protected]>
…#205) Snyk has created this PR to upgrade @types/jasmine from 3.6.2 to 3.6.6. See this package in npm: https://www.npmjs.com/package/@types/jasmine See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/5ee802a9-8df2-4243-be28-e1da63426b99?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade typescript from 4.1.3 to 4.2.3. See this package in npm: https://www.npmjs.com/package/typescript See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/5ee802a9-8df2-4243-be28-e1da63426b99?utm_source=github&utm_medium=upgrade-pr
…#207) Snyk has created this PR to upgrade @types/jasmine from 3.6.2 to 3.6.6. See this package in npm: https://www.npmjs.com/package/@types/jasmine See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/0c90cff6-4386-4509-bd57-37f0b57f5960?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade typescript from 4.1.3 to 4.2.3. See this package in npm: https://www.npmjs.com/package/typescript See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/0c90cff6-4386-4509-bd57-37f0b57f5960?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade typescript from 4.1.3 to 4.2.3. See this package in npm: https://www.npmjs.com/package/typescript See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/206705c7-640c-491f-9f5b-bcb93537444e?utm_source=github&utm_medium=upgrade-pr
…#209) Snyk has created this PR to upgrade @types/jasmine from 3.6.2 to 3.6.6. See this package in npm: https://www.npmjs.com/package/@types/jasmine See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/206705c7-640c-491f-9f5b-bcb93537444e?utm_source=github&utm_medium=upgrade-pr
…eContainerTools#202) * Add metadata.yaml files and remove dir convention for examples * update metadata
Snyk has created this PR to upgrade typescript from 4.1.3 to 4.2.3. See this package in npm: https://www.npmjs.com/package/typescript See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/23d8f4ca-6976-433c-98ec-370eccabc2e7?utm_source=github&utm_medium=upgrade-pr
…#211) Snyk has created this PR to upgrade @types/jasmine from 3.6.2 to 3.6.7. See this package in npm: https://www.npmjs.com/package/@types/jasmine See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/23d8f4ca-6976-433c-98ec-370eccabc2e7?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade jasmine from 3.6.3 to 3.7.0. See this package in npm: https://www.npmjs.com/package/jasmine See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/206705c7-640c-491f-9f5b-bcb93537444e?utm_source=github&utm_medium=upgrade-pr
…#215) Snyk has created this PR to upgrade @types/jasmine from 3.6.6 to 3.6.7. See this package in npm: https://www.npmjs.com/package/@types/jasmine See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/0c90cff6-4386-4509-bd57-37f0b57f5960?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade jasmine from 3.6.3 to 3.7.0. See this package in npm: https://www.npmjs.com/package/jasmine See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/23d8f4ca-6976-433c-98ec-370eccabc2e7?utm_source=github&utm_medium=upgrade-pr
…#217) Snyk has created this PR to upgrade @types/jasmine from 3.6.6 to 3.6.7. See this package in npm: https://www.npmjs.com/package/@types/jasmine See this project in Snyk: https://app.snyk.io/org/kpt-fn-bot/project/206705c7-640c-491f-9f5b-bcb93537444e?utm_source=github&utm_medium=upgrade-pr
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Going to manually overwrite CLA label, since all of these commit are from the master branch and there are no new commits from unknown contributors. |
cc: @etefera |
fa1831a)
Other commits are picked up from the master branch.
There are no behavior change to the set-label function.