From 924761e62971766110e4a265410907008d002aa6 Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 09:22:14 +0100 Subject: [PATCH 01/12] chore(deps): upgrade docusaurus to v3 --- .github/workflows/docs.yaml | 2 +- website/docusaurus.config.js | 1 + website/package.json | 21 +- website/yarn.lock | 7837 +++++++++++++++++++++------------- 4 files changed, 4830 insertions(+), 3031 deletions(-) diff --git a/.github/workflows/docs.yaml b/.github/workflows/docs.yaml index 1fb1136f16..7bb9ffbd09 100644 --- a/.github/workflows/docs.yaml +++ b/.github/workflows/docs.yaml @@ -29,7 +29,7 @@ jobs: uses: actions/configure-pages@v5 - uses: actions/setup-node@v4 with: - node-version: '16.x' + node-version: '18.x' - name: Build docs env: NODE_OPTIONS: "--max-old-space-size=4096" diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js index baf8253302..b0d321d507 100644 --- a/website/docusaurus.config.js +++ b/website/docusaurus.config.js @@ -14,6 +14,7 @@ module.exports = { plugins: [ () => ({ // Load yaml files as blobs + name: "yaml-files-as-blobs", configureWebpack: function () { return { module: { diff --git a/website/package.json b/website/package.json index 73b5a67cff..7d33114041 100644 --- a/website/package.json +++ b/website/package.json @@ -14,21 +14,21 @@ "write-heading-ids": "docusaurus write-heading-ids" }, "dependencies": { - "@docusaurus/core": "^2.4.1", - "@docusaurus/plugin-client-redirects": "^2.4.1", - "@docusaurus/plugin-google-analytics": "^2.4.1", - "@docusaurus/plugin-google-gtag": "^2.4.1", - "@docusaurus/plugin-sitemap": "^2.4.1", - "@docusaurus/preset-classic": "^2.4.1", - "@docusaurus/theme-search-algolia": "^2.4.1", + "@docusaurus/core": "^3.6.3", + "@docusaurus/plugin-client-redirects": "^3.6.3", + "@docusaurus/plugin-google-analytics": "^3.6.3", + "@docusaurus/plugin-google-gtag": "^3.6.3", + "@docusaurus/plugin-sitemap": "^3.6.3", + "@docusaurus/preset-classic": "^3.6.3", + "@docusaurus/theme-search-algolia": "^3.6.3", "@fortawesome/fontawesome-svg-core": "^6.3.0", "@fortawesome/free-regular-svg-icons": "^6.3.0", "@fortawesome/free-solid-svg-icons": "^6.3.0", "@fortawesome/react-fontawesome": "^0.2.0", "file-loader": "^6.2.0", "raw-loader": "^4.0.2", - "react": "^17.0.1", - "react-dom": "^17.0.1", + "react": "^18.0.0", + "react-dom": "^18.0.0", "react-player": "^2.11.0", "trim": "^1.0.1", "url-loader": "^4.1.1", @@ -52,5 +52,8 @@ "resolutions": { "ua-parser-js": "^0.7.33", "yaml": "^2.2.2" + }, + "engines": { + "node": ">=18.0" } } diff --git a/website/yarn.lock b/website/yarn.lock index 82fd4f31d3..4e6b9d123f 100644 --- a/website/yarn.lock +++ b/website/yarn.lock @@ -2,143 +2,284 @@ # yarn lockfile v1 -"@algolia/autocomplete-core@1.7.4": - version "1.7.4" - resolved "https://registry.npmjs.org/@algolia/autocomplete-core/-/autocomplete-core-1.7.4.tgz" - integrity sha512-daoLpQ3ps/VTMRZDEBfU8ixXd+amZcNJ4QSP3IERGyzqnL5Ch8uSRFt/4G8pUvW9c3o6GA4vtVv4I4lmnkdXyg== - dependencies: - "@algolia/autocomplete-shared" "1.7.4" - -"@algolia/autocomplete-preset-algolia@1.7.4": - version "1.7.4" - resolved "https://registry.npmjs.org/@algolia/autocomplete-preset-algolia/-/autocomplete-preset-algolia-1.7.4.tgz" - integrity sha512-s37hrvLEIfcmKY8VU9LsAXgm2yfmkdHT3DnA3SgHaY93yjZ2qL57wzb5QweVkYuEBZkT2PIREvRoLXC2sxTbpQ== - dependencies: - "@algolia/autocomplete-shared" "1.7.4" - -"@algolia/autocomplete-shared@1.7.4": - version "1.7.4" - resolved "https://registry.npmjs.org/@algolia/autocomplete-shared/-/autocomplete-shared-1.7.4.tgz" - integrity sha512-2VGCk7I9tA9Ge73Km99+Qg87w0wzW4tgUruvWAn/gfey1ZXgmxZtyIRBebk35R1O8TbK77wujVtCnpsGpRy1kg== - -"@algolia/cache-browser-local-storage@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/cache-browser-local-storage/-/cache-browser-local-storage-4.14.3.tgz" - integrity sha512-hWH1yCxgG3+R/xZIscmUrWAIBnmBFHH5j30fY/+aPkEZWt90wYILfAHIOZ1/Wxhho5SkPfwFmT7ooX2d9JeQBw== - dependencies: - "@algolia/cache-common" "4.14.3" - -"@algolia/cache-common@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/cache-common/-/cache-common-4.14.3.tgz" - integrity sha512-oZJofOoD9FQOwiGTzyRnmzvh3ZP8WVTNPBLH5xU5JNF7drDbRT0ocVT0h/xB2rPHYzOeXRrLaQQBwRT/CKom0Q== - -"@algolia/cache-in-memory@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/cache-in-memory/-/cache-in-memory-4.14.3.tgz" - integrity sha512-ES0hHQnzWjeioLQf5Nq+x1AWdZJ50znNPSH3puB/Y4Xsg4Av1bvLmTJe7SY2uqONaeMTvL0OaVcoVtQgJVw0vg== - dependencies: - "@algolia/cache-common" "4.14.3" - -"@algolia/client-account@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/client-account/-/client-account-4.14.3.tgz" - integrity sha512-PBcPb0+f5Xbh5UfLZNx2Ow589OdP8WYjB4CnvupfYBrl9JyC1sdH4jcq/ri8osO/mCZYjZrQsKAPIqW/gQmizQ== - dependencies: - "@algolia/client-common" "4.14.3" - "@algolia/client-search" "4.14.3" - "@algolia/transporter" "4.14.3" - -"@algolia/client-analytics@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/client-analytics/-/client-analytics-4.14.3.tgz" - integrity sha512-eAwQq0Hb/aauv9NhCH5Dp3Nm29oFx28sayFN2fdOWemwSeJHIl7TmcsxVlRsO50fsD8CtPcDhtGeD3AIFLNvqw== - dependencies: - "@algolia/client-common" "4.14.3" - "@algolia/client-search" "4.14.3" - "@algolia/requester-common" "4.14.3" - "@algolia/transporter" "4.14.3" - -"@algolia/client-common@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/client-common/-/client-common-4.14.3.tgz" - integrity sha512-jkPPDZdi63IK64Yg4WccdCsAP4pHxSkr4usplkUZM5C1l1oEpZXsy2c579LQ0rvwCs5JFmwfNG4ahOszidfWPw== - dependencies: - "@algolia/requester-common" "4.14.3" - "@algolia/transporter" "4.14.3" - -"@algolia/client-personalization@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/client-personalization/-/client-personalization-4.14.3.tgz" - integrity sha512-UCX1MtkVNgaOL9f0e22x6tC9e2H3unZQlSUdnVaSKpZ+hdSChXGaRjp2UIT7pxmPqNCyv51F597KEX5WT60jNg== - dependencies: - "@algolia/client-common" "4.14.3" - "@algolia/requester-common" "4.14.3" - "@algolia/transporter" "4.14.3" - -"@algolia/client-search@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/client-search/-/client-search-4.14.3.tgz" - integrity sha512-I2U7xBx5OPFdPLA8AXKUPPxGY3HDxZ4r7+mlZ8ZpLbI8/ri6fnu6B4z3wcL7sgHhDYMwnAE8Xr0AB0h3Hnkp4A== - dependencies: - "@algolia/client-common" "4.14.3" - "@algolia/requester-common" "4.14.3" - "@algolia/transporter" "4.14.3" +"@algolia/autocomplete-core@1.17.7": + version "1.17.7" + resolved "https://registry.yarnpkg.com/@algolia/autocomplete-core/-/autocomplete-core-1.17.7.tgz#2c410baa94a47c5c5f56ed712bb4a00ebe24088b" + integrity sha512-BjiPOW6ks90UKl7TwMv7oNQMnzU+t/wk9mgIDi6b1tXpUek7MW0lbNOUHpvam9pe3lVCf4xPFT+lK7s+e+fs7Q== + dependencies: + "@algolia/autocomplete-plugin-algolia-insights" "1.17.7" + "@algolia/autocomplete-shared" "1.17.7" + +"@algolia/autocomplete-plugin-algolia-insights@1.17.7": + version "1.17.7" + resolved "https://registry.yarnpkg.com/@algolia/autocomplete-plugin-algolia-insights/-/autocomplete-plugin-algolia-insights-1.17.7.tgz#7d2b105f84e7dd8f0370aa4c4ab3b704e6760d82" + integrity sha512-Jca5Ude6yUOuyzjnz57og7Et3aXjbwCSDf/8onLHSQgw1qW3ALl9mrMWaXb5FmPVkV3EtkD2F/+NkT6VHyPu9A== + dependencies: + "@algolia/autocomplete-shared" "1.17.7" + +"@algolia/autocomplete-preset-algolia@1.17.7": + version "1.17.7" + resolved "https://registry.yarnpkg.com/@algolia/autocomplete-preset-algolia/-/autocomplete-preset-algolia-1.17.7.tgz#c9badc0d73d62db5bf565d839d94ec0034680ae9" + integrity sha512-ggOQ950+nwbWROq2MOCIL71RE0DdQZsceqrg32UqnhDz8FlO9rL8ONHNsI2R1MH0tkgVIDKI/D0sMiUchsFdWA== + dependencies: + "@algolia/autocomplete-shared" "1.17.7" + +"@algolia/autocomplete-shared@1.17.7": + version "1.17.7" + resolved "https://registry.yarnpkg.com/@algolia/autocomplete-shared/-/autocomplete-shared-1.17.7.tgz#105e84ad9d1a31d3fb86ba20dc890eefe1a313a0" + integrity sha512-o/1Vurr42U/qskRSuhBH+VKxMvkkUVTLU6WZQr+L5lGZZLYWyhdzWjW0iGXY7EkwRTjBqvN2EsR81yCTGV/kmg== + +"@algolia/cache-browser-local-storage@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/cache-browser-local-storage/-/cache-browser-local-storage-4.24.0.tgz#97bc6d067a9fd932b9c922faa6b7fd6e546e1348" + integrity sha512-t63W9BnoXVrGy9iYHBgObNXqYXM3tYXCjDSHeNwnsc324r4o5UiVKUiAB4THQ5z9U5hTj6qUvwg/Ez43ZD85ww== + dependencies: + "@algolia/cache-common" "4.24.0" + +"@algolia/cache-common@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/cache-common/-/cache-common-4.24.0.tgz#81a8d3a82ceb75302abb9b150a52eba9960c9744" + integrity sha512-emi+v+DmVLpMGhp0V9q9h5CdkURsNmFC+cOS6uK9ndeJm9J4TiqSvPYVu+THUP8P/S08rxf5x2P+p3CfID0Y4g== + +"@algolia/cache-in-memory@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/cache-in-memory/-/cache-in-memory-4.24.0.tgz#ffcf8872f3a10cb85c4f4641bdffd307933a6e44" + integrity sha512-gDrt2so19jW26jY3/MkFg5mEypFIPbPoXsQGQWAi6TrCPsNOSEYepBMPlucqWigsmEy/prp5ug2jy/N3PVG/8w== + dependencies: + "@algolia/cache-common" "4.24.0" + +"@algolia/client-abtesting@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/client-abtesting/-/client-abtesting-5.18.0.tgz#1bc368444d08b6e48ce56f1d5c935bfb9f658a98" + integrity sha512-DLIrAukjsSrdMNNDx1ZTks72o4RH/1kOn8Wx5zZm8nnqFexG+JzY4SANnCNEjnFQPJTTvC+KpgiNW/CP2lumng== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +"@algolia/client-account@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/client-account/-/client-account-4.24.0.tgz#eba7a921d828e7c8c40a32d4add21206c7fe12f1" + integrity sha512-adcvyJ3KjPZFDybxlqnf+5KgxJtBjwTPTeyG2aOyoJvx0Y8dUQAEOEVOJ/GBxX0WWNbmaSrhDURMhc+QeevDsA== + dependencies: + "@algolia/client-common" "4.24.0" + "@algolia/client-search" "4.24.0" + "@algolia/transporter" "4.24.0" + +"@algolia/client-analytics@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/client-analytics/-/client-analytics-4.24.0.tgz#9d2576c46a9093a14e668833c505ea697a1a3e30" + integrity sha512-y8jOZt1OjwWU4N2qr8G4AxXAzaa8DBvyHTWlHzX/7Me1LX8OayfgHexqrsL4vSBcoMmVw2XnVW9MhL+Y2ZDJXg== + dependencies: + "@algolia/client-common" "4.24.0" + "@algolia/client-search" "4.24.0" + "@algolia/requester-common" "4.24.0" + "@algolia/transporter" "4.24.0" + +"@algolia/client-analytics@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/client-analytics/-/client-analytics-5.18.0.tgz#de0dc80011fdbaa9853adbdb836e0a80f08f53df" + integrity sha512-0VpGG2uQW+h2aejxbG8VbnMCQ9ary9/ot7OASXi6OjE0SRkYQ/+pkW+q09+IScif3pmsVVYggmlMPtAsmYWHng== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +"@algolia/client-common@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/client-common/-/client-common-4.24.0.tgz#77c46eee42b9444a1d1c1583a83f7df4398a649d" + integrity sha512-bc2ROsNL6w6rqpl5jj/UywlIYC21TwSSoFHKl01lYirGMW+9Eek6r02Tocg4gZ8HAw3iBvu6XQiM3BEbmEMoiA== + dependencies: + "@algolia/requester-common" "4.24.0" + "@algolia/transporter" "4.24.0" + +"@algolia/client-common@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/client-common/-/client-common-5.18.0.tgz#8de3991b25ff3c9bbf5ef06c19f6a4a4fa64f328" + integrity sha512-X1WMSC+1ve2qlMsemyTF5bIjwipOT+m99Ng1Tyl36ZjQKTa54oajBKE0BrmM8LD8jGdtukAgkUhFoYOaRbMcmQ== + +"@algolia/client-insights@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/client-insights/-/client-insights-5.18.0.tgz#2c6f158e57265fd0888f5b84fe7302d6d659c0ff" + integrity sha512-FAJRNANUOSs/FgYOJ/Njqp+YTe4TMz2GkeZtfsw1TMiA5mVNRS/nnMpxas9771aJz7KTEWvK9GwqPs0K6RMYWg== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +"@algolia/client-personalization@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/client-personalization/-/client-personalization-4.24.0.tgz#8b47789fb1cb0f8efbea0f79295b7c5a3850f6ae" + integrity sha512-l5FRFm/yngztweU0HdUzz1rC4yoWCFo3IF+dVIVTfEPg906eZg5BOd1k0K6rZx5JzyyoP4LdmOikfkfGsKVE9w== + dependencies: + "@algolia/client-common" "4.24.0" + "@algolia/requester-common" "4.24.0" + "@algolia/transporter" "4.24.0" + +"@algolia/client-personalization@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/client-personalization/-/client-personalization-5.18.0.tgz#26128f6a1aef523ae32f29ef9afd18fd2f159b98" + integrity sha512-I2dc94Oiwic3SEbrRp8kvTZtYpJjGtg5y5XnqubgnA15AgX59YIY8frKsFG8SOH1n2rIhUClcuDkxYQNXJLg+w== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +"@algolia/client-query-suggestions@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/client-query-suggestions/-/client-query-suggestions-5.18.0.tgz#9911560aa2dd26984a6d3f9803f14aecc2f1d10e" + integrity sha512-x6XKIQgKFTgK/bMasXhghoEjHhmgoP61pFPb9+TaUJ32aKOGc65b12usiGJ9A84yS73UDkXS452NjyP50Knh/g== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +"@algolia/client-search@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/client-search/-/client-search-4.24.0.tgz#75e6c02d33ef3e0f34afd9962c085b856fc4a55f" + integrity sha512-uRW6EpNapmLAD0mW47OXqTP8eiIx5F6qN9/x/7HHO6owL3N1IXqydGwW5nhDFBrV+ldouro2W1VX3XlcUXEFCA== + dependencies: + "@algolia/client-common" "4.24.0" + "@algolia/requester-common" "4.24.0" + "@algolia/transporter" "4.24.0" + +"@algolia/client-search@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/client-search/-/client-search-5.18.0.tgz#26a3b55b6783cf7eaa8c28b48b891ed245c7e708" + integrity sha512-qI3LcFsVgtvpsBGR7aNSJYxhsR+Zl46+958ODzg8aCxIcdxiK7QEVLMJMZAR57jGqW0Lg/vrjtuLFDMfSE53qA== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" "@algolia/events@^4.0.1": version "4.0.1" resolved "https://registry.npmjs.org/@algolia/events/-/events-4.0.1.tgz" integrity sha512-FQzvOCgoFXAbf5Y6mYozw2aj5KCJoA3m4heImceldzPSMbdyS4atVjJzXKMsfX3wnZTFYwkkt8/z8UesLHlSBQ== -"@algolia/logger-common@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/logger-common/-/logger-common-4.14.3.tgz" - integrity sha512-kUEAZaBt/J3RjYi8MEBT2QEexJR2kAE2mtLmezsmqMQZTV502TkHCxYzTwY2dE7OKcUTxi4OFlMuS4GId9CWPw== - -"@algolia/logger-console@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/logger-console/-/logger-console-4.14.3.tgz" - integrity sha512-ZWqAlUITktiMN2EiFpQIFCJS10N96A++yrexqC2Z+3hgF/JcKrOxOdT4nSCQoEPvU4Ki9QKbpzbebRDemZt/hw== - dependencies: - "@algolia/logger-common" "4.14.3" - -"@algolia/requester-browser-xhr@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/requester-browser-xhr/-/requester-browser-xhr-4.14.3.tgz" - integrity sha512-AZeg2T08WLUPvDncl2XLX2O67W5wIO8MNaT7z5ii5LgBTuk/rU4CikTjCe2xsUleIZeFl++QrPAi4Bdxws6r/Q== - dependencies: - "@algolia/requester-common" "4.14.3" - -"@algolia/requester-common@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/requester-common/-/requester-common-4.14.3.tgz" - integrity sha512-RrRzqNyKFDP7IkTuV3XvYGF9cDPn9h6qEDl595lXva3YUk9YSS8+MGZnnkOMHvjkrSCKfoLeLbm/T4tmoIeclw== - -"@algolia/requester-node-http@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/requester-node-http/-/requester-node-http-4.14.3.tgz" - integrity sha512-O5wnPxtDRPuW2U0EaOz9rMMWdlhwP0J0eSL1Z7TtXF8xnUeeUyNJrdhV5uy2CAp6RbhM1VuC3sOJcIR6Av+vbA== - dependencies: - "@algolia/requester-common" "4.14.3" - -"@algolia/transporter@4.14.3": - version "4.14.3" - resolved "https://registry.npmjs.org/@algolia/transporter/-/transporter-4.14.3.tgz" - integrity sha512-2qlKlKsnGJ008exFRb5RTeTOqhLZj0bkMCMVskxoqWejs2Q2QtWmsiH98hDfpw0fmnyhzHEt0Z7lqxBYp8bW2w== - dependencies: - "@algolia/cache-common" "4.14.3" - "@algolia/logger-common" "4.14.3" - "@algolia/requester-common" "4.14.3" - -"@ampproject/remapping@^2.1.0": - version "2.2.0" - resolved "https://registry.npmjs.org/@ampproject/remapping/-/remapping-2.2.0.tgz" - integrity sha512-qRmjj8nj9qmLTQXXmaR1cck3UXSRMPrbsLJAasZpF+t3riI71BXed5ebIOYwQntykeZuhjsdweEc9BxH5Jc26w== +"@algolia/ingestion@1.18.0": + version "1.18.0" + resolved "https://registry.yarnpkg.com/@algolia/ingestion/-/ingestion-1.18.0.tgz#023e2fda366655b0e8f2cdddd98666412815429d" + integrity sha512-bGvJg7HnGGm+XWYMDruZXWgMDPVt4yCbBqq8DM6EoaMBK71SYC4WMfIdJaw+ABqttjBhe6aKNRkWf/bbvYOGyw== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +"@algolia/logger-common@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/logger-common/-/logger-common-4.24.0.tgz#28d439976019ec0a46ba7a1a739ef493d4ef8123" + integrity sha512-LLUNjkahj9KtKYrQhFKCzMx0BY3RnNP4FEtO+sBybCjJ73E8jNdaKJ/Dd8A/VA4imVHP5tADZ8pn5B8Ga/wTMA== + +"@algolia/logger-console@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/logger-console/-/logger-console-4.24.0.tgz#c6ff486036cd90b81d07a95aaba04461da7e1c65" + integrity sha512-X4C8IoHgHfiUROfoRCV+lzSy+LHMgkoEEU1BbKcsfnV0i0S20zyy0NLww9dwVHUWNfPPxdMU+/wKmLGYf96yTg== + dependencies: + "@algolia/logger-common" "4.24.0" + +"@algolia/monitoring@1.18.0": + version "1.18.0" + resolved "https://registry.yarnpkg.com/@algolia/monitoring/-/monitoring-1.18.0.tgz#e94a4c436be0d8c1e9d19c69aeff8e67d0237736" + integrity sha512-lBssglINIeGIR+8KyzH05NAgAmn1BCrm5D2T6pMtr/8kbTHvvrm1Zvcltc5dKUQEFyyx3J5+MhNc7kfi8LdjVw== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +"@algolia/recommend@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/recommend/-/recommend-4.24.0.tgz#8a3f78aea471ee0a4836b78fd2aad4e9abcaaf34" + integrity sha512-P9kcgerfVBpfYHDfVZDvvdJv0lEoCvzNlOy2nykyt5bK8TyieYyiD0lguIJdRZZYGre03WIAFf14pgE+V+IBlw== + dependencies: + "@algolia/cache-browser-local-storage" "4.24.0" + "@algolia/cache-common" "4.24.0" + "@algolia/cache-in-memory" "4.24.0" + "@algolia/client-common" "4.24.0" + "@algolia/client-search" "4.24.0" + "@algolia/logger-common" "4.24.0" + "@algolia/logger-console" "4.24.0" + "@algolia/requester-browser-xhr" "4.24.0" + "@algolia/requester-common" "4.24.0" + "@algolia/requester-node-http" "4.24.0" + "@algolia/transporter" "4.24.0" + +"@algolia/recommend@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/recommend/-/recommend-5.18.0.tgz#bd07d3057dd2030718c6707a4fe247b871f1834d" + integrity sha512-uSnkm0cdAuFwdMp4pGT5vHVQ84T6AYpTZ3I0b3k/M3wg4zXDhl3aCiY8NzokEyRLezz/kHLEEcgb/tTTobOYVw== + dependencies: + "@algolia/client-common" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +"@algolia/requester-browser-xhr@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/requester-browser-xhr/-/requester-browser-xhr-4.24.0.tgz#313c5edab4ed73a052e75803855833b62dd19c16" + integrity sha512-Z2NxZMb6+nVXSjF13YpjYTdvV3032YTBSGm2vnYvYPA6mMxzM3v5rsCiSspndn9rzIW4Qp1lPHBvuoKJV6jnAA== + dependencies: + "@algolia/requester-common" "4.24.0" + +"@algolia/requester-browser-xhr@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/requester-browser-xhr/-/requester-browser-xhr-5.18.0.tgz#6e7e56bb687904a01c91988393f5c1969944ee3d" + integrity sha512-1XFjW0C3pV0dS/9zXbV44cKI+QM4ZIz9cpatXpsjRlq6SUCpLID3DZHsXyE6sTb8IhyPaUjk78GEJT8/3hviqg== + dependencies: + "@algolia/client-common" "5.18.0" + +"@algolia/requester-common@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/requester-common/-/requester-common-4.24.0.tgz#1c60c198031f48fcdb9e34c4057a3ea987b9a436" + integrity sha512-k3CXJ2OVnvgE3HMwcojpvY6d9kgKMPRxs/kVohrwF5WMr2fnqojnycZkxPoEg+bXm8fi5BBfFmOqgYztRtHsQA== + +"@algolia/requester-fetch@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/requester-fetch/-/requester-fetch-5.18.0.tgz#fcccc76bd7d16fb54c56d15baa6b5f657b17ca71" + integrity sha512-0uodeNdAHz1YbzJh6C5xeQ4T6x5WGiUxUq3GOaT/R4njh5t78dq+Rb187elr7KtnjUmETVVuCvmEYaThfTHzNg== + dependencies: + "@algolia/client-common" "5.18.0" + +"@algolia/requester-node-http@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/requester-node-http/-/requester-node-http-4.24.0.tgz#4461593714031d02aa7da221c49df675212f482f" + integrity sha512-JF18yTjNOVYvU/L3UosRcvbPMGT9B+/GQWNWnenIImglzNVGpyzChkXLnrSf6uxwVNO6ESGu6oN8MqcGQcjQJw== + dependencies: + "@algolia/requester-common" "4.24.0" + +"@algolia/requester-node-http@5.18.0": + version "5.18.0" + resolved "https://registry.yarnpkg.com/@algolia/requester-node-http/-/requester-node-http-5.18.0.tgz#c5b16de53d83276067583e7b2f56b09eac938435" + integrity sha512-tZCqDrqJ2YE2I5ukCQrYN8oiF6u3JIdCxrtKq+eniuLkjkO78TKRnXrVcKZTmfFJyyDK8q47SfDcHzAA3nHi6w== + dependencies: + "@algolia/client-common" "5.18.0" + +"@algolia/transporter@4.24.0": + version "4.24.0" + resolved "https://registry.yarnpkg.com/@algolia/transporter/-/transporter-4.24.0.tgz#226bb1f8af62430374c1972b2e5c8580ab275102" + integrity sha512-86nI7w6NzWxd1Zp9q3413dRshDqAzSbsQjhcDhPIatEFiZrL1/TjnHL8S7jVKFePlIMzDsZWXAXwXzcok9c5oA== + dependencies: + "@algolia/cache-common" "4.24.0" + "@algolia/logger-common" "4.24.0" + "@algolia/requester-common" "4.24.0" + +"@ampproject/remapping@^2.2.0": + version "2.3.0" + resolved "https://registry.yarnpkg.com/@ampproject/remapping/-/remapping-2.3.0.tgz#ed441b6fa600072520ce18b43d2c8cc8caecc7f4" + integrity sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw== dependencies: - "@jridgewell/gen-mapping" "^0.1.0" - "@jridgewell/trace-mapping" "^0.3.9" + "@jridgewell/gen-mapping" "^0.3.5" + "@jridgewell/trace-mapping" "^0.3.24" -"@babel/code-frame@^7.0.0", "@babel/code-frame@^7.10.4", "@babel/code-frame@^7.16.0", "@babel/code-frame@^7.18.6", "@babel/code-frame@^7.22.13", "@babel/code-frame@^7.8.3": +"@babel/code-frame@^7.0.0", "@babel/code-frame@^7.16.0", "@babel/code-frame@^7.8.3": version "7.22.13" resolved "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.22.13.tgz" integrity sha512-XktuhWlJ5g+3TJXc5upd9Ks1HutSArik6jf2eAjYFyIOf4ej3RN+184cZbzDvbPnuTJIUhPKKJE3cIsYTiAT3w== @@ -146,63 +287,51 @@ "@babel/highlight" "^7.22.13" chalk "^2.4.2" -"@babel/compat-data@^7.17.7", "@babel/compat-data@^7.20.1", "@babel/compat-data@^7.20.5": - version "7.20.14" - resolved "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.20.14.tgz" - integrity sha512-0YpKHD6ImkWMEINCyDAD0HLLUH/lPCefG8ld9it8DJB2wnApraKuhgYTvTY1z7UFIfBTGy5LwncZ+5HWWGbhFw== - -"@babel/core@7.12.9": - version "7.12.9" - resolved "https://registry.npmjs.org/@babel/core/-/core-7.12.9.tgz" - integrity sha512-gTXYh3M5wb7FRXQy+FErKFAv90BnlOuNn1QkCK2lREoPAjrQCO49+HVSrFoe5uakFAF5eenS75KbO2vQiLrTMQ== - dependencies: - "@babel/code-frame" "^7.10.4" - "@babel/generator" "^7.12.5" - "@babel/helper-module-transforms" "^7.12.1" - "@babel/helpers" "^7.12.5" - "@babel/parser" "^7.12.7" - "@babel/template" "^7.12.7" - "@babel/traverse" "^7.12.9" - "@babel/types" "^7.12.7" - convert-source-map "^1.7.0" - debug "^4.1.0" - gensync "^1.0.0-beta.1" - json5 "^2.1.2" - lodash "^4.17.19" - resolve "^1.3.2" - semver "^5.4.1" - source-map "^0.5.0" - -"@babel/core@^7.18.6", "@babel/core@^7.19.6": - version "7.20.12" - resolved "https://registry.npmjs.org/@babel/core/-/core-7.20.12.tgz" - integrity sha512-XsMfHovsUYHFMdrIHkZphTN/2Hzzi78R08NuHfDBehym2VsPDL6Zn/JAD/JQdnRvbSsbQc4mVaU1m6JgtTEElg== - dependencies: - "@ampproject/remapping" "^2.1.0" - "@babel/code-frame" "^7.18.6" - "@babel/generator" "^7.20.7" - "@babel/helper-compilation-targets" "^7.20.7" - "@babel/helper-module-transforms" "^7.20.11" - "@babel/helpers" "^7.20.7" - "@babel/parser" "^7.20.7" - "@babel/template" "^7.20.7" - "@babel/traverse" "^7.20.12" - "@babel/types" "^7.20.7" - convert-source-map "^1.7.0" +"@babel/code-frame@^7.25.9", "@babel/code-frame@^7.26.0", "@babel/code-frame@^7.26.2": + version "7.26.2" + resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.26.2.tgz#4b5fab97d33338eff916235055f0ebc21e573a85" + integrity sha512-RJlIHRueQgwWitWgF8OdFYGZX328Ax5BCemNGlqHfplnRT9ESi8JkFlvaVYbS+UubVY6dpv87Fs2u5M29iNFVQ== + dependencies: + "@babel/helper-validator-identifier" "^7.25.9" + js-tokens "^4.0.0" + picocolors "^1.0.0" + +"@babel/compat-data@^7.22.6", "@babel/compat-data@^7.25.9", "@babel/compat-data@^7.26.0": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/compat-data/-/compat-data-7.26.3.tgz#99488264a56b2aded63983abd6a417f03b92ed02" + integrity sha512-nHIxvKPniQXpmQLb0vhY3VaFb3S0YrTAwpOWJZh1wn3oJPjJk9Asva204PsBdmAE8vpzfHudT8DB0scYvy9q0g== + +"@babel/core@^7.21.3", "@babel/core@^7.25.9": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.26.0.tgz#d78b6023cc8f3114ccf049eb219613f74a747b40" + integrity sha512-i1SLeK+DzNnQ3LL/CswPCa/E5u4lh1k6IAEphON8F+cXt0t9euTshDru0q7/IqMa1PMPz5RnHuHscF8/ZJsStg== + dependencies: + "@ampproject/remapping" "^2.2.0" + "@babel/code-frame" "^7.26.0" + "@babel/generator" "^7.26.0" + "@babel/helper-compilation-targets" "^7.25.9" + "@babel/helper-module-transforms" "^7.26.0" + "@babel/helpers" "^7.26.0" + "@babel/parser" "^7.26.0" + "@babel/template" "^7.25.9" + "@babel/traverse" "^7.25.9" + "@babel/types" "^7.26.0" + convert-source-map "^2.0.0" debug "^4.1.0" gensync "^1.0.0-beta.2" - json5 "^2.2.2" - semver "^6.3.0" + json5 "^2.2.3" + semver "^6.3.1" -"@babel/generator@^7.12.5", "@babel/generator@^7.18.7", "@babel/generator@^7.20.7", "@babel/generator@^7.23.0": - version "7.23.0" - resolved "https://registry.npmjs.org/@babel/generator/-/generator-7.23.0.tgz" - integrity sha512-lN85QRR+5IbYrMWM6Y4pE/noaQtg4pNiqeNGX60eqOfo6gtEj6uw/JagelB8vVztSd7R6M5n1+PQkDbHbBRU4g== +"@babel/generator@^7.25.9", "@babel/generator@^7.26.0", "@babel/generator@^7.26.3": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.26.3.tgz#ab8d4360544a425c90c248df7059881f4b2ce019" + integrity sha512-6FF/urZvD0sTeO7k6/B15pMLC4CHUv1426lzr3N01aHJTl046uCAh9LXW/fzeXXjPNCJ6iABW5XaWOsIZB93aQ== dependencies: - "@babel/types" "^7.23.0" - "@jridgewell/gen-mapping" "^0.3.2" - "@jridgewell/trace-mapping" "^0.3.17" - jsesc "^2.5.1" + "@babel/parser" "^7.26.3" + "@babel/types" "^7.26.3" + "@jridgewell/gen-mapping" "^0.3.5" + "@jridgewell/trace-mapping" "^0.3.25" + jsesc "^3.0.2" "@babel/helper-annotate-as-pure@^7.18.6": version "7.18.6" @@ -211,40 +340,38 @@ dependencies: "@babel/types" "^7.18.6" -"@babel/helper-builder-binary-assignment-operator-visitor@^7.18.6": - version "7.18.9" - resolved "https://registry.npmjs.org/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.18.9.tgz" - integrity sha512-yFQ0YCHoIqarl8BCRwBL8ulYUaZpz3bNsA7oFepAzee+8/+ImtADXNOmO5vJvsPff3qi+hvpkY/NYBTrBQgdNw== +"@babel/helper-annotate-as-pure@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.25.9.tgz#d8eac4d2dc0d7b6e11fa6e535332e0d3184f06b4" + integrity sha512-gv7320KBUFJz1RnylIg5WWYPRXKZ884AGkYpgpWW02TH66Dl+HaC1t1CKd0z3R4b6hdYEcmrNZHUmfCP+1u3/g== dependencies: - "@babel/helper-explode-assignable-expression" "^7.18.6" - "@babel/types" "^7.18.9" + "@babel/types" "^7.25.9" -"@babel/helper-compilation-targets@^7.17.7", "@babel/helper-compilation-targets@^7.18.9", "@babel/helper-compilation-targets@^7.20.0", "@babel/helper-compilation-targets@^7.20.7": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-targets-7.20.7.tgz" - integrity sha512-4tGORmfQcrc+bvrjb5y3dG9Mx1IOZjsHqQVUz7XCNHO+iTmqxWnVg3KRygjGmpRLJGdQSKuvFinbIb0CnZwHAQ== +"@babel/helper-compilation-targets@^7.22.6", "@babel/helper-compilation-targets@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-compilation-targets/-/helper-compilation-targets-7.25.9.tgz#55af025ce365be3cdc0c1c1e56c6af617ce88875" + integrity sha512-j9Db8Suy6yV/VHa4qzrj9yZfZxhLWQdVnRlXxmKLYlhWUVB1sB2G5sxuWYXk/whHD9iW76PmNzxZ4UCnTQTVEQ== dependencies: - "@babel/compat-data" "^7.20.5" - "@babel/helper-validator-option" "^7.18.6" - browserslist "^4.21.3" + "@babel/compat-data" "^7.25.9" + "@babel/helper-validator-option" "^7.25.9" + browserslist "^4.24.0" lru-cache "^5.1.1" - semver "^6.3.0" - -"@babel/helper-create-class-features-plugin@^7.18.6", "@babel/helper-create-class-features-plugin@^7.20.12", "@babel/helper-create-class-features-plugin@^7.20.5", "@babel/helper-create-class-features-plugin@^7.20.7": - version "7.20.12" - resolved "https://registry.npmjs.org/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.20.12.tgz" - integrity sha512-9OunRkbT0JQcednL0UFvbfXpAsUXiGjUk0a7sN8fUXX7Mue79cUSMjHGDRRi/Vz9vYlpIhLV5fMD5dKoMhhsNQ== - dependencies: - "@babel/helper-annotate-as-pure" "^7.18.6" - "@babel/helper-environment-visitor" "^7.18.9" - "@babel/helper-function-name" "^7.19.0" - "@babel/helper-member-expression-to-functions" "^7.20.7" - "@babel/helper-optimise-call-expression" "^7.18.6" - "@babel/helper-replace-supers" "^7.20.7" - "@babel/helper-skip-transparent-expression-wrappers" "^7.20.0" - "@babel/helper-split-export-declaration" "^7.18.6" - -"@babel/helper-create-regexp-features-plugin@^7.18.6", "@babel/helper-create-regexp-features-plugin@^7.20.5": + semver "^6.3.1" + +"@babel/helper-create-class-features-plugin@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.25.9.tgz#7644147706bb90ff613297d49ed5266bde729f83" + integrity sha512-UTZQMvt0d/rSz6KI+qdu7GQze5TIajwTS++GUozlw8VBJDEOAqSXwm1WvmYEZwqdqSGQshRocPDqrt4HBZB3fQ== + dependencies: + "@babel/helper-annotate-as-pure" "^7.25.9" + "@babel/helper-member-expression-to-functions" "^7.25.9" + "@babel/helper-optimise-call-expression" "^7.25.9" + "@babel/helper-replace-supers" "^7.25.9" + "@babel/helper-skip-transparent-expression-wrappers" "^7.25.9" + "@babel/traverse" "^7.25.9" + semver "^6.3.1" + +"@babel/helper-create-regexp-features-plugin@^7.18.6": version "7.20.5" resolved "https://registry.npmjs.org/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.20.5.tgz" integrity sha512-m68B1lkg3XDGX5yCvGO0kPx3v9WIYLnzjKfPcQiwntEQa5ZeRkPmo2X/ISJc8qxWGfwUr+kvZAeEzAwLec2r2w== @@ -252,51 +379,33 @@ "@babel/helper-annotate-as-pure" "^7.18.6" regexpu-core "^5.2.1" -"@babel/helper-define-polyfill-provider@^0.3.3": - version "0.3.3" - resolved "https://registry.npmjs.org/@babel/helper-define-polyfill-provider/-/helper-define-polyfill-provider-0.3.3.tgz" - integrity sha512-z5aQKU4IzbqCC1XH0nAqfsFLMVSo22SBKUc0BxGrLkolTdPTructy0ToNnlO2zA4j9Q/7pjMZf0DSY+DSTYzww== +"@babel/helper-create-regexp-features-plugin@^7.25.9": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/helper-create-regexp-features-plugin/-/helper-create-regexp-features-plugin-7.26.3.tgz#5169756ecbe1d95f7866b90bb555b022595302a0" + integrity sha512-G7ZRb40uUgdKOQqPLjfD12ZmGA54PzqDFUv2BKImnC9QIfGhIHKvVML0oN8IUiDq4iRqpq74ABpvOaerfWdong== dependencies: - "@babel/helper-compilation-targets" "^7.17.7" - "@babel/helper-plugin-utils" "^7.16.7" + "@babel/helper-annotate-as-pure" "^7.25.9" + regexpu-core "^6.2.0" + semver "^6.3.1" + +"@babel/helper-define-polyfill-provider@^0.6.2", "@babel/helper-define-polyfill-provider@^0.6.3": + version "0.6.3" + resolved "https://registry.yarnpkg.com/@babel/helper-define-polyfill-provider/-/helper-define-polyfill-provider-0.6.3.tgz#f4f2792fae2ef382074bc2d713522cf24e6ddb21" + integrity sha512-HK7Bi+Hj6H+VTHA3ZvBis7V/6hu9QuTrnMXNybfUf2iiuU/N97I8VjB+KbhFF8Rld/Lx5MzoCwPCpPjfK+n8Cg== + dependencies: + "@babel/helper-compilation-targets" "^7.22.6" + "@babel/helper-plugin-utils" "^7.22.5" debug "^4.1.1" lodash.debounce "^4.0.8" resolve "^1.14.2" - semver "^6.1.2" - -"@babel/helper-environment-visitor@^7.18.9", "@babel/helper-environment-visitor@^7.22.20": - version "7.22.20" - resolved "https://registry.npmjs.org/@babel/helper-environment-visitor/-/helper-environment-visitor-7.22.20.tgz" - integrity sha512-zfedSIzFhat/gFhWfHtgWvlec0nqB9YEIVrpuwjruLlXfUSnA8cJB0miHKwqDnQ7d32aKo2xt88/xZptwxbfhA== - -"@babel/helper-explode-assignable-expression@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/helper-explode-assignable-expression/-/helper-explode-assignable-expression-7.18.6.tgz" - integrity sha512-eyAYAsQmB80jNfg4baAtLeWAQHfHFiR483rzFK+BhETlGZaQC9bsfrugfXDCbRHLQbIA7U5NxhhOxN7p/dWIcg== - dependencies: - "@babel/types" "^7.18.6" - -"@babel/helper-function-name@^7.18.9", "@babel/helper-function-name@^7.19.0", "@babel/helper-function-name@^7.23.0": - version "7.23.0" - resolved "https://registry.npmjs.org/@babel/helper-function-name/-/helper-function-name-7.23.0.tgz" - integrity sha512-OErEqsrxjZTJciZ4Oo+eoZqeW9UIiOcuYKRJA4ZAgV9myA+pOXhhmpfNCKjEH/auVfEYVFJ6y1Tc4r0eIApqiw== - dependencies: - "@babel/template" "^7.22.15" - "@babel/types" "^7.23.0" - -"@babel/helper-hoist-variables@^7.18.6", "@babel/helper-hoist-variables@^7.22.5": - version "7.22.5" - resolved "https://registry.npmjs.org/@babel/helper-hoist-variables/-/helper-hoist-variables-7.22.5.tgz" - integrity sha512-wGjk9QZVzvknA6yKIUURb8zY3grXCcOZt+/7Wcy8O2uctxhplmUPkOdlgoNhmdVee2c92JXbf1xpMtVNbfoxRw== - dependencies: - "@babel/types" "^7.22.5" -"@babel/helper-member-expression-to-functions@^7.20.7": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.20.7.tgz" - integrity sha512-9J0CxJLq315fEdi4s7xK5TQaNYjZw+nDVpVqr1axNGKzdrdwYBD5b4uKv3n75aABG0rCCTK8Im8Ww7eYfMrZgw== +"@babel/helper-member-expression-to-functions@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.25.9.tgz#9dfffe46f727005a5ea29051ac835fb735e4c1a3" + integrity sha512-wbfdZ9w5vk0C0oyHqAJbc62+vet5prjj01jjJ8sKn3j9h3MQQlflEdXYvuqRWjHnM12coDEqiC1IRCi0U/EKwQ== dependencies: - "@babel/types" "^7.20.7" + "@babel/traverse" "^7.25.9" + "@babel/types" "^7.25.9" "@babel/helper-module-imports@^7.18.6": version "7.18.6" @@ -305,113 +414,112 @@ dependencies: "@babel/types" "^7.18.6" -"@babel/helper-module-transforms@^7.12.1", "@babel/helper-module-transforms@^7.18.6", "@babel/helper-module-transforms@^7.20.11": - version "7.20.11" - resolved "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.20.11.tgz" - integrity sha512-uRy78kN4psmji1s2QtbtcCSaj/LILFDp0f/ymhpQH5QY3nljUZCaNWz9X1dEj/8MBdBEFECs7yRhKn8i7NjZgg== +"@babel/helper-module-imports@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-module-imports/-/helper-module-imports-7.25.9.tgz#e7f8d20602ebdbf9ebbea0a0751fb0f2a4141715" + integrity sha512-tnUA4RsrmflIM6W6RFTLFSXITtl0wKjgpnLgXyowocVPrbYrLUXSBXDgTs8BlbmIzIdlBySRQjINYs2BAkiLtw== dependencies: - "@babel/helper-environment-visitor" "^7.18.9" - "@babel/helper-module-imports" "^7.18.6" - "@babel/helper-simple-access" "^7.20.2" - "@babel/helper-split-export-declaration" "^7.18.6" - "@babel/helper-validator-identifier" "^7.19.1" - "@babel/template" "^7.20.7" - "@babel/traverse" "^7.20.10" - "@babel/types" "^7.20.7" + "@babel/traverse" "^7.25.9" + "@babel/types" "^7.25.9" -"@babel/helper-optimise-call-expression@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.18.6.tgz" - integrity sha512-HP59oD9/fEHQkdcbgFCnbmgH5vIQTJbxh2yf+CdM89/glUNnuzr87Q8GIjGEnOktTROemO0Pe0iPAYbqZuOUiA== +"@babel/helper-module-transforms@^7.25.9", "@babel/helper-module-transforms@^7.26.0": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/helper-module-transforms/-/helper-module-transforms-7.26.0.tgz#8ce54ec9d592695e58d84cd884b7b5c6a2fdeeae" + integrity sha512-xO+xu6B5K2czEnQye6BHA7DolFFmS3LB7stHZFaOLb1pAwO1HWLS8fXA+eh0A2yIvltPVmx3eNNDBJA2SLHXFw== dependencies: - "@babel/types" "^7.18.6" + "@babel/helper-module-imports" "^7.25.9" + "@babel/helper-validator-identifier" "^7.25.9" + "@babel/traverse" "^7.25.9" -"@babel/helper-plugin-utils@7.10.4": - version "7.10.4" - resolved "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.10.4.tgz" - integrity sha512-O4KCvQA6lLiMU9l2eawBPMf1xPP8xPfB3iEQw150hOVTqj/rfXz0ThTb4HEzqQfs2Bmo5Ay8BzxfzVtBrr9dVg== +"@babel/helper-optimise-call-expression@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.25.9.tgz#3324ae50bae7e2ab3c33f60c9a877b6a0146b54e" + integrity sha512-FIpuNaz5ow8VyrYcnXQTDRGvV6tTjkNtCK/RYNDXGSLlUD6cBuQTSw43CShGxjvfBTfcUA/r6UhUCbtYqkhcuQ== + dependencies: + "@babel/types" "^7.25.9" -"@babel/helper-plugin-utils@^7.0.0", "@babel/helper-plugin-utils@^7.10.4", "@babel/helper-plugin-utils@^7.12.13", "@babel/helper-plugin-utils@^7.14.5", "@babel/helper-plugin-utils@^7.16.7", "@babel/helper-plugin-utils@^7.18.6", "@babel/helper-plugin-utils@^7.18.9", "@babel/helper-plugin-utils@^7.19.0", "@babel/helper-plugin-utils@^7.20.2", "@babel/helper-plugin-utils@^7.8.0", "@babel/helper-plugin-utils@^7.8.3": +"@babel/helper-plugin-utils@^7.0.0", "@babel/helper-plugin-utils@^7.18.6", "@babel/helper-plugin-utils@^7.20.2", "@babel/helper-plugin-utils@^7.8.0": version "7.20.2" resolved "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.20.2.tgz" integrity sha512-8RvlJG2mj4huQ4pZ+rU9lqKi9ZKiRmuvGuM2HlWmkmgOhbs6zEAw6IEiJ5cQqGbDzGZOhwuOQNtZMi/ENLjZoQ== -"@babel/helper-remap-async-to-generator@^7.18.9": - version "7.18.9" - resolved "https://registry.npmjs.org/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.18.9.tgz" - integrity sha512-dI7q50YKd8BAv3VEfgg7PS7yD3Rtbi2J1XMXaalXO0W0164hYLnh8zpjRS0mte9MfVp/tltvr/cfdXPvJr1opA== - dependencies: - "@babel/helper-annotate-as-pure" "^7.18.6" - "@babel/helper-environment-visitor" "^7.18.9" - "@babel/helper-wrap-function" "^7.18.9" - "@babel/types" "^7.18.9" - -"@babel/helper-replace-supers@^7.18.6", "@babel/helper-replace-supers@^7.20.7": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/helper-replace-supers/-/helper-replace-supers-7.20.7.tgz" - integrity sha512-vujDMtB6LVfNW13jhlCrp48QNslK6JXi7lQG736HVbHz/mbf4Dc7tIRh1Xf5C0rF7BP8iiSxGMCmY6Ci1ven3A== - dependencies: - "@babel/helper-environment-visitor" "^7.18.9" - "@babel/helper-member-expression-to-functions" "^7.20.7" - "@babel/helper-optimise-call-expression" "^7.18.6" - "@babel/template" "^7.20.7" - "@babel/traverse" "^7.20.7" - "@babel/types" "^7.20.7" +"@babel/helper-plugin-utils@^7.22.5", "@babel/helper-plugin-utils@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-plugin-utils/-/helper-plugin-utils-7.25.9.tgz#9cbdd63a9443a2c92a725cca7ebca12cc8dd9f46" + integrity sha512-kSMlyUVdWe25rEsRGviIgOWnoT/nfABVWlqt9N19/dIPWViAOW2s9wznP5tURbs/IDuNk4gPy3YdYRgH3uxhBw== -"@babel/helper-simple-access@^7.20.2": - version "7.20.2" - resolved "https://registry.npmjs.org/@babel/helper-simple-access/-/helper-simple-access-7.20.2.tgz" - integrity sha512-+0woI/WPq59IrqDYbVGfshjT5Dmk/nnbdpcF8SnMhhXObpTq2KNBdLFRFrkVdbDOyUmHBCxzm5FHV1rACIkIbA== +"@babel/helper-remap-async-to-generator@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.25.9.tgz#e53956ab3d5b9fb88be04b3e2f31b523afd34b92" + integrity sha512-IZtukuUeBbhgOcaW2s06OXTzVNJR0ybm4W5xC1opWFFJMZbwRj5LCk+ByYH7WdZPZTt8KnFwA8pvjN2yqcPlgw== dependencies: - "@babel/types" "^7.20.2" + "@babel/helper-annotate-as-pure" "^7.25.9" + "@babel/helper-wrap-function" "^7.25.9" + "@babel/traverse" "^7.25.9" -"@babel/helper-skip-transparent-expression-wrappers@^7.20.0": - version "7.20.0" - resolved "https://registry.npmjs.org/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.20.0.tgz" - integrity sha512-5y1JYeNKfvnT8sZcK9DVRtpTbGiomYIHviSP3OQWmDPU3DeH4a1ZlT/N2lyQ5P8egjcRaT/Y9aNqUxK0WsnIIg== +"@babel/helper-replace-supers@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.25.9.tgz#ba447224798c3da3f8713fc272b145e33da6a5c5" + integrity sha512-IiDqTOTBQy0sWyeXyGSC5TBJpGFXBkRynjBeXsvbhQFKj2viwJC76Epz35YLU1fpe/Am6Vppb7W7zM4fPQzLsQ== dependencies: - "@babel/types" "^7.20.0" + "@babel/helper-member-expression-to-functions" "^7.25.9" + "@babel/helper-optimise-call-expression" "^7.25.9" + "@babel/traverse" "^7.25.9" -"@babel/helper-split-export-declaration@^7.18.6", "@babel/helper-split-export-declaration@^7.22.6": - version "7.22.6" - resolved "https://registry.npmjs.org/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.22.6.tgz" - integrity sha512-AsUnxuLhRYsisFiaJwvp1QF+I3KjD5FOxut14q/GzovUe6orHLesW2C7d754kRm53h5gqrz6sFl6sxc4BVtE/g== +"@babel/helper-skip-transparent-expression-wrappers@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-skip-transparent-expression-wrappers/-/helper-skip-transparent-expression-wrappers-7.25.9.tgz#0b2e1b62d560d6b1954893fd2b705dc17c91f0c9" + integrity sha512-K4Du3BFa3gvyhzgPcntrkDgZzQaq6uozzcpGbOO1OEJaI+EJdqWIMTLgFgQf6lrfiDFo5FU+BxKepI9RmZqahA== dependencies: - "@babel/types" "^7.22.5" + "@babel/traverse" "^7.25.9" + "@babel/types" "^7.25.9" "@babel/helper-string-parser@^7.22.5": version "7.22.5" resolved "https://registry.npmjs.org/@babel/helper-string-parser/-/helper-string-parser-7.22.5.tgz" integrity sha512-mM4COjgZox8U+JcXQwPijIZLElkgEpO5rsERVDJTc2qfCDfERyob6k5WegS14SX18IIjv+XD+GrqNumY5JRCDw== -"@babel/helper-validator-identifier@^7.19.1", "@babel/helper-validator-identifier@^7.22.20": +"@babel/helper-string-parser@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-string-parser/-/helper-string-parser-7.25.9.tgz#1aabb72ee72ed35789b4bbcad3ca2862ce614e8c" + integrity sha512-4A/SCr/2KLd5jrtOMFzaKjVtAei3+2r/NChoBNoZ3EyP/+GlhoaEGoWOZUmFmoITP7zOJyHIMm+DYRd8o3PvHA== + +"@babel/helper-validator-identifier@^7.22.20": version "7.22.20" resolved "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.22.20.tgz" integrity sha512-Y4OZ+ytlatR8AI+8KZfKuL5urKp7qey08ha31L8b3BwewJAoJamTzyvxPR/5D+KkdJCGPq/+8TukHBlY10FX9A== +"@babel/helper-validator-identifier@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.25.9.tgz#24b64e2c3ec7cd3b3c547729b8d16871f22cbdc7" + integrity sha512-Ed61U6XJc3CVRfkERJWDz4dJwKe7iLmmJsbOGu9wSloNSFttHV0I8g6UAgb7qnK5ly5bGLPd4oXZlxCdANBOWQ== + "@babel/helper-validator-option@^7.18.6": version "7.18.6" resolved "https://registry.npmjs.org/@babel/helper-validator-option/-/helper-validator-option-7.18.6.tgz" integrity sha512-XO7gESt5ouv/LRJdrVjkShckw6STTaB7l9BrpBaAHDeF5YZT+01PCwmR0SJHnkW6i8OwW/EVWRShfi4j2x+KQw== -"@babel/helper-wrap-function@^7.18.9": - version "7.20.5" - resolved "https://registry.npmjs.org/@babel/helper-wrap-function/-/helper-wrap-function-7.20.5.tgz" - integrity sha512-bYMxIWK5mh+TgXGVqAtnu5Yn1un+v8DDZtqyzKRLUzrh70Eal2O3aZ7aPYiMADO4uKlkzOiRiZ6GX5q3qxvW9Q== +"@babel/helper-validator-option@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-validator-option/-/helper-validator-option-7.25.9.tgz#86e45bd8a49ab7e03f276577f96179653d41da72" + integrity sha512-e/zv1co8pp55dNdEcCynfj9X7nyUKUXoUEwfXqaZt0omVOmDe9oOTdKStH4GmAw6zxMFs50ZayuMfHDKlO7Tfw== + +"@babel/helper-wrap-function@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/helper-wrap-function/-/helper-wrap-function-7.25.9.tgz#d99dfd595312e6c894bd7d237470025c85eea9d0" + integrity sha512-ETzz9UTjQSTmw39GboatdymDq4XIQbR8ySgVrylRhPOFpsd+JrKHIuF0de7GCWmem+T4uC5z7EZguod7Wj4A4g== dependencies: - "@babel/helper-function-name" "^7.19.0" - "@babel/template" "^7.18.10" - "@babel/traverse" "^7.20.5" - "@babel/types" "^7.20.5" + "@babel/template" "^7.25.9" + "@babel/traverse" "^7.25.9" + "@babel/types" "^7.25.9" -"@babel/helpers@^7.12.5", "@babel/helpers@^7.20.7": - version "7.20.13" - resolved "https://registry.npmjs.org/@babel/helpers/-/helpers-7.20.13.tgz" - integrity sha512-nzJ0DWCL3gB5RCXbUO3KIMMsBY2Eqbx8mBpKGE/02PgyRQFcPQLbkQ1vyy596mZLaP+dAfD+R4ckASzNVmW3jg== +"@babel/helpers@^7.26.0": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.26.0.tgz#30e621f1eba5aa45fe6f4868d2e9154d884119a4" + integrity sha512-tbhNuIxNcVb21pInl3ZSjksLCvgdZy9KwJ8brv993QtIVKJBBkYXz4q4ZbAv31GdnC+R90np23L5FbEBlthAEw== dependencies: - "@babel/template" "^7.20.7" - "@babel/traverse" "^7.20.13" - "@babel/types" "^7.20.7" + "@babel/template" "^7.25.9" + "@babel/types" "^7.26.0" "@babel/highlight@^7.22.13": version "7.22.20" @@ -422,482 +530,410 @@ chalk "^2.4.2" js-tokens "^4.0.0" -"@babel/parser@^7.12.7", "@babel/parser@^7.18.8", "@babel/parser@^7.20.7", "@babel/parser@^7.22.15", "@babel/parser@^7.23.0": - version "7.23.0" - resolved "https://registry.npmjs.org/@babel/parser/-/parser-7.23.0.tgz" - integrity sha512-vvPKKdMemU85V9WE/l5wZEmImpCtLqbnTvqDS2U1fJ96KrxoW7KrXhNsNCblQlg8Ck4b85yxdTyelsMUgFUXiw== - -"@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression/-/plugin-bugfix-safari-id-destructuring-collision-in-function-expression-7.18.6.tgz" - integrity sha512-Dgxsyg54Fx1d4Nge8UnvTrED63vrwOdPmyvPzlNN/boaliRP54pm3pGzZD1SJUwrBA+Cs/xdG8kXX6Mn/RfISQ== +"@babel/parser@^7.25.9", "@babel/parser@^7.26.0", "@babel/parser@^7.26.3": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.26.3.tgz#8c51c5db6ddf08134af1ddbacf16aaab48bac234" + integrity sha512-WJ/CvmY8Mea8iDXo6a7RK2wbmJITT5fN3BEkRuFlxVyNx8jOKIIhmC4fSkTcPcf8JyavbBwIe6OpiCOBXt/IcA== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/types" "^7.26.3" -"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@^7.18.9": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining/-/plugin-bugfix-v8-spread-parameters-in-optional-chaining-7.20.7.tgz" - integrity sha512-sbr9+wNE5aXMBBFBICk01tt7sBf2Oc9ikRFEcem/ZORup9IMUdNhW7/wVLEbbtlWOsEubJet46mHAL2C8+2jKQ== +"@babel/plugin-bugfix-firefox-class-in-computed-class-key@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-firefox-class-in-computed-class-key/-/plugin-bugfix-firefox-class-in-computed-class-key-7.25.9.tgz#cc2e53ebf0a0340777fff5ed521943e253b4d8fe" + integrity sha512-ZkRyVkThtxQ/J6nv3JFYv1RYY+JT5BvU0y3k5bWrmuG4woXypRa4PXmm9RhOwodRkYFWqC0C0cqcJ4OqR7kW+g== dependencies: - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-skip-transparent-expression-wrappers" "^7.20.0" - "@babel/plugin-proposal-optional-chaining" "^7.20.7" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/traverse" "^7.25.9" -"@babel/plugin-proposal-async-generator-functions@^7.20.1": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.20.7.tgz" - integrity sha512-xMbiLsn/8RK7Wq7VeVytytS2L6qE69bXPB10YCmMdDZbKF4okCqY74pI/jJQ/8U0b/F6NrT2+14b8/P9/3AMGA== +"@babel/plugin-bugfix-safari-class-field-initializer-scope@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-safari-class-field-initializer-scope/-/plugin-bugfix-safari-class-field-initializer-scope-7.25.9.tgz#af9e4fb63ccb8abcb92375b2fcfe36b60c774d30" + integrity sha512-MrGRLZxLD/Zjj0gdU15dfs+HH/OXvnw/U4jJD8vpcP2CJQapPEv1IWwjc/qMg7ItBlPwSv1hRBbb7LeuANdcnw== dependencies: - "@babel/helper-environment-visitor" "^7.18.9" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-remap-async-to-generator" "^7.18.9" - "@babel/plugin-syntax-async-generators" "^7.8.4" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-proposal-class-properties@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.18.6.tgz" - integrity sha512-cumfXOF0+nzZrrN8Rf0t7M+tF6sZc7vhQwYQck9q1/5w2OExlD+b4v4RpMJFaV1Z7WcDRgO6FqvxqxGlwo+RHQ== +"@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression/-/plugin-bugfix-safari-id-destructuring-collision-in-function-expression-7.25.9.tgz#e8dc26fcd616e6c5bf2bd0d5a2c151d4f92a9137" + integrity sha512-2qUwwfAFpJLZqxd02YW9btUCZHl+RFvdDkNfZwaIJrvB8Tesjsk8pEQkTvGwZXLqXUx/2oyY3ySRhm6HOXuCug== dependencies: - "@babel/helper-create-class-features-plugin" "^7.18.6" - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-proposal-class-static-block@^7.18.6": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-class-static-block/-/plugin-proposal-class-static-block-7.20.7.tgz" - integrity sha512-AveGOoi9DAjUYYuUAG//Ig69GlazLnoyzMw68VCDux+c1tsnnH/OkYcpz/5xzMkEFC6UxjR5Gw1c+iY2wOGVeQ== +"@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining/-/plugin-bugfix-v8-spread-parameters-in-optional-chaining-7.25.9.tgz#807a667f9158acac6f6164b4beb85ad9ebc9e1d1" + integrity sha512-6xWgLZTJXwilVjlnV7ospI3xi+sl8lN8rXXbBD6vYn3UYDlGsag8wrZkKcSI8G6KgqKP7vNFaDgeDnfAABq61g== dependencies: - "@babel/helper-create-class-features-plugin" "^7.20.7" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/plugin-syntax-class-static-block" "^7.14.5" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-skip-transparent-expression-wrappers" "^7.25.9" + "@babel/plugin-transform-optional-chaining" "^7.25.9" -"@babel/plugin-proposal-dynamic-import@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.18.6.tgz" - integrity sha512-1auuwmK+Rz13SJj36R+jqFPMJWyKEDd7lLSdOj4oJK0UTgGueSAtkrCvz9ewmgyU/P941Rv2fQwZJN8s6QruXw== +"@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly/-/plugin-bugfix-v8-static-class-fields-redefine-readonly-7.25.9.tgz#de7093f1e7deaf68eadd7cc6b07f2ab82543269e" + integrity sha512-aLnMXYPnzwwqhYSCyXfKkIkYgJ8zv9RK+roo9DkTXz38ynIhd9XCbN08s3MGvqL2MYGVUGdRQLL/JqBIeJhJBg== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" - "@babel/plugin-syntax-dynamic-import" "^7.8.3" - -"@babel/plugin-proposal-export-namespace-from@^7.18.9": - version "7.18.9" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-export-namespace-from/-/plugin-proposal-export-namespace-from-7.18.9.tgz" - integrity sha512-k1NtHyOMvlDDFeb9G5PhUXuGj8m/wiwojgQVEhJ/fsVsMCpLyOP4h0uGEjYJKrRI+EVPlb5Jk+Gt9P97lOGwtA== - dependencies: - "@babel/helper-plugin-utils" "^7.18.9" - "@babel/plugin-syntax-export-namespace-from" "^7.8.3" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/traverse" "^7.25.9" -"@babel/plugin-proposal-json-strings@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-json-strings/-/plugin-proposal-json-strings-7.18.6.tgz" - integrity sha512-lr1peyn9kOdbYc0xr0OdHTZ5FMqS6Di+H0Fz2I/JwMzGmzJETNeOFq2pBySw6X/KFL5EWDjlJuMsUGRFb8fQgQ== - dependencies: - "@babel/helper-plugin-utils" "^7.18.6" - "@babel/plugin-syntax-json-strings" "^7.8.3" +"@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2": + version "7.21.0-placeholder-for-preset-env.2" + resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-private-property-in-object/-/plugin-proposal-private-property-in-object-7.21.0-placeholder-for-preset-env.2.tgz#7844f9289546efa9febac2de4cfe358a050bd703" + integrity sha512-SOSkfJDddaM7mak6cPEpswyTRnuRltl429hMraQEglW+OkovnCzsiszTmsrlY//qLFjCpQDFRvjdm2wA5pPm9w== -"@babel/plugin-proposal-logical-assignment-operators@^7.18.9": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-logical-assignment-operators/-/plugin-proposal-logical-assignment-operators-7.20.7.tgz" - integrity sha512-y7C7cZgpMIjWlKE5T7eJwp+tnRYM89HmRvWM5EQuB5BoHEONjmQ8lSNmBUwOyy/GFRsohJED51YBF79hE1djug== - dependencies: - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/plugin-syntax-logical-assignment-operators" "^7.10.4" - -"@babel/plugin-proposal-nullish-coalescing-operator@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-nullish-coalescing-operator/-/plugin-proposal-nullish-coalescing-operator-7.18.6.tgz" - integrity sha512-wQxQzxYeJqHcfppzBDnm1yAY0jSRkUXR2z8RePZYrKwMKgMlE8+Z6LUno+bd6LvbGh8Gltvy74+9pIYkr+XkKA== - dependencies: - "@babel/helper-plugin-utils" "^7.18.6" - "@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.3" - -"@babel/plugin-proposal-numeric-separator@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-numeric-separator/-/plugin-proposal-numeric-separator-7.18.6.tgz" - integrity sha512-ozlZFogPqoLm8WBr5Z8UckIoE4YQ5KESVcNudyXOR8uqIkliTEgJ3RoketfG6pmzLdeZF0H/wjE9/cCEitBl7Q== +"@babel/plugin-syntax-dynamic-import@^7.8.3": + version "7.8.3" + resolved "https://registry.npmjs.org/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.8.3.tgz" + integrity sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" - "@babel/plugin-syntax-numeric-separator" "^7.10.4" + "@babel/helper-plugin-utils" "^7.8.0" -"@babel/plugin-proposal-object-rest-spread@7.12.1": - version "7.12.1" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.12.1.tgz" - integrity sha512-s6SowJIjzlhx8o7lsFx5zmY4At6CTtDvgNQDdPzkBQucle58A6b/TTeEBYtyDgmcXjUTM+vE8YOGHZzzbc/ioA== +"@babel/plugin-syntax-import-assertions@^7.26.0": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-import-assertions/-/plugin-syntax-import-assertions-7.26.0.tgz#620412405058efa56e4a564903b79355020f445f" + integrity sha512-QCWT5Hh830hK5EQa7XzuqIkQU9tT/whqbDz7kuaZMHFl1inRRg7JnuAEOQ0Ur0QUl0NufCk1msK2BeY79Aj/eg== dependencies: - "@babel/helper-plugin-utils" "^7.10.4" - "@babel/plugin-syntax-object-rest-spread" "^7.8.0" - "@babel/plugin-transform-parameters" "^7.12.1" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-proposal-object-rest-spread@^7.20.2": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.20.7.tgz" - integrity sha512-d2S98yCiLxDVmBmE8UjGcfPvNEUbA1U5q5WxaWFUGRzJSVAZqm5W6MbPct0jxnegUZ0niLeNX+IOzEs7wYg9Dg== +"@babel/plugin-syntax-import-attributes@^7.26.0": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-import-attributes/-/plugin-syntax-import-attributes-7.26.0.tgz#3b1412847699eea739b4f2602c74ce36f6b0b0f7" + integrity sha512-e2dttdsJ1ZTpi3B9UYGLw41hifAubg19AtCu/2I/F1QNVclOBr1dYpTdmdyZ84Xiz43BS/tCUkMAZNLv12Pi+A== dependencies: - "@babel/compat-data" "^7.20.5" - "@babel/helper-compilation-targets" "^7.20.7" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/plugin-syntax-object-rest-spread" "^7.8.3" - "@babel/plugin-transform-parameters" "^7.20.7" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-proposal-optional-catch-binding@^7.18.6": +"@babel/plugin-syntax-jsx@^7.18.6": version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-optional-catch-binding/-/plugin-proposal-optional-catch-binding-7.18.6.tgz" - integrity sha512-Q40HEhs9DJQyaZfUjjn6vE8Cv4GmMHCYuMGIWUnlxH6400VGxOuwWsPt4FxXxJkC/5eOzgn0z21M9gMT4MOhbw== + resolved "https://registry.npmjs.org/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.18.6.tgz" + integrity sha512-6mmljtAedFGTWu2p/8WIORGwy+61PLgOMPOdazc7YoJ9ZCWUyFy3A6CpPkRKLKD1ToAesxX8KGEViAiLo9N+7Q== dependencies: "@babel/helper-plugin-utils" "^7.18.6" - "@babel/plugin-syntax-optional-catch-binding" "^7.8.3" -"@babel/plugin-proposal-optional-chaining@^7.18.9", "@babel/plugin-proposal-optional-chaining@^7.20.7": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-optional-chaining/-/plugin-proposal-optional-chaining-7.20.7.tgz" - integrity sha512-T+A7b1kfjtRM51ssoOfS1+wbyCVqorfyZhT99TvxxLMirPShD8CzKMRepMlCBGM5RpHMbn8s+5MMHnPstJH6mQ== +"@babel/plugin-syntax-jsx@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.25.9.tgz#a34313a178ea56f1951599b929c1ceacee719290" + integrity sha512-ld6oezHQMZsZfp6pWtbjaNDF2tiiCYYDqQszHt5VV437lewP9aSi2Of99CK0D0XB21k7FLgnLcmQKyKzynfeAA== dependencies: - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-skip-transparent-expression-wrappers" "^7.20.0" - "@babel/plugin-syntax-optional-chaining" "^7.8.3" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-proposal-private-methods@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-private-methods/-/plugin-proposal-private-methods-7.18.6.tgz" - integrity sha512-nutsvktDItsNn4rpGItSNV2sz1XwS+nfU0Rg8aCx3W3NOKVzdMjJRu0O5OkgDp3ZGICSTbgRpxZoWsxoKRvbeA== - dependencies: - "@babel/helper-create-class-features-plugin" "^7.18.6" - "@babel/helper-plugin-utils" "^7.18.6" - -"@babel/plugin-proposal-private-property-in-object@^7.18.6": - version "7.20.5" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-private-property-in-object/-/plugin-proposal-private-property-in-object-7.20.5.tgz" - integrity sha512-Vq7b9dUA12ByzB4EjQTPo25sFhY+08pQDBSZRtUAkj7lb7jahaHR5igera16QZ+3my1nYR4dKsNdYj5IjPHilQ== +"@babel/plugin-syntax-typescript@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-typescript/-/plugin-syntax-typescript-7.25.9.tgz#67dda2b74da43727cf21d46cf9afef23f4365399" + integrity sha512-hjMgRy5hb8uJJjUcdWunWVcoi9bGpJp8p5Ol1229PoN6aytsLwNMgmdftO23wnCLMfVmTwZDWMPNq/D1SY60JQ== dependencies: - "@babel/helper-annotate-as-pure" "^7.18.6" - "@babel/helper-create-class-features-plugin" "^7.20.5" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/plugin-syntax-private-property-in-object" "^7.14.5" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-proposal-unicode-property-regex@^7.18.6", "@babel/plugin-proposal-unicode-property-regex@^7.4.4": +"@babel/plugin-syntax-unicode-sets-regex@^7.18.6": version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-proposal-unicode-property-regex/-/plugin-proposal-unicode-property-regex-7.18.6.tgz" - integrity sha512-2BShG/d5yoZyXZfVePH91urL5wTG6ASZU9M4o03lKK8u8UW1y08OMttBSOADTcJrnPMpvDXRG3G8fyLh4ovs8w== + resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-unicode-sets-regex/-/plugin-syntax-unicode-sets-regex-7.18.6.tgz#d49a3b3e6b52e5be6740022317580234a6a47357" + integrity sha512-727YkEAPwSIQTv5im8QHz3upqp92JTWhidIC81Tdx4VJYIte/VndKf1qKrfnnhPLiPghStWfvC/iFaMCQu7Nqg== dependencies: "@babel/helper-create-regexp-features-plugin" "^7.18.6" "@babel/helper-plugin-utils" "^7.18.6" -"@babel/plugin-syntax-async-generators@^7.8.4": - version "7.8.4" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.8.4.tgz" - integrity sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw== +"@babel/plugin-transform-arrow-functions@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.25.9.tgz#7821d4410bee5daaadbb4cdd9a6649704e176845" + integrity sha512-6jmooXYIwn9ca5/RylZADJ+EnSxVUS5sjeJ9UPk6RWRzXCmOJCy6dqItPJFpw2cuCangPK4OYr5uhGKcmrm5Qg== dependencies: - "@babel/helper-plugin-utils" "^7.8.0" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-class-properties@^7.12.13": - version "7.12.13" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-class-properties/-/plugin-syntax-class-properties-7.12.13.tgz" - integrity sha512-fm4idjKla0YahUNgFNLCB0qySdsoPiZP3iQE3rky0mBUtMZ23yDJ9SJdg6dXTSDnulOVqiF3Hgr9nbXvXTQZYA== +"@babel/plugin-transform-async-generator-functions@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-generator-functions/-/plugin-transform-async-generator-functions-7.25.9.tgz#1b18530b077d18a407c494eb3d1d72da505283a2" + integrity sha512-RXV6QAzTBbhDMO9fWwOmwwTuYaiPbggWQ9INdZqAYeSHyG7FzQ+nOZaUUjNwKv9pV3aE4WFqFm1Hnbci5tBCAw== dependencies: - "@babel/helper-plugin-utils" "^7.12.13" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-remap-async-to-generator" "^7.25.9" + "@babel/traverse" "^7.25.9" -"@babel/plugin-syntax-class-static-block@^7.14.5": - version "7.14.5" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-class-static-block/-/plugin-syntax-class-static-block-7.14.5.tgz" - integrity sha512-b+YyPmr6ldyNnM6sqYeMWE+bgJcJpO6yS4QD7ymxgH34GBPNDM/THBh8iunyvKIZztiwLH4CJZ0RxTk9emgpjw== +"@babel/plugin-transform-async-to-generator@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.25.9.tgz#c80008dacae51482793e5a9c08b39a5be7e12d71" + integrity sha512-NT7Ejn7Z/LjUH0Gv5KsBCxh7BH3fbLTV0ptHvpeMvrt3cPThHfJfst9Wrb7S8EvJ7vRTFI7z+VAvFVEQn/m5zQ== dependencies: - "@babel/helper-plugin-utils" "^7.14.5" + "@babel/helper-module-imports" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-remap-async-to-generator" "^7.25.9" -"@babel/plugin-syntax-dynamic-import@^7.8.3": - version "7.8.3" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.8.3.tgz" - integrity sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ== +"@babel/plugin-transform-block-scoped-functions@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.25.9.tgz#5700691dbd7abb93de300ca7be94203764fce458" + integrity sha512-toHc9fzab0ZfenFpsyYinOX0J/5dgJVA2fm64xPewu7CoYHWEivIWKxkK2rMi4r3yQqLnVmheMXRdG+k239CgA== dependencies: - "@babel/helper-plugin-utils" "^7.8.0" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-export-namespace-from@^7.8.3": - version "7.8.3" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-export-namespace-from/-/plugin-syntax-export-namespace-from-7.8.3.tgz" - integrity sha512-MXf5laXo6c1IbEbegDmzGPwGNTsHZmEy6QGznu5Sh2UCWvueywb2ee+CCE4zQiZstxU9BMoQO9i6zUFSY0Kj0Q== +"@babel/plugin-transform-block-scoping@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.25.9.tgz#c33665e46b06759c93687ca0f84395b80c0473a1" + integrity sha512-1F05O7AYjymAtqbsFETboN1NvBdcnzMerO+zlMyJBEz6WkMdejvGWw9p05iTSjC85RLlBseHHQpYaM4gzJkBGg== dependencies: - "@babel/helper-plugin-utils" "^7.8.3" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-import-assertions@^7.20.0": - version "7.20.0" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-import-assertions/-/plugin-syntax-import-assertions-7.20.0.tgz" - integrity sha512-IUh1vakzNoWalR8ch/areW7qFopR2AEw03JlG7BbrDqmQ4X3q9uuipQwSGrUn7oGiemKjtSLDhNtQHzMHr1JdQ== +"@babel/plugin-transform-class-properties@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-class-properties/-/plugin-transform-class-properties-7.25.9.tgz#a8ce84fedb9ad512549984101fa84080a9f5f51f" + integrity sha512-bbMAII8GRSkcd0h0b4X+36GksxuheLFjP65ul9w6C3KgAamI3JqErNgSrosX6ZPj+Mpim5VvEbawXxJCyEUV3Q== dependencies: - "@babel/helper-plugin-utils" "^7.19.0" + "@babel/helper-create-class-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-json-strings@^7.8.3": - version "7.8.3" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.8.3.tgz" - integrity sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA== +"@babel/plugin-transform-class-static-block@^7.26.0": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-class-static-block/-/plugin-transform-class-static-block-7.26.0.tgz#6c8da219f4eb15cae9834ec4348ff8e9e09664a0" + integrity sha512-6J2APTs7BDDm+UMqP1useWqhcRAXo0WIoVj26N7kPFB6S73Lgvyka4KTZYIxtgYXiN5HTyRObA72N2iu628iTQ== dependencies: - "@babel/helper-plugin-utils" "^7.8.0" + "@babel/helper-create-class-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-jsx@7.12.1": - version "7.12.1" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.12.1.tgz" - integrity sha512-1yRi7yAtB0ETgxdY9ti/p2TivUxJkTdhu/ZbF9MshVGqOx1TdB3b7xCXs49Fupgg50N45KcAsRP/ZqWjs9SRjg== +"@babel/plugin-transform-classes@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-classes/-/plugin-transform-classes-7.25.9.tgz#7152457f7880b593a63ade8a861e6e26a4469f52" + integrity sha512-mD8APIXmseE7oZvZgGABDyM34GUmK45Um2TXiBUt7PnuAxrgoSVf123qUzPxEr/+/BHrRn5NMZCdE2m/1F8DGg== dependencies: - "@babel/helper-plugin-utils" "^7.10.4" + "@babel/helper-annotate-as-pure" "^7.25.9" + "@babel/helper-compilation-targets" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-replace-supers" "^7.25.9" + "@babel/traverse" "^7.25.9" + globals "^11.1.0" -"@babel/plugin-syntax-jsx@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.18.6.tgz" - integrity sha512-6mmljtAedFGTWu2p/8WIORGwy+61PLgOMPOdazc7YoJ9ZCWUyFy3A6CpPkRKLKD1ToAesxX8KGEViAiLo9N+7Q== +"@babel/plugin-transform-computed-properties@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.25.9.tgz#db36492c78460e534b8852b1d5befe3c923ef10b" + integrity sha512-HnBegGqXZR12xbcTHlJ9HGxw1OniltT26J5YpfruGqtUHlz/xKf/G2ak9e+t0rVqrjXa9WOhvYPz1ERfMj23AA== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/template" "^7.25.9" -"@babel/plugin-syntax-logical-assignment-operators@^7.10.4": - version "7.10.4" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-logical-assignment-operators/-/plugin-syntax-logical-assignment-operators-7.10.4.tgz" - integrity sha512-d8waShlpFDinQ5MtvGU9xDAOzKH47+FFoney2baFIoMr952hKOLp1HR7VszoZvOsV/4+RRszNY7D17ba0te0ig== +"@babel/plugin-transform-destructuring@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.25.9.tgz#966ea2595c498224340883602d3cfd7a0c79cea1" + integrity sha512-WkCGb/3ZxXepmMiX101nnGiU+1CAdut8oHyEOHxkKuS1qKpU2SMXE2uSvfz8PBuLd49V6LEsbtyPhWC7fnkgvQ== dependencies: - "@babel/helper-plugin-utils" "^7.10.4" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-nullish-coalescing-operator@^7.8.3": - version "7.8.3" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-nullish-coalescing-operator/-/plugin-syntax-nullish-coalescing-operator-7.8.3.tgz" - integrity sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ== +"@babel/plugin-transform-dotall-regex@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.25.9.tgz#bad7945dd07734ca52fe3ad4e872b40ed09bb09a" + integrity sha512-t7ZQ7g5trIgSRYhI9pIJtRl64KHotutUJsh4Eze5l7olJv+mRSg4/MmbZ0tv1eeqRbdvo/+trvJD/Oc5DmW2cA== dependencies: - "@babel/helper-plugin-utils" "^7.8.0" + "@babel/helper-create-regexp-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-numeric-separator@^7.10.4": - version "7.10.4" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-numeric-separator/-/plugin-syntax-numeric-separator-7.10.4.tgz" - integrity sha512-9H6YdfkcK/uOnY/K7/aA2xpzaAgkQn37yzWUMRK7OaPOqOpGS1+n0H5hxT9AUw9EsSjPW8SVyMJwYRtWs3X3ug== +"@babel/plugin-transform-duplicate-keys@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.25.9.tgz#8850ddf57dce2aebb4394bb434a7598031059e6d" + integrity sha512-LZxhJ6dvBb/f3x8xwWIuyiAHy56nrRG3PeYTpBkkzkYRRQ6tJLu68lEF5VIqMUZiAV7a8+Tb78nEoMCMcqjXBw== dependencies: - "@babel/helper-plugin-utils" "^7.10.4" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-object-rest-spread@7.8.3", "@babel/plugin-syntax-object-rest-spread@^7.8.0", "@babel/plugin-syntax-object-rest-spread@^7.8.3": - version "7.8.3" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.8.3.tgz" - integrity sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA== +"@babel/plugin-transform-duplicate-named-capturing-groups-regex@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-named-capturing-groups-regex/-/plugin-transform-duplicate-named-capturing-groups-regex-7.25.9.tgz#6f7259b4de127721a08f1e5165b852fcaa696d31" + integrity sha512-0UfuJS0EsXbRvKnwcLjFtJy/Sxc5J5jhLHnFhy7u4zih97Hz6tJkLU+O+FMMrNZrosUPxDi6sYxJ/EA8jDiAog== dependencies: - "@babel/helper-plugin-utils" "^7.8.0" + "@babel/helper-create-regexp-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-optional-catch-binding@^7.8.3": - version "7.8.3" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-optional-catch-binding/-/plugin-syntax-optional-catch-binding-7.8.3.tgz" - integrity sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q== +"@babel/plugin-transform-dynamic-import@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-dynamic-import/-/plugin-transform-dynamic-import-7.25.9.tgz#23e917de63ed23c6600c5dd06d94669dce79f7b8" + integrity sha512-GCggjexbmSLaFhqsojeugBpeaRIgWNTcgKVq/0qIteFEqY2A+b9QidYadrWlnbWQUrW5fn+mCvf3tr7OeBFTyg== dependencies: - "@babel/helper-plugin-utils" "^7.8.0" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-optional-chaining@^7.8.3": - version "7.8.3" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-optional-chaining/-/plugin-syntax-optional-chaining-7.8.3.tgz" - integrity sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg== +"@babel/plugin-transform-exponentiation-operator@^7.25.9": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.26.3.tgz#e29f01b6de302c7c2c794277a48f04a9ca7f03bc" + integrity sha512-7CAHcQ58z2chuXPWblnn1K6rLDnDWieghSOEmqQsrBenH0P9InCUtOJYD89pvngljmZlJcz3fcmgYsXFNGa1ZQ== dependencies: - "@babel/helper-plugin-utils" "^7.8.0" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-private-property-in-object@^7.14.5": - version "7.14.5" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-private-property-in-object/-/plugin-syntax-private-property-in-object-7.14.5.tgz" - integrity sha512-0wVnp9dxJ72ZUJDV27ZfbSj6iHLoytYZmh3rFcxNnvsJF3ktkzLDZPy/mA17HGsaQT3/DQsWYX1f1QGWkCoVUg== +"@babel/plugin-transform-export-namespace-from@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-export-namespace-from/-/plugin-transform-export-namespace-from-7.25.9.tgz#90745fe55053394f554e40584cda81f2c8a402a2" + integrity sha512-2NsEz+CxzJIVOPx2o9UsW1rXLqtChtLoVnwYHHiB04wS5sgn7mrV45fWMBX0Kk+ub9uXytVYfNP2HjbVbCB3Ww== dependencies: - "@babel/helper-plugin-utils" "^7.14.5" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-syntax-top-level-await@^7.14.5": - version "7.14.5" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-top-level-await/-/plugin-syntax-top-level-await-7.14.5.tgz" - integrity sha512-hx++upLv5U1rgYfwe1xBQUhRmU41NEvpUvrp8jkrSCdvGSnM5/qdRMtylJ6PG5OFkBaHkbTAKTnd3/YyESRHFw== +"@babel/plugin-transform-for-of@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.25.9.tgz#4bdc7d42a213397905d89f02350c5267866d5755" + integrity sha512-LqHxduHoaGELJl2uhImHwRQudhCM50pT46rIBNvtT/Oql3nqiS3wOwP+5ten7NpYSXrrVLgtZU3DZmPtWZo16A== dependencies: - "@babel/helper-plugin-utils" "^7.14.5" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-skip-transparent-expression-wrappers" "^7.25.9" -"@babel/plugin-syntax-typescript@^7.20.0": - version "7.20.0" - resolved "https://registry.npmjs.org/@babel/plugin-syntax-typescript/-/plugin-syntax-typescript-7.20.0.tgz" - integrity sha512-rd9TkG+u1CExzS4SM1BlMEhMXwFLKVjOAFFCDx9PbX5ycJWDoWMcwdJH9RhkPu1dOgn5TrxLot/Gx6lWFuAUNQ== +"@babel/plugin-transform-function-name@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.25.9.tgz#939d956e68a606661005bfd550c4fc2ef95f7b97" + integrity sha512-8lP+Yxjv14Vc5MuWBpJsoUCd3hD6V9DgBon2FVYL4jJgbnVQ9fTgYmonchzZJOVNgzEgbxp4OwAf6xz6M/14XA== dependencies: - "@babel/helper-plugin-utils" "^7.19.0" + "@babel/helper-compilation-targets" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/traverse" "^7.25.9" -"@babel/plugin-transform-arrow-functions@^7.18.6": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.20.7.tgz" - integrity sha512-3poA5E7dzDomxj9WXWwuD6A5F3kc7VXwIJO+E+J8qtDtS+pXPAhrgEyh+9GBwBgPq1Z+bB+/JD60lp5jsN7JPQ== +"@babel/plugin-transform-json-strings@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-json-strings/-/plugin-transform-json-strings-7.25.9.tgz#c86db407cb827cded902a90c707d2781aaa89660" + integrity sha512-xoTMk0WXceiiIvsaquQQUaLLXSW1KJ159KP87VilruQm0LNNGxWzahxSS6T6i4Zg3ezp4vA4zuwiNUR53qmQAw== dependencies: - "@babel/helper-plugin-utils" "^7.20.2" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-async-to-generator@^7.18.6": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.20.7.tgz" - integrity sha512-Uo5gwHPT9vgnSXQxqGtpdufUiWp96gk7yiP4Mp5bm1QMkEmLXBO7PAGYbKoJ6DhAwiNkcHFBol/x5zZZkL/t0Q== +"@babel/plugin-transform-literals@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-literals/-/plugin-transform-literals-7.25.9.tgz#1a1c6b4d4aa59bc4cad5b6b3a223a0abd685c9de" + integrity sha512-9N7+2lFziW8W9pBl2TzaNht3+pgMIRP74zizeCSrtnSKVdUl8mAjjOP2OOVQAfZ881P2cNjDj1uAMEdeD50nuQ== dependencies: - "@babel/helper-module-imports" "^7.18.6" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-remap-async-to-generator" "^7.18.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-block-scoped-functions@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.18.6.tgz" - integrity sha512-ExUcOqpPWnliRcPqves5HJcJOvHvIIWfuS4sroBUenPuMdmW+SMHDakmtS7qOo13sVppmUijqeTv7qqGsvURpQ== +"@babel/plugin-transform-logical-assignment-operators@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-logical-assignment-operators/-/plugin-transform-logical-assignment-operators-7.25.9.tgz#b19441a8c39a2fda0902900b306ea05ae1055db7" + integrity sha512-wI4wRAzGko551Y8eVf6iOY9EouIDTtPb0ByZx+ktDGHwv6bHFimrgJM/2T021txPZ2s4c7bqvHbd+vXG6K948Q== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-block-scoping@^7.20.2": - version "7.20.14" - resolved "https://registry.npmjs.org/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.20.14.tgz" - integrity sha512-sMPepQtsOs5fM1bwNvuJJHvaCfOEQfmc01FGw0ELlTpTJj5Ql/zuNRRldYhAPys4ghXdBIQJbRVYi44/7QflQQ== +"@babel/plugin-transform-member-expression-literals@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.25.9.tgz#63dff19763ea64a31f5e6c20957e6a25e41ed5de" + integrity sha512-PYazBVfofCQkkMzh2P6IdIUaCEWni3iYEerAsRWuVd8+jlM1S9S9cz1dF9hIzyoZ8IA3+OwVYIp9v9e+GbgZhA== dependencies: - "@babel/helper-plugin-utils" "^7.20.2" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-classes@^7.20.2": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-transform-classes/-/plugin-transform-classes-7.20.7.tgz" - integrity sha512-LWYbsiXTPKl+oBlXUGlwNlJZetXD5Am+CyBdqhPsDVjM9Jc8jwBJFrKhHf900Kfk2eZG1y9MAG3UNajol7A4VQ== +"@babel/plugin-transform-modules-amd@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.25.9.tgz#49ba478f2295101544abd794486cd3088dddb6c5" + integrity sha512-g5T11tnI36jVClQlMlt4qKDLlWnG5pP9CSM4GhdRciTNMRgkfpo5cR6b4rGIOYPgRRuFAvwjPQ/Yk+ql4dyhbw== dependencies: - "@babel/helper-annotate-as-pure" "^7.18.6" - "@babel/helper-compilation-targets" "^7.20.7" - "@babel/helper-environment-visitor" "^7.18.9" - "@babel/helper-function-name" "^7.19.0" - "@babel/helper-optimise-call-expression" "^7.18.6" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-replace-supers" "^7.20.7" - "@babel/helper-split-export-declaration" "^7.18.6" - globals "^11.1.0" - -"@babel/plugin-transform-computed-properties@^7.18.9": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.20.7.tgz" - integrity sha512-Lz7MvBK6DTjElHAmfu6bfANzKcxpyNPeYBGEafyA6E5HtRpjpZwU+u7Qrgz/2OR0z+5TvKYbPdphfSaAcZBrYQ== - dependencies: - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/template" "^7.20.7" + "@babel/helper-module-transforms" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-destructuring@^7.20.2": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.20.7.tgz" - integrity sha512-Xwg403sRrZb81IVB79ZPqNQME23yhugYVqgTxAhT99h485F4f+GMELFhhOsscDUB7HCswepKeCKLn/GZvUKoBA== +"@babel/plugin-transform-modules-commonjs@^7.25.9": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.26.3.tgz#8f011d44b20d02c3de44d8850d971d8497f981fb" + integrity sha512-MgR55l4q9KddUDITEzEFYn5ZsGDXMSsU9E+kh7fjRXTIC3RHqfCo8RPRbyReYJh44HQ/yomFkqbOFohXvDCiIQ== dependencies: - "@babel/helper-plugin-utils" "^7.20.2" + "@babel/helper-module-transforms" "^7.26.0" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-dotall-regex@^7.18.6", "@babel/plugin-transform-dotall-regex@^7.4.4": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.18.6.tgz" - integrity sha512-6S3jpun1eEbAxq7TdjLotAsl4WpQI9DxfkycRcKrjhQYzU87qpXdknpBg/e+TdcMehqGnLFi7tnFUBR02Vq6wg== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.18.6" - "@babel/helper-plugin-utils" "^7.18.6" - -"@babel/plugin-transform-duplicate-keys@^7.18.9": - version "7.18.9" - resolved "https://registry.npmjs.org/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.18.9.tgz" - integrity sha512-d2bmXCtZXYc59/0SanQKbiWINadaJXqtvIQIzd4+hNwkWBgyCd5F/2t1kXoUdvPMrxzPvhK6EMQRROxsue+mfw== - dependencies: - "@babel/helper-plugin-utils" "^7.18.9" - -"@babel/plugin-transform-exponentiation-operator@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.18.6.tgz" - integrity sha512-wzEtc0+2c88FVR34aQmiz56dxEkxr2g8DQb/KfaFa1JYXOFVsbhvAonFN6PwVWj++fKmku8NP80plJ5Et4wqHw== +"@babel/plugin-transform-modules-systemjs@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.25.9.tgz#8bd1b43836269e3d33307151a114bcf3ba6793f8" + integrity sha512-hyss7iIlH/zLHaehT+xwiymtPOpsiwIIRlCAOwBB04ta5Tt+lNItADdlXw3jAWZ96VJ2jlhl/c+PNIQPKNfvcA== dependencies: - "@babel/helper-builder-binary-assignment-operator-visitor" "^7.18.6" - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-module-transforms" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-validator-identifier" "^7.25.9" + "@babel/traverse" "^7.25.9" -"@babel/plugin-transform-for-of@^7.18.8": - version "7.18.8" - resolved "https://registry.npmjs.org/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.18.8.tgz" - integrity sha512-yEfTRnjuskWYo0k1mHUqrVWaZwrdq8AYbfrpqULOJOaucGSp4mNMVps+YtA8byoevxS/urwU75vyhQIxcCgiBQ== +"@babel/plugin-transform-modules-umd@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.25.9.tgz#6710079cdd7c694db36529a1e8411e49fcbf14c9" + integrity sha512-bS9MVObUgE7ww36HEfwe6g9WakQ0KF07mQF74uuXdkoziUPfKyu/nIm663kz//e5O1nPInPFx36z7WJmJ4yNEw== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-module-transforms" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-function-name@^7.18.9": - version "7.18.9" - resolved "https://registry.npmjs.org/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.18.9.tgz" - integrity sha512-WvIBoRPaJQ5yVHzcnJFor7oS5Ls0PYixlTYE63lCj2RtdQEl15M68FXQlxnG6wdraJIXRdR7KI+hQ7q/9QjrCQ== +"@babel/plugin-transform-named-capturing-groups-regex@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.25.9.tgz#454990ae6cc22fd2a0fa60b3a2c6f63a38064e6a" + integrity sha512-oqB6WHdKTGl3q/ItQhpLSnWWOpjUJLsOCLVyeFgeTktkBSCiurvPOsyt93gibI9CmuKvTUEtWmG5VhZD+5T/KA== dependencies: - "@babel/helper-compilation-targets" "^7.18.9" - "@babel/helper-function-name" "^7.18.9" - "@babel/helper-plugin-utils" "^7.18.9" + "@babel/helper-create-regexp-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-literals@^7.18.9": - version "7.18.9" - resolved "https://registry.npmjs.org/@babel/plugin-transform-literals/-/plugin-transform-literals-7.18.9.tgz" - integrity sha512-IFQDSRoTPnrAIrI5zoZv73IFeZu2dhu6irxQjY9rNjTT53VmKg9fenjvoiOWOkJ6mm4jKVPtdMzBY98Fp4Z4cg== +"@babel/plugin-transform-new-target@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.25.9.tgz#42e61711294b105c248336dcb04b77054ea8becd" + integrity sha512-U/3p8X1yCSoKyUj2eOBIx3FOn6pElFOKvAAGf8HTtItuPyB+ZeOqfn+mvTtg9ZlOAjsPdK3ayQEjqHjU/yLeVQ== dependencies: - "@babel/helper-plugin-utils" "^7.18.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-member-expression-literals@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.18.6.tgz" - integrity sha512-qSF1ihLGO3q+/g48k85tUjD033C29TNTVB2paCwZPVmOsjn9pClvYYrM2VeJpBY2bcNkuny0YUyTNRyRxJ54KA== +"@babel/plugin-transform-nullish-coalescing-operator@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-nullish-coalescing-operator/-/plugin-transform-nullish-coalescing-operator-7.25.9.tgz#bcb1b0d9e948168102d5f7104375ca21c3266949" + integrity sha512-ENfftpLZw5EItALAD4WsY/KUWvhUlZndm5GC7G3evUsVeSJB6p0pBeLQUnRnBCBx7zV0RKQjR9kCuwrsIrjWog== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-modules-amd@^7.19.6": - version "7.20.11" - resolved "https://registry.npmjs.org/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.20.11.tgz" - integrity sha512-NuzCt5IIYOW0O30UvqktzHYR2ud5bOWbY0yaxWZ6G+aFzOMJvrs5YHNikrbdaT15+KNO31nPOy5Fim3ku6Zb5g== +"@babel/plugin-transform-numeric-separator@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-numeric-separator/-/plugin-transform-numeric-separator-7.25.9.tgz#bfed75866261a8b643468b0ccfd275f2033214a1" + integrity sha512-TlprrJ1GBZ3r6s96Yq8gEQv82s8/5HnCVHtEJScUj90thHQbwe+E5MLhi2bbNHBEJuzrvltXSru+BUxHDoog7Q== dependencies: - "@babel/helper-module-transforms" "^7.20.11" - "@babel/helper-plugin-utils" "^7.20.2" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-modules-commonjs@^7.19.6": - version "7.20.11" - resolved "https://registry.npmjs.org/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.20.11.tgz" - integrity sha512-S8e1f7WQ7cimJQ51JkAaDrEtohVEitXjgCGAS2N8S31Y42E+kWwfSz83LYz57QdBm7q9diARVqanIaH2oVgQnw== +"@babel/plugin-transform-object-rest-spread@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-rest-spread/-/plugin-transform-object-rest-spread-7.25.9.tgz#0203725025074164808bcf1a2cfa90c652c99f18" + integrity sha512-fSaXafEE9CVHPweLYw4J0emp1t8zYTXyzN3UuG+lylqkvYd7RMrsOQ8TYx5RF231be0vqtFC6jnx3UmpJmKBYg== dependencies: - "@babel/helper-module-transforms" "^7.20.11" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-simple-access" "^7.20.2" + "@babel/helper-compilation-targets" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/plugin-transform-parameters" "^7.25.9" -"@babel/plugin-transform-modules-systemjs@^7.19.6": - version "7.20.11" - resolved "https://registry.npmjs.org/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.20.11.tgz" - integrity sha512-vVu5g9BPQKSFEmvt2TA4Da5N+QVS66EX21d8uoOihC+OCpUoGvzVsXeqFdtAEfVa5BILAeFt+U7yVmLbQnAJmw== +"@babel/plugin-transform-object-super@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.25.9.tgz#385d5de135162933beb4a3d227a2b7e52bb4cf03" + integrity sha512-Kj/Gh+Rw2RNLbCK1VAWj2U48yxxqL2x0k10nPtSdRa0O2xnHXalD0s+o1A6a0W43gJ00ANo38jxkQreckOzv5A== dependencies: - "@babel/helper-hoist-variables" "^7.18.6" - "@babel/helper-module-transforms" "^7.20.11" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-validator-identifier" "^7.19.1" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-replace-supers" "^7.25.9" -"@babel/plugin-transform-modules-umd@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.18.6.tgz" - integrity sha512-dcegErExVeXcRqNtkRU/z8WlBLnvD4MRnHgNs3MytRO1Mn1sHRyhbcpYbVMGclAqOjdW+9cfkdZno9dFdfKLfQ== +"@babel/plugin-transform-optional-catch-binding@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-optional-catch-binding/-/plugin-transform-optional-catch-binding-7.25.9.tgz#10e70d96d52bb1f10c5caaac59ac545ea2ba7ff3" + integrity sha512-qM/6m6hQZzDcZF3onzIhZeDHDO43bkNNlOX0i8n3lR6zLbu0GN2d8qfM/IERJZYauhAHSLHy39NF0Ctdvcid7g== dependencies: - "@babel/helper-module-transforms" "^7.18.6" - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-named-capturing-groups-regex@^7.19.1": - version "7.20.5" - resolved "https://registry.npmjs.org/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.20.5.tgz" - integrity sha512-mOW4tTzi5iTLnw+78iEq3gr8Aoq4WNRGpmSlrogqaiCBoR1HFhpU4JkpQFOHfeYx3ReVIFWOQJS4aZBRvuZ6mA== +"@babel/plugin-transform-optional-chaining@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-optional-chaining/-/plugin-transform-optional-chaining-7.25.9.tgz#e142eb899d26ef715435f201ab6e139541eee7dd" + integrity sha512-6AvV0FsLULbpnXeBjrY4dmWF8F7gf8QnvTEoO/wX/5xm/xE1Xo8oPuD3MPS+KS9f9XBEAWN7X1aWr4z9HdOr7A== dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.20.5" - "@babel/helper-plugin-utils" "^7.20.2" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-skip-transparent-expression-wrappers" "^7.25.9" -"@babel/plugin-transform-new-target@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.18.6.tgz" - integrity sha512-DjwFA/9Iu3Z+vrAn+8pBUGcjhxKguSMlsFqeCKbhb9BAV756v0krzVK04CRDi/4aqmk8BsHb4a/gFcaA5joXRw== +"@babel/plugin-transform-parameters@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.25.9.tgz#b856842205b3e77e18b7a7a1b94958069c7ba257" + integrity sha512-wzz6MKwpnshBAiRmn4jR8LYz/g8Ksg0o80XmwZDlordjwEk9SxBzTWC7F5ef1jhbrbOW2DJ5J6ayRukrJmnr0g== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-object-super@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.18.6.tgz" - integrity sha512-uvGz6zk+pZoS1aTZrOvrbj6Pp/kK2mp45t2B+bTDre2UgsZZ8EZLSJtUg7m/no0zOJUWgFONpB7Zv9W2tSaFlA== +"@babel/plugin-transform-private-methods@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-private-methods/-/plugin-transform-private-methods-7.25.9.tgz#847f4139263577526455d7d3223cd8bda51e3b57" + integrity sha512-D/JUozNpQLAPUVusvqMxyvjzllRaF8/nSrP1s2YGQT/W4LHK4xxsMcHjhOGTS01mp9Hda8nswb+FblLdJornQw== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" - "@babel/helper-replace-supers" "^7.18.6" + "@babel/helper-create-class-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-parameters@^7.12.1", "@babel/plugin-transform-parameters@^7.20.1", "@babel/plugin-transform-parameters@^7.20.7": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.20.7.tgz" - integrity sha512-WiWBIkeHKVOSYPO0pWkxGPfKeWrCJyD3NJ53+Lrp/QMSZbsVPovrVl2aWZ19D/LTVnaDv5Ap7GJ/B2CTOZdrfA== +"@babel/plugin-transform-private-property-in-object@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-private-property-in-object/-/plugin-transform-private-property-in-object-7.25.9.tgz#9c8b73e64e6cc3cbb2743633885a7dd2c385fe33" + integrity sha512-Evf3kcMqzXA3xfYJmZ9Pg1OvKdtqsDMSWBDzZOPLvHiTt36E75jLDQo5w1gtRU95Q4E5PDttrTf25Fw8d/uWLw== dependencies: - "@babel/helper-plugin-utils" "^7.20.2" + "@babel/helper-annotate-as-pure" "^7.25.9" + "@babel/helper-create-class-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-property-literals@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.18.6.tgz" - integrity sha512-cYcs6qlgafTud3PAzrrRNbQtfpQ8+y/+M5tKmksS9+M1ckbH6kzY8MrexEM9mcA6JDsukE19iIRvAyYl463sMg== +"@babel/plugin-transform-property-literals@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.25.9.tgz#d72d588bd88b0dec8b62e36f6fda91cedfe28e3f" + integrity sha512-IvIUeV5KrS/VPavfSM/Iu+RE6llrHrYIKY1yfCzyO/lMXHQ+p7uGhonmGVisv6tSBSVgWzMBohTcvkC9vQcQFA== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-react-constant-elements@^7.18.12": - version "7.20.2" - resolved "https://registry.npmjs.org/@babel/plugin-transform-react-constant-elements/-/plugin-transform-react-constant-elements-7.20.2.tgz" - integrity sha512-KS/G8YI8uwMGKErLFOHS/ekhqdHhpEloxs43NecQHVgo2QuQSyJhGIY1fL8UGl9wy5ItVwwoUL4YxVqsplGq2g== +"@babel/plugin-transform-react-constant-elements@^7.21.3": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-constant-elements/-/plugin-transform-react-constant-elements-7.25.9.tgz#08a1de35a301929b60fdf2788a54b46cd8ecd0ef" + integrity sha512-Ncw2JFsJVuvfRsa2lSHiC55kETQVLSnsYGQ1JDDwkUeWGTL/8Tom8aLTnlqgoeuopWrbbGndrc9AlLYrIosrow== dependencies: - "@babel/helper-plugin-utils" "^7.20.2" + "@babel/helper-plugin-utils" "^7.25.9" "@babel/plugin-transform-react-display-name@^7.18.6": version "7.18.6" @@ -906,6 +942,13 @@ dependencies: "@babel/helper-plugin-utils" "^7.18.6" +"@babel/plugin-transform-react-display-name@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-display-name/-/plugin-transform-react-display-name-7.25.9.tgz#4b79746b59efa1f38c8695065a92a9f5afb24f7d" + integrity sha512-KJfMlYIUxQB1CJfO3e0+h0ZHWOTLCPP115Awhaz8U0Zpq36Gl/cXlpoyMRnUWlhNUBAzldnCiAZNvCDj7CrKxQ== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/plugin-transform-react-jsx-development@^7.18.6": version "7.18.6" resolved "https://registry.npmjs.org/@babel/plugin-transform-react-jsx-development/-/plugin-transform-react-jsx-development-7.18.6.tgz" @@ -913,6 +956,13 @@ dependencies: "@babel/plugin-transform-react-jsx" "^7.18.6" +"@babel/plugin-transform-react-jsx-development@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-jsx-development/-/plugin-transform-react-jsx-development-7.25.9.tgz#8fd220a77dd139c07e25225a903b8be8c829e0d7" + integrity sha512-9mj6rm7XVYs4mdLIpbZnHOYdpW42uoiBCTVowg7sP1thUOiANgMb4UtpRivR0pp5iL+ocvUv7X4mZgFRpJEzGw== + dependencies: + "@babel/plugin-transform-react-jsx" "^7.25.9" + "@babel/plugin-transform-react-jsx@^7.18.6": version "7.20.13" resolved "https://registry.npmjs.org/@babel/plugin-transform-react-jsx/-/plugin-transform-react-jsx-7.20.13.tgz" @@ -924,6 +974,17 @@ "@babel/plugin-syntax-jsx" "^7.18.6" "@babel/types" "^7.20.7" +"@babel/plugin-transform-react-jsx@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-jsx/-/plugin-transform-react-jsx-7.25.9.tgz#06367940d8325b36edff5e2b9cbe782947ca4166" + integrity sha512-s5XwpQYCqGerXl+Pu6VDL3x0j2d82eiV77UJ8a2mDHAW7j9SWRqQ2y1fNo1Z74CdcYipl5Z41zvjj4Nfzq36rw== + dependencies: + "@babel/helper-annotate-as-pure" "^7.25.9" + "@babel/helper-module-imports" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/plugin-syntax-jsx" "^7.25.9" + "@babel/types" "^7.25.9" + "@babel/plugin-transform-react-pure-annotations@^7.18.6": version "7.18.6" resolved "https://registry.npmjs.org/@babel/plugin-transform-react-pure-annotations/-/plugin-transform-react-pure-annotations-7.18.6.tgz" @@ -932,182 +993,208 @@ "@babel/helper-annotate-as-pure" "^7.18.6" "@babel/helper-plugin-utils" "^7.18.6" -"@babel/plugin-transform-regenerator@^7.18.6": - version "7.20.5" - resolved "https://registry.npmjs.org/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.20.5.tgz" - integrity sha512-kW/oO7HPBtntbsahzQ0qSE3tFvkFwnbozz3NWFhLGqH75vLEg+sCGngLlhVkePlCs3Jv0dBBHDzCHxNiFAQKCQ== +"@babel/plugin-transform-react-pure-annotations@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-pure-annotations/-/plugin-transform-react-pure-annotations-7.25.9.tgz#ea1c11b2f9dbb8e2d97025f43a3b5bc47e18ae62" + integrity sha512-KQ/Takk3T8Qzj5TppkS1be588lkbTp5uj7w6a0LeQaTMSckU/wK0oJ/pih+T690tkgI5jfmg2TqDJvd41Sj1Cg== dependencies: - "@babel/helper-plugin-utils" "^7.20.2" - regenerator-transform "^0.15.1" + "@babel/helper-annotate-as-pure" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-reserved-words@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.18.6.tgz" - integrity sha512-oX/4MyMoypzHjFrT1CdivfKZ+XvIPMFXwwxHp/r0Ddy2Vuomt4HDFGmft1TAY2yiTKiNSsh3kjBAzcM8kSdsjA== +"@babel/plugin-transform-regenerator@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.25.9.tgz#03a8a4670d6cebae95305ac6defac81ece77740b" + integrity sha512-vwDcDNsgMPDGP0nMqzahDWE5/MLcX8sv96+wfX7as7LoF/kr97Bo/7fI00lXY4wUXYfVmwIIyG80fGZ1uvt2qg== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" + "@babel/helper-plugin-utils" "^7.25.9" + regenerator-transform "^0.15.2" -"@babel/plugin-transform-runtime@^7.18.6": - version "7.19.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-runtime/-/plugin-transform-runtime-7.19.6.tgz" - integrity sha512-PRH37lz4JU156lYFW1p8OxE5i7d6Sl/zV58ooyr+q1J1lnQPyg5tIiXlIwNVhJaY4W3TmOtdc8jqdXQcB1v5Yw== +"@babel/plugin-transform-regexp-modifiers@^7.26.0": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-regexp-modifiers/-/plugin-transform-regexp-modifiers-7.26.0.tgz#2f5837a5b5cd3842a919d8147e9903cc7455b850" + integrity sha512-vN6saax7lrA2yA/Pak3sCxuD6F5InBjn9IcrIKQPjpsLvuHYLVroTxjdlVRHjjBWxKOqIwpTXDkOssYT4BFdRw== dependencies: - "@babel/helper-module-imports" "^7.18.6" - "@babel/helper-plugin-utils" "^7.19.0" - babel-plugin-polyfill-corejs2 "^0.3.3" - babel-plugin-polyfill-corejs3 "^0.6.0" - babel-plugin-polyfill-regenerator "^0.4.1" - semver "^6.3.0" + "@babel/helper-create-regexp-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" -"@babel/plugin-transform-shorthand-properties@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.18.6.tgz" - integrity sha512-eCLXXJqv8okzg86ywZJbRn19YJHU4XUa55oz2wbHhaQVn/MM+XhukiT7SYqp/7o00dg52Rj51Ny+Ecw4oyoygw== - dependencies: - "@babel/helper-plugin-utils" "^7.18.6" - -"@babel/plugin-transform-spread@^7.19.0": - version "7.20.7" - resolved "https://registry.npmjs.org/@babel/plugin-transform-spread/-/plugin-transform-spread-7.20.7.tgz" - integrity sha512-ewBbHQ+1U/VnH1fxltbJqDeWBU1oNLG8Dj11uIv3xVf7nrQu0bPGe5Rf716r7K5Qz+SqtAOVswoVunoiBtGhxw== - dependencies: - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-skip-transparent-expression-wrappers" "^7.20.0" - -"@babel/plugin-transform-sticky-regex@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.18.6.tgz" - integrity sha512-kfiDrDQ+PBsQDO85yj1icueWMfGfJFKN1KCkndygtu/C9+XUfydLC8Iv5UYJqRwy4zk8EcplRxEOeLyjq1gm6Q== +"@babel/plugin-transform-reserved-words@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.25.9.tgz#0398aed2f1f10ba3f78a93db219b27ef417fb9ce" + integrity sha512-7DL7DKYjn5Su++4RXu8puKZm2XBPHyjWLUidaPEkCUBbE7IPcsrkRHggAOOKydH1dASWdcUBxrkOGNxUv5P3Jg== dependencies: - "@babel/helper-plugin-utils" "^7.18.6" - -"@babel/plugin-transform-template-literals@^7.18.9": - version "7.18.9" - resolved "https://registry.npmjs.org/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.18.9.tgz" - integrity sha512-S8cOWfT82gTezpYOiVaGHrCbhlHgKhQt8XH5ES46P2XWmX92yisoZywf5km75wv5sYcXDUCLMmMxOLCtthDgMA== - dependencies: - "@babel/helper-plugin-utils" "^7.18.9" - -"@babel/plugin-transform-typeof-symbol@^7.18.9": - version "7.18.9" - resolved "https://registry.npmjs.org/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.18.9.tgz" - integrity sha512-SRfwTtF11G2aemAZWivL7PD+C9z52v9EvMqH9BuYbabyPuKUvSWks3oCg6041pT925L4zVFqaVBeECwsmlguEw== - dependencies: - "@babel/helper-plugin-utils" "^7.18.9" - -"@babel/plugin-transform-typescript@^7.18.6": - version "7.20.13" - resolved "https://registry.npmjs.org/@babel/plugin-transform-typescript/-/plugin-transform-typescript-7.20.13.tgz" - integrity sha512-O7I/THxarGcDZxkgWKMUrk7NK1/WbHAg3Xx86gqS6x9MTrNL6AwIluuZ96ms4xeDe6AVx6rjHbWHP7x26EPQBA== - dependencies: - "@babel/helper-create-class-features-plugin" "^7.20.12" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/plugin-syntax-typescript" "^7.20.0" - -"@babel/plugin-transform-unicode-escapes@^7.18.10": - version "7.18.10" - resolved "https://registry.npmjs.org/@babel/plugin-transform-unicode-escapes/-/plugin-transform-unicode-escapes-7.18.10.tgz" - integrity sha512-kKAdAI+YzPgGY/ftStBFXTI1LZFju38rYThnfMykS+IXy8BVx+res7s2fxf1l8I35DV2T97ezo6+SGrXz6B3iQ== - dependencies: - "@babel/helper-plugin-utils" "^7.18.9" - -"@babel/plugin-transform-unicode-regex@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.18.6.tgz" - integrity sha512-gE7A6Lt7YLnNOL3Pb9BNeZvi+d8l7tcRrG4+pwJjK9hD2xX4mEvjlQW60G9EEmfXVYRPv9VRQcyegIVHCql/AA== - dependencies: - "@babel/helper-create-regexp-features-plugin" "^7.18.6" - "@babel/helper-plugin-utils" "^7.18.6" - -"@babel/preset-env@^7.18.6", "@babel/preset-env@^7.19.4": - version "7.20.2" - resolved "https://registry.npmjs.org/@babel/preset-env/-/preset-env-7.20.2.tgz" - integrity sha512-1G0efQEWR1EHkKvKHqbG+IN/QdgwfByUpM5V5QroDzGV2t3S/WXNQd693cHiHTlCFMpr9B6FkPFXDA2lQcKoDg== - dependencies: - "@babel/compat-data" "^7.20.1" - "@babel/helper-compilation-targets" "^7.20.0" - "@babel/helper-plugin-utils" "^7.20.2" - "@babel/helper-validator-option" "^7.18.6" - "@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression" "^7.18.6" - "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining" "^7.18.9" - "@babel/plugin-proposal-async-generator-functions" "^7.20.1" - "@babel/plugin-proposal-class-properties" "^7.18.6" - "@babel/plugin-proposal-class-static-block" "^7.18.6" - "@babel/plugin-proposal-dynamic-import" "^7.18.6" - "@babel/plugin-proposal-export-namespace-from" "^7.18.9" - "@babel/plugin-proposal-json-strings" "^7.18.6" - "@babel/plugin-proposal-logical-assignment-operators" "^7.18.9" - "@babel/plugin-proposal-nullish-coalescing-operator" "^7.18.6" - "@babel/plugin-proposal-numeric-separator" "^7.18.6" - "@babel/plugin-proposal-object-rest-spread" "^7.20.2" - "@babel/plugin-proposal-optional-catch-binding" "^7.18.6" - "@babel/plugin-proposal-optional-chaining" "^7.18.9" - "@babel/plugin-proposal-private-methods" "^7.18.6" - "@babel/plugin-proposal-private-property-in-object" "^7.18.6" - "@babel/plugin-proposal-unicode-property-regex" "^7.18.6" - "@babel/plugin-syntax-async-generators" "^7.8.4" - "@babel/plugin-syntax-class-properties" "^7.12.13" - "@babel/plugin-syntax-class-static-block" "^7.14.5" - "@babel/plugin-syntax-dynamic-import" "^7.8.3" - "@babel/plugin-syntax-export-namespace-from" "^7.8.3" - "@babel/plugin-syntax-import-assertions" "^7.20.0" - "@babel/plugin-syntax-json-strings" "^7.8.3" - "@babel/plugin-syntax-logical-assignment-operators" "^7.10.4" - "@babel/plugin-syntax-nullish-coalescing-operator" "^7.8.3" - "@babel/plugin-syntax-numeric-separator" "^7.10.4" - "@babel/plugin-syntax-object-rest-spread" "^7.8.3" - "@babel/plugin-syntax-optional-catch-binding" "^7.8.3" - "@babel/plugin-syntax-optional-chaining" "^7.8.3" - "@babel/plugin-syntax-private-property-in-object" "^7.14.5" - "@babel/plugin-syntax-top-level-await" "^7.14.5" - "@babel/plugin-transform-arrow-functions" "^7.18.6" - "@babel/plugin-transform-async-to-generator" "^7.18.6" - "@babel/plugin-transform-block-scoped-functions" "^7.18.6" - "@babel/plugin-transform-block-scoping" "^7.20.2" - "@babel/plugin-transform-classes" "^7.20.2" - "@babel/plugin-transform-computed-properties" "^7.18.9" - "@babel/plugin-transform-destructuring" "^7.20.2" - "@babel/plugin-transform-dotall-regex" "^7.18.6" - "@babel/plugin-transform-duplicate-keys" "^7.18.9" - "@babel/plugin-transform-exponentiation-operator" "^7.18.6" - "@babel/plugin-transform-for-of" "^7.18.8" - "@babel/plugin-transform-function-name" "^7.18.9" - "@babel/plugin-transform-literals" "^7.18.9" - "@babel/plugin-transform-member-expression-literals" "^7.18.6" - "@babel/plugin-transform-modules-amd" "^7.19.6" - "@babel/plugin-transform-modules-commonjs" "^7.19.6" - "@babel/plugin-transform-modules-systemjs" "^7.19.6" - "@babel/plugin-transform-modules-umd" "^7.18.6" - "@babel/plugin-transform-named-capturing-groups-regex" "^7.19.1" - "@babel/plugin-transform-new-target" "^7.18.6" - "@babel/plugin-transform-object-super" "^7.18.6" - "@babel/plugin-transform-parameters" "^7.20.1" - "@babel/plugin-transform-property-literals" "^7.18.6" - "@babel/plugin-transform-regenerator" "^7.18.6" - "@babel/plugin-transform-reserved-words" "^7.18.6" - "@babel/plugin-transform-shorthand-properties" "^7.18.6" - "@babel/plugin-transform-spread" "^7.19.0" - "@babel/plugin-transform-sticky-regex" "^7.18.6" - "@babel/plugin-transform-template-literals" "^7.18.9" - "@babel/plugin-transform-typeof-symbol" "^7.18.9" - "@babel/plugin-transform-unicode-escapes" "^7.18.10" - "@babel/plugin-transform-unicode-regex" "^7.18.6" - "@babel/preset-modules" "^0.1.5" - "@babel/types" "^7.20.2" - babel-plugin-polyfill-corejs2 "^0.3.3" - babel-plugin-polyfill-corejs3 "^0.6.0" - babel-plugin-polyfill-regenerator "^0.4.1" - core-js-compat "^3.25.1" - semver "^6.3.0" - -"@babel/preset-modules@^0.1.5": - version "0.1.5" - resolved "https://registry.npmjs.org/@babel/preset-modules/-/preset-modules-0.1.5.tgz" - integrity sha512-A57th6YRG7oR3cq/yt/Y84MvGgE0eJG2F1JLhKuyG+jFxEgrd/HAMJatiFtmOiZurz+0DkrvbheCLaV5f2JfjA== + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/plugin-transform-runtime@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-runtime/-/plugin-transform-runtime-7.25.9.tgz#62723ea3f5b31ffbe676da9d6dae17138ae580ea" + integrity sha512-nZp7GlEl+yULJrClz0SwHPqir3lc0zsPrDHQUcxGspSL7AKrexNSEfTbfqnDNJUO13bgKyfuOLMF8Xqtu8j3YQ== + dependencies: + "@babel/helper-module-imports" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + babel-plugin-polyfill-corejs2 "^0.4.10" + babel-plugin-polyfill-corejs3 "^0.10.6" + babel-plugin-polyfill-regenerator "^0.6.1" + semver "^6.3.1" + +"@babel/plugin-transform-shorthand-properties@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.25.9.tgz#bb785e6091f99f826a95f9894fc16fde61c163f2" + integrity sha512-MUv6t0FhO5qHnS/W8XCbHmiRWOphNufpE1IVxhK5kuN3Td9FT1x4rx4K42s3RYdMXCXpfWkGSbCSd0Z64xA7Ng== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/plugin-transform-spread@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-spread/-/plugin-transform-spread-7.25.9.tgz#24a35153931b4ba3d13cec4a7748c21ab5514ef9" + integrity sha512-oNknIB0TbURU5pqJFVbOOFspVlrpVwo2H1+HUIsVDvp5VauGGDP1ZEvO8Nn5xyMEs3dakajOxlmkNW7kNgSm6A== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-skip-transparent-expression-wrappers" "^7.25.9" + +"@babel/plugin-transform-sticky-regex@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.25.9.tgz#c7f02b944e986a417817b20ba2c504dfc1453d32" + integrity sha512-WqBUSgeVwucYDP9U/xNRQam7xV8W5Zf+6Eo7T2SRVUFlhRiMNFdFz58u0KZmCVVqs2i7SHgpRnAhzRNmKfi2uA== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/plugin-transform-template-literals@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.25.9.tgz#6dbd4a24e8fad024df76d1fac6a03cf413f60fe1" + integrity sha512-o97AE4syN71M/lxrCtQByzphAdlYluKPDBzDVzMmfCobUjjhAryZV0AIpRPrxN0eAkxXO6ZLEScmt+PNhj2OTw== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/plugin-transform-typeof-symbol@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.25.9.tgz#224ba48a92869ddbf81f9b4a5f1204bbf5a2bc4b" + integrity sha512-v61XqUMiueJROUv66BVIOi0Fv/CUuZuZMl5NkRoCVxLAnMexZ0A3kMe7vvZ0nulxMuMp0Mk6S5hNh48yki08ZA== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/plugin-transform-typescript@^7.25.9": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-typescript/-/plugin-transform-typescript-7.26.3.tgz#3d6add9c78735623317387ee26d5ada540eee3fd" + integrity sha512-6+5hpdr6mETwSKjmJUdYw0EIkATiQhnELWlE3kJFBwSg/BGIVwVaVbX+gOXBCdc7Ln1RXZxyWGecIXhUfnl7oA== + dependencies: + "@babel/helper-annotate-as-pure" "^7.25.9" + "@babel/helper-create-class-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-skip-transparent-expression-wrappers" "^7.25.9" + "@babel/plugin-syntax-typescript" "^7.25.9" + +"@babel/plugin-transform-unicode-escapes@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-escapes/-/plugin-transform-unicode-escapes-7.25.9.tgz#a75ef3947ce15363fccaa38e2dd9bc70b2788b82" + integrity sha512-s5EDrE6bW97LtxOcGj1Khcx5AaXwiMmi4toFWRDP9/y0Woo6pXC+iyPu/KuhKtfSrNFd7jJB+/fkOtZy6aIC6Q== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/plugin-transform-unicode-property-regex@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-property-regex/-/plugin-transform-unicode-property-regex-7.25.9.tgz#a901e96f2c1d071b0d1bb5dc0d3c880ce8f53dd3" + integrity sha512-Jt2d8Ga+QwRluxRQ307Vlxa6dMrYEMZCgGxoPR8V52rxPyldHu3hdlHspxaqYmE7oID5+kB+UKUB/eWS+DkkWg== + dependencies: + "@babel/helper-create-regexp-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/plugin-transform-unicode-regex@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.25.9.tgz#5eae747fe39eacf13a8bd006a4fb0b5d1fa5e9b1" + integrity sha512-yoxstj7Rg9dlNn9UQxzk4fcNivwv4nUYz7fYXBaKxvw/lnmPuOm/ikoELygbYq68Bls3D/D+NBPHiLwZdZZ4HA== + dependencies: + "@babel/helper-create-regexp-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/plugin-transform-unicode-sets-regex@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-sets-regex/-/plugin-transform-unicode-sets-regex-7.25.9.tgz#65114c17b4ffc20fa5b163c63c70c0d25621fabe" + integrity sha512-8BYqO3GeVNHtx69fdPshN3fnzUNLrWdHhk/icSwigksJGczKSizZ+Z6SBCxTs723Fr5VSNorTIK7a+R2tISvwQ== + dependencies: + "@babel/helper-create-regexp-features-plugin" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + +"@babel/preset-env@^7.20.2", "@babel/preset-env@^7.25.9": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/preset-env/-/preset-env-7.26.0.tgz#30e5c6bc1bcc54865bff0c5a30f6d4ccdc7fa8b1" + integrity sha512-H84Fxq0CQJNdPFT2DrfnylZ3cf5K43rGfWK4LJGPpjKHiZlk0/RzwEus3PDDZZg+/Er7lCA03MVacueUuXdzfw== + dependencies: + "@babel/compat-data" "^7.26.0" + "@babel/helper-compilation-targets" "^7.25.9" + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-validator-option" "^7.25.9" + "@babel/plugin-bugfix-firefox-class-in-computed-class-key" "^7.25.9" + "@babel/plugin-bugfix-safari-class-field-initializer-scope" "^7.25.9" + "@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression" "^7.25.9" + "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining" "^7.25.9" + "@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly" "^7.25.9" + "@babel/plugin-proposal-private-property-in-object" "7.21.0-placeholder-for-preset-env.2" + "@babel/plugin-syntax-import-assertions" "^7.26.0" + "@babel/plugin-syntax-import-attributes" "^7.26.0" + "@babel/plugin-syntax-unicode-sets-regex" "^7.18.6" + "@babel/plugin-transform-arrow-functions" "^7.25.9" + "@babel/plugin-transform-async-generator-functions" "^7.25.9" + "@babel/plugin-transform-async-to-generator" "^7.25.9" + "@babel/plugin-transform-block-scoped-functions" "^7.25.9" + "@babel/plugin-transform-block-scoping" "^7.25.9" + "@babel/plugin-transform-class-properties" "^7.25.9" + "@babel/plugin-transform-class-static-block" "^7.26.0" + "@babel/plugin-transform-classes" "^7.25.9" + "@babel/plugin-transform-computed-properties" "^7.25.9" + "@babel/plugin-transform-destructuring" "^7.25.9" + "@babel/plugin-transform-dotall-regex" "^7.25.9" + "@babel/plugin-transform-duplicate-keys" "^7.25.9" + "@babel/plugin-transform-duplicate-named-capturing-groups-regex" "^7.25.9" + "@babel/plugin-transform-dynamic-import" "^7.25.9" + "@babel/plugin-transform-exponentiation-operator" "^7.25.9" + "@babel/plugin-transform-export-namespace-from" "^7.25.9" + "@babel/plugin-transform-for-of" "^7.25.9" + "@babel/plugin-transform-function-name" "^7.25.9" + "@babel/plugin-transform-json-strings" "^7.25.9" + "@babel/plugin-transform-literals" "^7.25.9" + "@babel/plugin-transform-logical-assignment-operators" "^7.25.9" + "@babel/plugin-transform-member-expression-literals" "^7.25.9" + "@babel/plugin-transform-modules-amd" "^7.25.9" + "@babel/plugin-transform-modules-commonjs" "^7.25.9" + "@babel/plugin-transform-modules-systemjs" "^7.25.9" + "@babel/plugin-transform-modules-umd" "^7.25.9" + "@babel/plugin-transform-named-capturing-groups-regex" "^7.25.9" + "@babel/plugin-transform-new-target" "^7.25.9" + "@babel/plugin-transform-nullish-coalescing-operator" "^7.25.9" + "@babel/plugin-transform-numeric-separator" "^7.25.9" + "@babel/plugin-transform-object-rest-spread" "^7.25.9" + "@babel/plugin-transform-object-super" "^7.25.9" + "@babel/plugin-transform-optional-catch-binding" "^7.25.9" + "@babel/plugin-transform-optional-chaining" "^7.25.9" + "@babel/plugin-transform-parameters" "^7.25.9" + "@babel/plugin-transform-private-methods" "^7.25.9" + "@babel/plugin-transform-private-property-in-object" "^7.25.9" + "@babel/plugin-transform-property-literals" "^7.25.9" + "@babel/plugin-transform-regenerator" "^7.25.9" + "@babel/plugin-transform-regexp-modifiers" "^7.26.0" + "@babel/plugin-transform-reserved-words" "^7.25.9" + "@babel/plugin-transform-shorthand-properties" "^7.25.9" + "@babel/plugin-transform-spread" "^7.25.9" + "@babel/plugin-transform-sticky-regex" "^7.25.9" + "@babel/plugin-transform-template-literals" "^7.25.9" + "@babel/plugin-transform-typeof-symbol" "^7.25.9" + "@babel/plugin-transform-unicode-escapes" "^7.25.9" + "@babel/plugin-transform-unicode-property-regex" "^7.25.9" + "@babel/plugin-transform-unicode-regex" "^7.25.9" + "@babel/plugin-transform-unicode-sets-regex" "^7.25.9" + "@babel/preset-modules" "0.1.6-no-external-plugins" + babel-plugin-polyfill-corejs2 "^0.4.10" + babel-plugin-polyfill-corejs3 "^0.10.6" + babel-plugin-polyfill-regenerator "^0.6.1" + core-js-compat "^3.38.1" + semver "^6.3.1" + +"@babel/preset-modules@0.1.6-no-external-plugins": + version "0.1.6-no-external-plugins" + resolved "https://registry.yarnpkg.com/@babel/preset-modules/-/preset-modules-0.1.6-no-external-plugins.tgz#ccb88a2c49c817236861fee7826080573b8a923a" + integrity sha512-HrcgcIESLm9aIR842yhJ5RWan/gebQUJ6E/E5+rf0y9o6oj7w0Br+sWuL6kEQ/o/AdfvR1Je9jG18/gnpwjEyA== dependencies: "@babel/helper-plugin-utils" "^7.0.0" - "@babel/plugin-proposal-unicode-property-regex" "^7.4.4" - "@babel/plugin-transform-dotall-regex" "^7.4.4" "@babel/types" "^7.4.4" esutils "^2.0.2" @@ -1123,56 +1210,74 @@ "@babel/plugin-transform-react-jsx-development" "^7.18.6" "@babel/plugin-transform-react-pure-annotations" "^7.18.6" -"@babel/preset-typescript@^7.18.6": - version "7.18.6" - resolved "https://registry.npmjs.org/@babel/preset-typescript/-/preset-typescript-7.18.6.tgz" - integrity sha512-s9ik86kXBAnD760aybBucdpnLsAt0jK1xqJn2juOn9lkOvSHV60os5hxoVJsPzMQxvnUJFAlkont2DvvaYEBtQ== - dependencies: - "@babel/helper-plugin-utils" "^7.18.6" - "@babel/helper-validator-option" "^7.18.6" - "@babel/plugin-transform-typescript" "^7.18.6" - -"@babel/runtime-corejs3@^7.18.6": - version "7.20.13" - resolved "https://registry.npmjs.org/@babel/runtime-corejs3/-/runtime-corejs3-7.20.13.tgz" - integrity sha512-p39/6rmY9uvlzRiLZBIB3G9/EBr66LBMcYm7fIDeSBNdRjF2AGD3rFZucUyAgGHC2N+7DdLvVi33uTjSE44FIw== - dependencies: - core-js-pure "^3.25.1" - regenerator-runtime "^0.13.11" - -"@babel/runtime@^7.1.2", "@babel/runtime@^7.10.2", "@babel/runtime@^7.10.3", "@babel/runtime@^7.12.13", "@babel/runtime@^7.12.5", "@babel/runtime@^7.18.6", "@babel/runtime@^7.8.4": +"@babel/preset-react@^7.25.9": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/preset-react/-/preset-react-7.26.3.tgz#7c5e028d623b4683c1f83a0bd4713b9100560caa" + integrity sha512-Nl03d6T9ky516DGK2YMxrTqvnpUW63TnJMOMonj+Zae0JiPC5BC9xPMSL6L8fiSpA5vP88qfygavVQvnLp+6Cw== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-validator-option" "^7.25.9" + "@babel/plugin-transform-react-display-name" "^7.25.9" + "@babel/plugin-transform-react-jsx" "^7.25.9" + "@babel/plugin-transform-react-jsx-development" "^7.25.9" + "@babel/plugin-transform-react-pure-annotations" "^7.25.9" + +"@babel/preset-typescript@^7.21.0", "@babel/preset-typescript@^7.25.9": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/preset-typescript/-/preset-typescript-7.26.0.tgz#4a570f1b8d104a242d923957ffa1eaff142a106d" + integrity sha512-NMk1IGZ5I/oHhoXEElcm+xUnL/szL6xflkFZmoEU9xj1qSJXpiS7rsspYo92B4DRCDvZn2erT5LdsCeXAKNCkg== + dependencies: + "@babel/helper-plugin-utils" "^7.25.9" + "@babel/helper-validator-option" "^7.25.9" + "@babel/plugin-syntax-jsx" "^7.25.9" + "@babel/plugin-transform-modules-commonjs" "^7.25.9" + "@babel/plugin-transform-typescript" "^7.25.9" + +"@babel/runtime-corejs3@^7.25.9": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/runtime-corejs3/-/runtime-corejs3-7.26.0.tgz#5af6bed16073eb4a0191233d61e158a5c768c430" + integrity sha512-YXHu5lN8kJCb1LOb9PgV6pvak43X2h4HvRApcN5SdWeaItQOzfn1hgP6jasD6KWQyJDBxrVmA9o9OivlnNJK/w== + dependencies: + core-js-pure "^3.30.2" + regenerator-runtime "^0.14.0" + +"@babel/runtime@^7.1.2", "@babel/runtime@^7.10.3", "@babel/runtime@^7.12.13", "@babel/runtime@^7.12.5", "@babel/runtime@^7.8.4": version "7.20.13" resolved "https://registry.npmjs.org/@babel/runtime/-/runtime-7.20.13.tgz" integrity sha512-gt3PKXs0DBoL9xCvOIIZ2NEqAGZqHjAnmVbfQtB620V0uReIQutpel14KcneZuer7UioY8ALKZ7iocavvzTNFA== dependencies: regenerator-runtime "^0.13.11" -"@babel/template@^7.12.7", "@babel/template@^7.18.10", "@babel/template@^7.20.7", "@babel/template@^7.22.15": - version "7.22.15" - resolved "https://registry.npmjs.org/@babel/template/-/template-7.22.15.tgz" - integrity sha512-QPErUVm4uyJa60rkI73qneDacvdvzxshT3kksGqlGWYdOTIUOwJ7RDUL8sGqslY1uXWSL6xMFKEXDS3ox2uF0w== - dependencies: - "@babel/code-frame" "^7.22.13" - "@babel/parser" "^7.22.15" - "@babel/types" "^7.22.15" - -"@babel/traverse@^7.12.9", "@babel/traverse@^7.18.8", "@babel/traverse@^7.20.10", "@babel/traverse@^7.20.12", "@babel/traverse@^7.20.13", "@babel/traverse@^7.20.5", "@babel/traverse@^7.20.7": - version "7.23.2" - resolved "https://registry.npmjs.org/@babel/traverse/-/traverse-7.23.2.tgz" - integrity sha512-azpe59SQ48qG6nu2CzcMLbxUudtN+dOM9kDbUqGq3HXUJRlo7i8fvPoxQUzYgLZ4cMVmuZgm8vvBpNeRhd6XSw== - dependencies: - "@babel/code-frame" "^7.22.13" - "@babel/generator" "^7.23.0" - "@babel/helper-environment-visitor" "^7.22.20" - "@babel/helper-function-name" "^7.23.0" - "@babel/helper-hoist-variables" "^7.22.5" - "@babel/helper-split-export-declaration" "^7.22.6" - "@babel/parser" "^7.23.0" - "@babel/types" "^7.23.0" - debug "^4.1.0" +"@babel/runtime@^7.25.9": + version "7.26.0" + resolved "https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.26.0.tgz#8600c2f595f277c60815256418b85356a65173c1" + integrity sha512-FDSOghenHTiToteC/QRlv2q3DhPZ/oOXTBoirfWNx1Cx3TMVcGWQtMMmQcSvb/JjpNeGzx8Pq/b4fKEJuWm1sw== + dependencies: + regenerator-runtime "^0.14.0" + +"@babel/template@^7.25.9": + version "7.25.9" + resolved "https://registry.yarnpkg.com/@babel/template/-/template-7.25.9.tgz#ecb62d81a8a6f5dc5fe8abfc3901fc52ddf15016" + integrity sha512-9DGttpmPvIxBb/2uwpVo3dqJ+O6RooAFOS+lB+xDqoE2PVCE8nfoHMdZLpfCQRLwvohzXISPZcgxt80xLfsuwg== + dependencies: + "@babel/code-frame" "^7.25.9" + "@babel/parser" "^7.25.9" + "@babel/types" "^7.25.9" + +"@babel/traverse@^7.25.9": + version "7.26.4" + resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.26.4.tgz#ac3a2a84b908dde6d463c3bfa2c5fdc1653574bd" + integrity sha512-fH+b7Y4p3yqvApJALCPJcwb0/XaOSgtK4pzV6WVjPR5GLFQBRI7pfoX2V2iM48NXvX07NUxxm1Vw98YjqTcU5w== + dependencies: + "@babel/code-frame" "^7.26.2" + "@babel/generator" "^7.26.3" + "@babel/parser" "^7.26.3" + "@babel/template" "^7.25.9" + "@babel/types" "^7.26.3" + debug "^4.3.1" globals "^11.1.0" -"@babel/types@^7.12.7", "@babel/types@^7.18.6", "@babel/types@^7.18.9", "@babel/types@^7.20.0", "@babel/types@^7.20.2", "@babel/types@^7.20.5", "@babel/types@^7.20.7", "@babel/types@^7.22.15", "@babel/types@^7.22.5", "@babel/types@^7.23.0", "@babel/types@^7.4.4": +"@babel/types@^7.18.6", "@babel/types@^7.20.7", "@babel/types@^7.4.4": version "7.23.0" resolved "https://registry.npmjs.org/@babel/types/-/types-7.23.0.tgz" integrity sha512-0oIyUfKoI3mSqMvsxBdclDwxXKXAUA8v/apZbc+iSyARYou1o8ZGDxbUYyLFoW2arqS2jDGqJuZvv1d/io1axg== @@ -1181,451 +1286,819 @@ "@babel/helper-validator-identifier" "^7.22.20" to-fast-properties "^2.0.0" +"@babel/types@^7.21.3", "@babel/types@^7.25.9", "@babel/types@^7.26.0", "@babel/types@^7.26.3": + version "7.26.3" + resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.26.3.tgz#37e79830f04c2b5687acc77db97fbc75fb81f3c0" + integrity sha512-vN5p+1kl59GVKMvTHt55NzzmYVxprfJD+ql7U9NFIfKCBkYE55LYtS+WtPlaYOyzydrKI8Nezd+aZextrd+FMA== + dependencies: + "@babel/helper-string-parser" "^7.25.9" + "@babel/helper-validator-identifier" "^7.25.9" + "@colors/colors@1.5.0": version "1.5.0" resolved "https://registry.npmjs.org/@colors/colors/-/colors-1.5.0.tgz" integrity sha512-ooWCrlZP11i8GImSjTHYHLkvFDP48nS4+204nGb1RiX/WXYHmJA2III9/e2DWVabCESdW7hBAEzHRqUn9OUVvQ== -"@docsearch/css@3.3.2": - version "3.3.2" - resolved "https://registry.npmjs.org/@docsearch/css/-/css-3.3.2.tgz" - integrity sha512-dctFYiwbvDZkksMlsmc7pj6W6By/EjnVXJq5TEPd05MwQe+dcdHJgaIn1c8wfsucxHpIsdrUcgSkACHCq6aIhw== +"@csstools/cascade-layer-name-parser@^2.0.4": + version "2.0.4" + resolved "https://registry.yarnpkg.com/@csstools/cascade-layer-name-parser/-/cascade-layer-name-parser-2.0.4.tgz#64d128529397aa1e1c986f685713363b262b81b1" + integrity sha512-7DFHlPuIxviKYZrOiwVU/PiHLm3lLUR23OMuEEtfEOQTOp9hzQ2JjdY6X5H18RVuUPJqSCI+qNnD5iOLMVE0bA== -"@docsearch/react@^3.1.1": - version "3.3.2" - resolved "https://registry.npmjs.org/@docsearch/react/-/react-3.3.2.tgz" - integrity sha512-ugILab2TYKSh6IEHf6Z9xZbOovsYbsdfo60PBj+Bw+oMJ1MHJ7pBt1TTcmPki1hSgg8mysgKy2hDiVdPm7XWSQ== +"@csstools/color-helpers@^5.0.1": + version "5.0.1" + resolved "https://registry.yarnpkg.com/@csstools/color-helpers/-/color-helpers-5.0.1.tgz#829f1c76f5800b79c51c709e2f36821b728e0e10" + integrity sha512-MKtmkA0BX87PKaO1NFRTFH+UnkgnmySQOvNxJubsadusqPEC2aJ9MOQiMceZJJ6oitUl/i0L6u0M1IrmAOmgBA== + +"@csstools/css-calc@^2.1.0": + version "2.1.0" + resolved "https://registry.yarnpkg.com/@csstools/css-calc/-/css-calc-2.1.0.tgz#3f28b8f8f736b8f78abbc75eebd55c756207e773" + integrity sha512-X69PmFOrjTZfN5ijxtI8hZ9kRADFSLrmmQ6hgDJ272Il049WGKpDY64KhrFm/7rbWve0z81QepawzjkKlqkNGw== + +"@csstools/css-color-parser@^3.0.6": + version "3.0.6" + resolved "https://registry.yarnpkg.com/@csstools/css-color-parser/-/css-color-parser-3.0.6.tgz#e646838f6aab4618aeea7ba0c4921a254e180276" + integrity sha512-S/IjXqTHdpI4EtzGoNCHfqraXF37x12ZZHA1Lk7zoT5pm2lMjFuqhX/89L7dqX4CcMacKK+6ZCs5TmEGb/+wKw== dependencies: - "@algolia/autocomplete-core" "1.7.4" - "@algolia/autocomplete-preset-algolia" "1.7.4" - "@docsearch/css" "3.3.2" - algoliasearch "^4.0.0" + "@csstools/color-helpers" "^5.0.1" + "@csstools/css-calc" "^2.1.0" -"@docusaurus/core@2.4.1", "@docusaurus/core@^2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/core/-/core-2.4.1.tgz" - integrity sha512-SNsY7PshK3Ri7vtsLXVeAJGS50nJN3RgF836zkyUfAD01Fq+sAk5EwWgLw+nnm5KVNGDu7PRR2kRGDsWvqpo0g== +"@csstools/css-parser-algorithms@^3.0.4": + version "3.0.4" + resolved "https://registry.yarnpkg.com/@csstools/css-parser-algorithms/-/css-parser-algorithms-3.0.4.tgz#74426e93bd1c4dcab3e441f5cc7ba4fb35d94356" + integrity sha512-Up7rBoV77rv29d3uKHUIVubz1BTcgyUK72IvCQAbfbMv584xHcGKCKbWh7i8hPrRJ7qU4Y8IO3IY9m+iTB7P3A== + +"@csstools/css-tokenizer@^3.0.3": + version "3.0.3" + resolved "https://registry.yarnpkg.com/@csstools/css-tokenizer/-/css-tokenizer-3.0.3.tgz#a5502c8539265fecbd873c1e395a890339f119c2" + integrity sha512-UJnjoFsmxfKUdNYdWgOB0mWUypuLvAfQPH1+pyvRJs6euowbFkFC6P13w1l8mJyi3vxYMxc9kld5jZEGRQs6bw== + +"@csstools/media-query-list-parser@^4.0.2": + version "4.0.2" + resolved "https://registry.yarnpkg.com/@csstools/media-query-list-parser/-/media-query-list-parser-4.0.2.tgz#e80e17eba1693fceafb8d6f2cfc68c0e7a9ab78a" + integrity sha512-EUos465uvVvMJehckATTlNqGj4UJWkTmdWuDMjqvSUkjGpmOyFZBVwb4knxCm/k2GMTXY+c/5RkdndzFYWeX5A== + +"@csstools/postcss-cascade-layers@^5.0.1": + version "5.0.1" + resolved "https://registry.yarnpkg.com/@csstools/postcss-cascade-layers/-/postcss-cascade-layers-5.0.1.tgz#9640313e64b5e39133de7e38a5aa7f40dc259597" + integrity sha512-XOfhI7GShVcKiKwmPAnWSqd2tBR0uxt+runAxttbSp/LY2U16yAVPmAf7e9q4JJ0d+xMNmpwNDLBXnmRCl3HMQ== + dependencies: + "@csstools/selector-specificity" "^5.0.0" + postcss-selector-parser "^7.0.0" + +"@csstools/postcss-color-function@^4.0.6": + version "4.0.6" + resolved "https://registry.yarnpkg.com/@csstools/postcss-color-function/-/postcss-color-function-4.0.6.tgz#dabd1e516ccd4c7bd5803e37075a503b5f7f0ac4" + integrity sha512-EcvXfC60cTIumzpsxWuvVjb7rsJEHPvqn3jeMEBUaE3JSc4FRuP7mEQ+1eicxWmIrs3FtzMH9gR3sgA5TH+ebQ== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-color-mix-function@^3.0.6": + version "3.0.6" + resolved "https://registry.yarnpkg.com/@csstools/postcss-color-mix-function/-/postcss-color-mix-function-3.0.6.tgz#d971832ec30b3b60363bceddfeb4b90c7cc0f4b8" + integrity sha512-jVKdJn4+JkASYGhyPO+Wa5WXSx1+oUgaXb3JsjJn/BlrtFh5zjocCY7pwWi0nuP24V1fY7glQsxEYcYNy0dMFg== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-content-alt-text@^2.0.4": + version "2.0.4" + resolved "https://registry.yarnpkg.com/@csstools/postcss-content-alt-text/-/postcss-content-alt-text-2.0.4.tgz#76f4687fb15ed45bc1139bb71e5775779762897a" + integrity sha512-YItlZUOuZJCBlRaCf8Aucc1lgN41qYGALMly0qQllrxYJhiyzlI6RxOTMUvtWk+KhS8GphMDsDhKQ7KTPfEMSw== + dependencies: + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-exponential-functions@^2.0.5": + version "2.0.5" + resolved "https://registry.yarnpkg.com/@csstools/postcss-exponential-functions/-/postcss-exponential-functions-2.0.5.tgz#0c39f75df3357ee1e444b0aa0ede4e12aafea0e9" + integrity sha512-mi8R6dVfA2nDoKM3wcEi64I8vOYEgQVtVKCfmLHXupeLpACfGAided5ddMt5f+CnEodNu4DifuVwb0I6fQDGGQ== + dependencies: + "@csstools/css-calc" "^2.1.0" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + +"@csstools/postcss-font-format-keywords@^4.0.0": + version "4.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-font-format-keywords/-/postcss-font-format-keywords-4.0.0.tgz#6730836eb0153ff4f3840416cc2322f129c086e6" + integrity sha512-usBzw9aCRDvchpok6C+4TXC57btc4bJtmKQWOHQxOVKen1ZfVqBUuCZ/wuqdX5GHsD0NRSr9XTP+5ID1ZZQBXw== + dependencies: + "@csstools/utilities" "^2.0.0" + postcss-value-parser "^4.2.0" + +"@csstools/postcss-gamut-mapping@^2.0.6": + version "2.0.6" + resolved "https://registry.yarnpkg.com/@csstools/postcss-gamut-mapping/-/postcss-gamut-mapping-2.0.6.tgz#04ec6a50fdbca2a30dec56e6bb780c79621e47a7" + integrity sha512-0ke7fmXfc8H+kysZz246yjirAH6JFhyX9GTlyRnM0exHO80XcA9zeJpy5pOp5zo/AZiC/q5Pf+Hw7Pd6/uAoYA== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + +"@csstools/postcss-gradients-interpolation-method@^5.0.6": + version "5.0.6" + resolved "https://registry.yarnpkg.com/@csstools/postcss-gradients-interpolation-method/-/postcss-gradients-interpolation-method-5.0.6.tgz#67fa61ada95e4534687fa76cd2d15ac74386560e" + integrity sha512-Itrbx6SLUzsZ6Mz3VuOlxhbfuyLTogG5DwEF1V8dAi24iMuvQPIHd7Ti+pNDp7j6WixndJGZaoNR0f9VSzwuTg== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-hwb-function@^4.0.6": + version "4.0.6" + resolved "https://registry.yarnpkg.com/@csstools/postcss-hwb-function/-/postcss-hwb-function-4.0.6.tgz#c40f557a54ed45e75c601a9ba7a08d315f64dbd7" + integrity sha512-927Pqy3a1uBP7U8sTfaNdZVB0mNXzIrJO/GZ8us9219q9n06gOqCdfZ0E6d1P66Fm0fYHvxfDbfcUuwAn5UwhQ== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-ic-unit@^4.0.0": + version "4.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-ic-unit/-/postcss-ic-unit-4.0.0.tgz#b60ec06500717c337447c39ae7fe7952eeb9d48f" + integrity sha512-9QT5TDGgx7wD3EEMN3BSUG6ckb6Eh5gSPT5kZoVtUuAonfPmLDJyPhqR4ntPpMYhUKAMVKAg3I/AgzqHMSeLhA== + dependencies: + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + postcss-value-parser "^4.2.0" + +"@csstools/postcss-initial@^2.0.0": + version "2.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-initial/-/postcss-initial-2.0.0.tgz#a86f5fc59ab9f16f1422dade4c58bd941af5df22" + integrity sha512-dv2lNUKR+JV+OOhZm9paWzYBXOCi+rJPqJ2cJuhh9xd8USVrd0cBEPczla81HNOyThMQWeCcdln3gZkQV2kYxA== + +"@csstools/postcss-is-pseudo-class@^5.0.1": + version "5.0.1" + resolved "https://registry.yarnpkg.com/@csstools/postcss-is-pseudo-class/-/postcss-is-pseudo-class-5.0.1.tgz#12041448fedf01090dd4626022c28b7f7623f58e" + integrity sha512-JLp3POui4S1auhDR0n8wHd/zTOWmMsmK3nQd3hhL6FhWPaox5W7j1se6zXOG/aP07wV2ww0lxbKYGwbBszOtfQ== + dependencies: + "@csstools/selector-specificity" "^5.0.0" + postcss-selector-parser "^7.0.0" + +"@csstools/postcss-light-dark-function@^2.0.7": + version "2.0.7" + resolved "https://registry.yarnpkg.com/@csstools/postcss-light-dark-function/-/postcss-light-dark-function-2.0.7.tgz#807c170cd28eebb0c00e64dfc6ab0bf418f19209" + integrity sha512-ZZ0rwlanYKOHekyIPaU+sVm3BEHCe+Ha0/px+bmHe62n0Uc1lL34vbwrLYn6ote8PHlsqzKeTQdIejQCJ05tfw== + dependencies: + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-logical-float-and-clear@^3.0.0": + version "3.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-logical-float-and-clear/-/postcss-logical-float-and-clear-3.0.0.tgz#62617564182cf86ab5d4e7485433ad91e4c58571" + integrity sha512-SEmaHMszwakI2rqKRJgE+8rpotFfne1ZS6bZqBoQIicFyV+xT1UF42eORPxJkVJVrH9C0ctUgwMSn3BLOIZldQ== + +"@csstools/postcss-logical-overflow@^2.0.0": + version "2.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-logical-overflow/-/postcss-logical-overflow-2.0.0.tgz#c6de7c5f04e3d4233731a847f6c62819bcbcfa1d" + integrity sha512-spzR1MInxPuXKEX2csMamshR4LRaSZ3UXVaRGjeQxl70ySxOhMpP2252RAFsg8QyyBXBzuVOOdx1+bVO5bPIzA== + +"@csstools/postcss-logical-overscroll-behavior@^2.0.0": + version "2.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-logical-overscroll-behavior/-/postcss-logical-overscroll-behavior-2.0.0.tgz#43c03eaecdf34055ef53bfab691db6dc97a53d37" + integrity sha512-e/webMjoGOSYfqLunyzByZj5KKe5oyVg/YSbie99VEaSDE2kimFm0q1f6t/6Jo+VVCQ/jbe2Xy+uX+C4xzWs4w== + +"@csstools/postcss-logical-resize@^3.0.0": + version "3.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-logical-resize/-/postcss-logical-resize-3.0.0.tgz#4df0eeb1a61d7bd85395e56a5cce350b5dbfdca6" + integrity sha512-DFbHQOFW/+I+MY4Ycd/QN6Dg4Hcbb50elIJCfnwkRTCX05G11SwViI5BbBlg9iHRl4ytB7pmY5ieAFk3ws7yyg== + dependencies: + postcss-value-parser "^4.2.0" + +"@csstools/postcss-logical-viewport-units@^3.0.3": + version "3.0.3" + resolved "https://registry.yarnpkg.com/@csstools/postcss-logical-viewport-units/-/postcss-logical-viewport-units-3.0.3.tgz#f6cc63520ca2a6eb76b9cd946070c38dda66d733" + integrity sha512-OC1IlG/yoGJdi0Y+7duz/kU/beCwO+Gua01sD6GtOtLi7ByQUpcIqs7UE/xuRPay4cHgOMatWdnDdsIDjnWpPw== + dependencies: + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-media-minmax@^2.0.5": + version "2.0.5" + resolved "https://registry.yarnpkg.com/@csstools/postcss-media-minmax/-/postcss-media-minmax-2.0.5.tgz#66970aa8d8057f84b88aff21f385194fbe03eb11" + integrity sha512-sdh5i5GToZOIAiwhdntRWv77QDtsxP2r2gXW/WbLSCoLr00KTq/yiF1qlQ5XX2+lmiFa8rATKMcbwl3oXDMNew== + dependencies: + "@csstools/css-calc" "^2.1.0" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/media-query-list-parser" "^4.0.2" + +"@csstools/postcss-media-queries-aspect-ratio-number-values@^3.0.4": + version "3.0.4" + resolved "https://registry.yarnpkg.com/@csstools/postcss-media-queries-aspect-ratio-number-values/-/postcss-media-queries-aspect-ratio-number-values-3.0.4.tgz#d71102172c74baf3f892fac88cf1ea46a961600d" + integrity sha512-AnGjVslHMm5xw9keusQYvjVWvuS7KWK+OJagaG0+m9QnIjZsrysD2kJP/tr/UJIyYtMCtu8OkUd+Rajb4DqtIQ== + dependencies: + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/media-query-list-parser" "^4.0.2" + +"@csstools/postcss-nested-calc@^4.0.0": + version "4.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-nested-calc/-/postcss-nested-calc-4.0.0.tgz#754e10edc6958d664c11cde917f44ba144141c62" + integrity sha512-jMYDdqrQQxE7k9+KjstC3NbsmC063n1FTPLCgCRS2/qHUbHM0mNy9pIn4QIiQGs9I/Bg98vMqw7mJXBxa0N88A== + dependencies: + "@csstools/utilities" "^2.0.0" + postcss-value-parser "^4.2.0" + +"@csstools/postcss-normalize-display-values@^4.0.0": + version "4.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-normalize-display-values/-/postcss-normalize-display-values-4.0.0.tgz#ecdde2daf4e192e5da0c6fd933b6d8aff32f2a36" + integrity sha512-HlEoG0IDRoHXzXnkV4in47dzsxdsjdz6+j7MLjaACABX2NfvjFS6XVAnpaDyGesz9gK2SC7MbNwdCHusObKJ9Q== + dependencies: + postcss-value-parser "^4.2.0" + +"@csstools/postcss-oklab-function@^4.0.6": + version "4.0.6" + resolved "https://registry.yarnpkg.com/@csstools/postcss-oklab-function/-/postcss-oklab-function-4.0.6.tgz#17e8dfb6422dfd8d77256def5d5be8335ea7af34" + integrity sha512-Hptoa0uX+XsNacFBCIQKTUBrFKDiplHan42X73EklG6XmQLG7/aIvxoNhvZ7PvOWMt67Pw3bIlUY2nD6p5vL8A== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-progressive-custom-properties@^4.0.0": + version "4.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-progressive-custom-properties/-/postcss-progressive-custom-properties-4.0.0.tgz#ecdb85bcdb1852d73970a214a376684a91f82bdc" + integrity sha512-XQPtROaQjomnvLUSy/bALTR5VCtTVUFwYs1SblvYgLSeTo2a/bMNwUwo2piXw5rTv/FEYiy5yPSXBqg9OKUx7Q== + dependencies: + postcss-value-parser "^4.2.0" + +"@csstools/postcss-random-function@^1.0.1": + version "1.0.1" + resolved "https://registry.yarnpkg.com/@csstools/postcss-random-function/-/postcss-random-function-1.0.1.tgz#73a0b62b5dbbc03c25a28f085235eb61b09a2fb0" + integrity sha512-Ab/tF8/RXktQlFwVhiC70UNfpFQRhtE5fQQoP2pO+KCPGLsLdWFiOuHgSRtBOqEshCVAzR4H6o38nhvRZq8deA== + dependencies: + "@csstools/css-calc" "^2.1.0" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + +"@csstools/postcss-relative-color-syntax@^3.0.6": + version "3.0.6" + resolved "https://registry.yarnpkg.com/@csstools/postcss-relative-color-syntax/-/postcss-relative-color-syntax-3.0.6.tgz#4b8bc219b34b16f5abdbbcf09ac13e65bff6ef16" + integrity sha512-yxP618Xb+ji1I624jILaYM62uEmZcmbdmFoZHoaThw896sq0vU39kqTTF+ZNic9XyPtPMvq0vyvbgmHaszq8xg== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +"@csstools/postcss-scope-pseudo-class@^4.0.1": + version "4.0.1" + resolved "https://registry.yarnpkg.com/@csstools/postcss-scope-pseudo-class/-/postcss-scope-pseudo-class-4.0.1.tgz#9fe60e9d6d91d58fb5fc6c768a40f6e47e89a235" + integrity sha512-IMi9FwtH6LMNuLea1bjVMQAsUhFxJnyLSgOp/cpv5hrzWmrUYU5fm0EguNDIIOHUqzXode8F/1qkC/tEo/qN8Q== dependencies: - "@babel/core" "^7.18.6" - "@babel/generator" "^7.18.7" + postcss-selector-parser "^7.0.0" + +"@csstools/postcss-sign-functions@^1.1.0": + version "1.1.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-sign-functions/-/postcss-sign-functions-1.1.0.tgz#a524fae1374b0e167729f612ca875d7b1b334262" + integrity sha512-SLcc20Nujx/kqbSwDmj6oaXgpy3UjFhBy1sfcqPgDkHfOIfUtUVH7OXO+j7BU4v/At5s61N5ZX6shvgPwluhsA== + dependencies: + "@csstools/css-calc" "^2.1.0" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + +"@csstools/postcss-stepped-value-functions@^4.0.5": + version "4.0.5" + resolved "https://registry.yarnpkg.com/@csstools/postcss-stepped-value-functions/-/postcss-stepped-value-functions-4.0.5.tgz#4d68633d502fbe2b6ef3898e368e3540488a0d8a" + integrity sha512-G6SJ6hZJkhxo6UZojVlLo14MohH4J5J7z8CRBrxxUYy9JuZiIqUo5TBYyDGcE0PLdzpg63a7mHSJz3VD+gMwqw== + dependencies: + "@csstools/css-calc" "^2.1.0" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + +"@csstools/postcss-text-decoration-shorthand@^4.0.1": + version "4.0.1" + resolved "https://registry.yarnpkg.com/@csstools/postcss-text-decoration-shorthand/-/postcss-text-decoration-shorthand-4.0.1.tgz#251fab0939d50c6fd73bb2b830b2574188efa087" + integrity sha512-xPZIikbx6jyzWvhms27uugIc0I4ykH4keRvoa3rxX5K7lEhkbd54rjj/dv60qOCTisoS+3bmwJTeyV1VNBrXaw== + dependencies: + "@csstools/color-helpers" "^5.0.1" + postcss-value-parser "^4.2.0" + +"@csstools/postcss-trigonometric-functions@^4.0.5": + version "4.0.5" + resolved "https://registry.yarnpkg.com/@csstools/postcss-trigonometric-functions/-/postcss-trigonometric-functions-4.0.5.tgz#267b95a8bd45536e0360596b6da660a9eb6aac83" + integrity sha512-/YQThYkt5MLvAmVu7zxjhceCYlKrYddK6LEmK5I4ojlS6BmO9u2yO4+xjXzu2+NPYmHSTtP4NFSamBCMmJ1NJA== + dependencies: + "@csstools/css-calc" "^2.1.0" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + +"@csstools/postcss-unset-value@^4.0.0": + version "4.0.0" + resolved "https://registry.yarnpkg.com/@csstools/postcss-unset-value/-/postcss-unset-value-4.0.0.tgz#7caa981a34196d06a737754864baf77d64de4bba" + integrity sha512-cBz3tOCI5Fw6NIFEwU3RiwK6mn3nKegjpJuzCndoGq3BZPkUjnsq7uQmIeMNeMbMk7YD2MfKcgCpZwX5jyXqCA== + +"@csstools/selector-resolve-nested@^3.0.0": + version "3.0.0" + resolved "https://registry.yarnpkg.com/@csstools/selector-resolve-nested/-/selector-resolve-nested-3.0.0.tgz#704a9b637975680e025e069a4c58b3beb3e2752a" + integrity sha512-ZoK24Yku6VJU1gS79a5PFmC8yn3wIapiKmPgun0hZgEI5AOqgH2kiPRsPz1qkGv4HL+wuDLH83yQyk6inMYrJQ== + +"@csstools/selector-specificity@^5.0.0": + version "5.0.0" + resolved "https://registry.yarnpkg.com/@csstools/selector-specificity/-/selector-specificity-5.0.0.tgz#037817b574262134cabd68fc4ec1a454f168407b" + integrity sha512-PCqQV3c4CoVm3kdPhyeZ07VmBRdH2EpMFA/pd9OASpOEC3aXNGoqPDAZ80D0cLpMBxnmk0+yNhGsEx31hq7Gtw== + +"@csstools/utilities@^2.0.0": + version "2.0.0" + resolved "https://registry.yarnpkg.com/@csstools/utilities/-/utilities-2.0.0.tgz#f7ff0fee38c9ffb5646d47b6906e0bc8868bde60" + integrity sha512-5VdOr0Z71u+Yp3ozOx8T11N703wIFGVRgOWbOZMKgglPJsWA54MRIoMNVMa7shUToIhx5J8vX4sOZgD2XiihiQ== + +"@discoveryjs/json-ext@0.5.7": + version "0.5.7" + resolved "https://registry.yarnpkg.com/@discoveryjs/json-ext/-/json-ext-0.5.7.tgz#1d572bfbbe14b7704e0ba0f39b74815b84870d70" + integrity sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw== + +"@docsearch/css@3.8.2": + version "3.8.2" + resolved "https://registry.yarnpkg.com/@docsearch/css/-/css-3.8.2.tgz#7973ceb6892c30f154ba254cd05c562257a44977" + integrity sha512-y05ayQFyUmCXze79+56v/4HpycYF3uFqB78pLPrSV5ZKAlDuIAAJNhaRi8tTdRNXh05yxX/TyNnzD6LwSM89vQ== + +"@docsearch/react@^3.5.2": + version "3.8.2" + resolved "https://registry.yarnpkg.com/@docsearch/react/-/react-3.8.2.tgz#7b11d39b61c976c0aa9fbde66e6b73b30f3acd42" + integrity sha512-xCRrJQlTt8N9GU0DG4ptwHRkfnSnD/YpdeaXe02iKfqs97TkZJv60yE+1eq/tjPcVnTW8dP5qLP7itifFVV5eg== + dependencies: + "@algolia/autocomplete-core" "1.17.7" + "@algolia/autocomplete-preset-algolia" "1.17.7" + "@docsearch/css" "3.8.2" + algoliasearch "^5.14.2" + +"@docusaurus/babel@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/babel/-/babel-3.6.3.tgz#016714fe7a8807d0fc2f7180eace5e82bebbb8a6" + integrity sha512-7dW9Hat9EHYCVicFXYA4hjxBY38+hPuCURL8oRF9fySRm7vzNWuEOghA1TXcykuXZp0HLG2td4RhDxCvGG7tNw== + dependencies: + "@babel/core" "^7.25.9" + "@babel/generator" "^7.25.9" "@babel/plugin-syntax-dynamic-import" "^7.8.3" - "@babel/plugin-transform-runtime" "^7.18.6" - "@babel/preset-env" "^7.18.6" - "@babel/preset-react" "^7.18.6" - "@babel/preset-typescript" "^7.18.6" - "@babel/runtime" "^7.18.6" - "@babel/runtime-corejs3" "^7.18.6" - "@babel/traverse" "^7.18.8" - "@docusaurus/cssnano-preset" "2.4.1" - "@docusaurus/logger" "2.4.1" - "@docusaurus/mdx-loader" "2.4.1" - "@docusaurus/react-loadable" "5.5.2" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-common" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - "@slorber/static-site-generator-webpack-plugin" "^4.0.7" - "@svgr/webpack" "^6.2.1" - autoprefixer "^10.4.7" - babel-loader "^8.2.5" + "@babel/plugin-transform-runtime" "^7.25.9" + "@babel/preset-env" "^7.25.9" + "@babel/preset-react" "^7.25.9" + "@babel/preset-typescript" "^7.25.9" + "@babel/runtime" "^7.25.9" + "@babel/runtime-corejs3" "^7.25.9" + "@babel/traverse" "^7.25.9" + "@docusaurus/logger" "3.6.3" + "@docusaurus/utils" "3.6.3" babel-plugin-dynamic-import-node "^2.3.3" + fs-extra "^11.1.1" + tslib "^2.6.0" + +"@docusaurus/bundler@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/bundler/-/bundler-3.6.3.tgz#f09c2e29613f988b874a4be2247708e121b7fc5c" + integrity sha512-47JLuc8D4wA+6VOvmMd5fUC9rFppBQpQOnxDYiVXffm/DeV/wmm3sbpNd5Y+O+G2+nevLTRnvCm/qyancv0Y3A== + dependencies: + "@babel/core" "^7.25.9" + "@docusaurus/babel" "3.6.3" + "@docusaurus/cssnano-preset" "3.6.3" + "@docusaurus/logger" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils" "3.6.3" + babel-loader "^9.2.1" + clean-css "^5.3.2" + copy-webpack-plugin "^11.0.0" + css-loader "^6.8.1" + css-minimizer-webpack-plugin "^5.0.1" + cssnano "^6.1.2" + file-loader "^6.2.0" + html-minifier-terser "^7.2.0" + mini-css-extract-plugin "^2.9.1" + null-loader "^4.0.1" + postcss "^8.4.26" + postcss-loader "^7.3.3" + postcss-preset-env "^10.1.0" + react-dev-utils "^12.0.1" + terser-webpack-plugin "^5.3.9" + tslib "^2.6.0" + url-loader "^4.1.1" + webpack "^5.95.0" + webpackbar "^6.0.1" + +"@docusaurus/core@3.6.3", "@docusaurus/core@^3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/core/-/core-3.6.3.tgz#6bf968ee26a36d71387bab293f27ccffc0e428b6" + integrity sha512-xL7FRY9Jr5DWqB6pEnqgKqcMPJOX5V0pgWXi5lCiih11sUBmcFKM7c3+GyxcVeeWFxyYSDP3grLTWqJoP4P9Vw== + dependencies: + "@docusaurus/babel" "3.6.3" + "@docusaurus/bundler" "3.6.3" + "@docusaurus/logger" "3.6.3" + "@docusaurus/mdx-loader" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-common" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" boxen "^6.2.1" chalk "^4.1.2" chokidar "^3.5.3" - clean-css "^5.3.0" - cli-table3 "^0.6.2" + cli-table3 "^0.6.3" combine-promises "^1.1.0" commander "^5.1.0" - copy-webpack-plugin "^11.0.0" - core-js "^3.23.3" - css-loader "^6.7.1" - css-minimizer-webpack-plugin "^4.0.0" - cssnano "^5.1.12" + core-js "^3.31.1" del "^6.1.1" - detect-port "^1.3.0" + detect-port "^1.5.1" escape-html "^1.0.3" - eta "^2.0.0" - file-loader "^6.2.0" - fs-extra "^10.1.0" - html-minifier-terser "^6.1.0" - html-tags "^3.2.0" - html-webpack-plugin "^5.5.0" - import-fresh "^3.3.0" + eta "^2.2.0" + eval "^0.1.8" + fs-extra "^11.1.1" + html-tags "^3.3.1" + html-webpack-plugin "^5.6.0" leven "^3.1.0" lodash "^4.17.21" - mini-css-extract-plugin "^2.6.1" - postcss "^8.4.14" - postcss-loader "^7.0.0" + p-map "^4.0.0" prompts "^2.4.2" react-dev-utils "^12.0.1" react-helmet-async "^1.3.0" - react-loadable "npm:@docusaurus/react-loadable@5.5.2" + react-loadable "npm:@docusaurus/react-loadable@6.0.0" react-loadable-ssr-addon-v5-slorber "^1.0.1" - react-router "^5.3.3" + react-router "^5.3.4" react-router-config "^5.1.1" - react-router-dom "^5.3.3" + react-router-dom "^5.3.4" rtl-detect "^1.0.4" - semver "^7.3.7" - serve-handler "^6.1.3" + semver "^7.5.4" + serve-handler "^6.1.6" shelljs "^0.8.5" - terser-webpack-plugin "^5.3.3" - tslib "^2.4.0" - update-notifier "^5.1.0" - url-loader "^4.1.1" - wait-on "^6.0.1" - webpack "^5.73.0" - webpack-bundle-analyzer "^4.5.0" - webpack-dev-server "^4.9.3" - webpack-merge "^5.8.0" - webpackbar "^5.0.2" - -"@docusaurus/cssnano-preset@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/cssnano-preset/-/cssnano-preset-2.4.1.tgz" - integrity sha512-ka+vqXwtcW1NbXxWsh6yA1Ckii1klY9E53cJ4O9J09nkMBgrNX3iEFED1fWdv8wf4mJjvGi5RLZ2p9hJNjsLyQ== - dependencies: - cssnano-preset-advanced "^5.3.8" - postcss "^8.4.14" - postcss-sort-media-queries "^4.2.1" - tslib "^2.4.0" - -"@docusaurus/logger@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/logger/-/logger-2.4.1.tgz" - integrity sha512-5h5ysIIWYIDHyTVd8BjheZmQZmEgWDR54aQ1BX9pjFfpyzFo5puKXKYrYJXbjEHGyVhEzmB9UXwbxGfaZhOjcg== + tslib "^2.6.0" + update-notifier "^6.0.2" + webpack "^5.95.0" + webpack-bundle-analyzer "^4.10.2" + webpack-dev-server "^4.15.2" + webpack-merge "^6.0.1" + +"@docusaurus/cssnano-preset@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/cssnano-preset/-/cssnano-preset-3.6.3.tgz#ea19b307183ec20dea4927efc4ddf249150b8c6a" + integrity sha512-qP7SXrwZ+23GFJdPN4aIHQrZW+oH/7tzwEuc/RNL0+BdZdmIjYQqUxdXsjE4lFxLNZjj0eUrSNYIS6xwfij+5Q== + dependencies: + cssnano-preset-advanced "^6.1.2" + postcss "^8.4.38" + postcss-sort-media-queries "^5.2.0" + tslib "^2.6.0" + +"@docusaurus/logger@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/logger/-/logger-3.6.3.tgz#c6e514c9429487ef38be2f2129b2b842740d92fd" + integrity sha512-xSubJixcNyMV9wMV4q0s47CBz3Rlc5jbcCCuij8pfQP8qn/DIpt0ks8W6hQWzHAedg/J/EwxxUOUrnEoKzJo8g== dependencies: chalk "^4.1.2" - tslib "^2.4.0" - -"@docusaurus/mdx-loader@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/mdx-loader/-/mdx-loader-2.4.1.tgz" - integrity sha512-4KhUhEavteIAmbBj7LVFnrVYDiU51H5YWW1zY6SmBSte/YLhDutztLTBE0PQl1Grux1jzUJeaSvAzHpTn6JJDQ== - dependencies: - "@babel/parser" "^7.18.8" - "@babel/traverse" "^7.18.8" - "@docusaurus/logger" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@mdx-js/mdx" "^1.6.22" + tslib "^2.6.0" + +"@docusaurus/mdx-loader@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/mdx-loader/-/mdx-loader-3.6.3.tgz#127babc7cdb26d37c723bc3ae518bda17ce40160" + integrity sha512-3iJdiDz9540ppBseeI93tWTDtUGVkxzh59nMq4ignylxMuXBLK8dFqVeaEor23v1vx6TrGKZ2FuLaTB+U7C0QQ== + dependencies: + "@docusaurus/logger" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + "@mdx-js/mdx" "^3.0.0" + "@slorber/remark-comment" "^1.0.0" escape-html "^1.0.3" + estree-util-value-to-estree "^3.0.1" file-loader "^6.2.0" - fs-extra "^10.1.0" - image-size "^1.0.1" - mdast-util-to-string "^2.0.0" - remark-emoji "^2.2.0" + fs-extra "^11.1.1" + image-size "^1.0.2" + mdast-util-mdx "^3.0.0" + mdast-util-to-string "^4.0.0" + rehype-raw "^7.0.0" + remark-directive "^3.0.0" + remark-emoji "^4.0.0" + remark-frontmatter "^5.0.0" + remark-gfm "^4.0.0" stringify-object "^3.3.0" - tslib "^2.4.0" - unified "^9.2.2" - unist-util-visit "^2.0.3" + tslib "^2.6.0" + unified "^11.0.3" + unist-util-visit "^5.0.0" url-loader "^4.1.1" - webpack "^5.73.0" + vfile "^6.0.1" + webpack "^5.88.1" -"@docusaurus/module-type-aliases@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/module-type-aliases/-/module-type-aliases-2.4.1.tgz" - integrity sha512-gLBuIFM8Dp2XOCWffUDSjtxY7jQgKvYujt7Mx5s4FCTfoL5dN1EVbnrn+O2Wvh8b0a77D57qoIDY7ghgmatR1A== +"@docusaurus/module-type-aliases@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/module-type-aliases/-/module-type-aliases-3.6.3.tgz#1f7030b1cf1f658cf664d41b6eadba93bbe51d87" + integrity sha512-MjaXX9PN/k5ugNvfRZdWyKWq4FsrhN4LEXaj0pEmMebJuBNlFeGyKQUa9DRhJHpadNaiMLrbo9m3U7Ig5YlsZg== dependencies: - "@docusaurus/react-loadable" "5.5.2" - "@docusaurus/types" "2.4.1" + "@docusaurus/types" "3.6.3" "@types/history" "^4.7.11" "@types/react" "*" "@types/react-router-config" "*" "@types/react-router-dom" "*" react-helmet-async "*" - react-loadable "npm:@docusaurus/react-loadable@5.5.2" - -"@docusaurus/plugin-client-redirects@^2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-client-redirects/-/plugin-client-redirects-2.4.1.tgz" - integrity sha512-tp0j16gaLIJ4p+IR0P6KDOFsTOGGMY54MNPnmM61Vaqqt5omLqsuKUO8UlCGU1oW/4EIQOhXYy99XYY5MjE+7A== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/logger" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-common" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - eta "^2.0.0" - fs-extra "^10.1.0" + react-loadable "npm:@docusaurus/react-loadable@6.0.0" + +"@docusaurus/plugin-client-redirects@^3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-client-redirects/-/plugin-client-redirects-3.6.3.tgz#a641fc8c6ab3a2afec183d57de7e12d8b5d6ec9f" + integrity sha512-fQDCxoJCO1jXNQGQmhgYoX3Yx+Z2xSbrLf3PBET6pHnsRk6gGW/VuCHcfQuZlJzbTxN0giQ5u3XcQQ/LzXftJA== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/logger" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-common" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + eta "^2.2.0" + fs-extra "^11.1.1" lodash "^4.17.21" - tslib "^2.4.0" - -"@docusaurus/plugin-content-blog@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-content-blog/-/plugin-content-blog-2.4.1.tgz" - integrity sha512-E2i7Knz5YIbE1XELI6RlTnZnGgS52cUO4BlCiCUCvQHbR+s1xeIWz4C6BtaVnlug0Ccz7nFSksfwDpVlkujg5Q== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/logger" "2.4.1" - "@docusaurus/mdx-loader" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-common" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - cheerio "^1.0.0-rc.12" + tslib "^2.6.0" + +"@docusaurus/plugin-content-blog@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-content-blog/-/plugin-content-blog-3.6.3.tgz#d6a597e4bfdeb3f1f6ce06d2ac86207296988cc9" + integrity sha512-k0ogWwwJU3pFRFfvW1kRVHxzf2DutLGaaLjAnHVEU6ju+aRP0Z5ap/13DHyPOfHeE4WKpn/M0TqjdwZAcY3kAw== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/logger" "3.6.3" + "@docusaurus/mdx-loader" "3.6.3" + "@docusaurus/theme-common" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-common" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + cheerio "1.0.0-rc.12" feed "^4.2.2" - fs-extra "^10.1.0" + fs-extra "^11.1.1" lodash "^4.17.21" reading-time "^1.5.0" - tslib "^2.4.0" - unist-util-visit "^2.0.3" + srcset "^4.0.0" + tslib "^2.6.0" + unist-util-visit "^5.0.0" utility-types "^3.10.0" - webpack "^5.73.0" - -"@docusaurus/plugin-content-docs@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-content-docs/-/plugin-content-docs-2.4.1.tgz" - integrity sha512-Lo7lSIcpswa2Kv4HEeUcGYqaasMUQNpjTXpV0N8G6jXgZaQurqp7E8NGYeGbDXnb48czmHWbzDL4S3+BbK0VzA== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/logger" "2.4.1" - "@docusaurus/mdx-loader" "2.4.1" - "@docusaurus/module-type-aliases" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - "@types/react-router-config" "^5.0.6" + webpack "^5.88.1" + +"@docusaurus/plugin-content-docs@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-content-docs/-/plugin-content-docs-3.6.3.tgz#aae044d2af6996d1a6de8d815aca8a83b485e0a5" + integrity sha512-r2wS8y/fsaDcxkm20W5bbYJFPzdWdEaTWVYjNxlHlcmX086eqQR1Fomlg9BHTJ0dLXPzAlbC8EN4XqMr3QzNCQ== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/logger" "3.6.3" + "@docusaurus/mdx-loader" "3.6.3" + "@docusaurus/module-type-aliases" "3.6.3" + "@docusaurus/theme-common" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-common" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + "@types/react-router-config" "^5.0.7" combine-promises "^1.1.0" - fs-extra "^10.1.0" - import-fresh "^3.3.0" + fs-extra "^11.1.1" js-yaml "^4.1.0" lodash "^4.17.21" - tslib "^2.4.0" + tslib "^2.6.0" utility-types "^3.10.0" - webpack "^5.73.0" - -"@docusaurus/plugin-content-pages@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-content-pages/-/plugin-content-pages-2.4.1.tgz" - integrity sha512-/UjuH/76KLaUlL+o1OvyORynv6FURzjurSjvn2lbWTFc4tpYY2qLYTlKpTCBVPhlLUQsfyFnshEJDLmPneq2oA== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/mdx-loader" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - fs-extra "^10.1.0" - tslib "^2.4.0" - webpack "^5.73.0" - -"@docusaurus/plugin-debug@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-debug/-/plugin-debug-2.4.1.tgz" - integrity sha512-7Yu9UPzRShlrH/G8btOpR0e6INFZr0EegWplMjOqelIwAcx3PKyR8mgPTxGTxcqiYj6hxSCRN0D8R7YrzImwNA== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils" "2.4.1" - fs-extra "^10.1.0" - react-json-view "^1.21.3" - tslib "^2.4.0" - -"@docusaurus/plugin-google-analytics@2.4.1", "@docusaurus/plugin-google-analytics@^2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-google-analytics/-/plugin-google-analytics-2.4.1.tgz" - integrity sha512-dyZJdJiCoL+rcfnm0RPkLt/o732HvLiEwmtoNzOoz9MSZz117UH2J6U2vUDtzUzwtFLIf32KkeyzisbwUCgcaQ== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - tslib "^2.4.0" - -"@docusaurus/plugin-google-gtag@2.4.1", "@docusaurus/plugin-google-gtag@^2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-google-gtag/-/plugin-google-gtag-2.4.1.tgz" - integrity sha512-mKIefK+2kGTQBYvloNEKtDmnRD7bxHLsBcxgnbt4oZwzi2nxCGjPX6+9SQO2KCN5HZbNrYmGo5GJfMgoRvy6uA== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - tslib "^2.4.0" - -"@docusaurus/plugin-google-tag-manager@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-google-tag-manager/-/plugin-google-tag-manager-2.4.1.tgz" - integrity sha512-Zg4Ii9CMOLfpeV2nG74lVTWNtisFaH9QNtEw48R5QE1KIwDBdTVaiSA18G1EujZjrzJJzXN79VhINSbOJO/r3g== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - tslib "^2.4.0" - -"@docusaurus/plugin-sitemap@2.4.1", "@docusaurus/plugin-sitemap@^2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/plugin-sitemap/-/plugin-sitemap-2.4.1.tgz" - integrity sha512-lZx+ijt/+atQ3FVE8FOHV/+X3kuok688OydDXrqKRJyXBJZKgGjA2Qa8RjQ4f27V2woaXhtnyrdPop/+OjVMRg== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/logger" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-common" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - fs-extra "^10.1.0" + webpack "^5.88.1" + +"@docusaurus/plugin-content-pages@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-content-pages/-/plugin-content-pages-3.6.3.tgz#0a5a43d1677ee519f63a54634653c54ddf41f475" + integrity sha512-eHrmTgjgLZsuqfsYr5X2xEwyIcck0wseSofWrjTwT9FLOWp+KDmMAuVK+wRo7sFImWXZk3oV/xX/g9aZrhD7OA== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/mdx-loader" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + fs-extra "^11.1.1" + tslib "^2.6.0" + webpack "^5.88.1" + +"@docusaurus/plugin-debug@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-debug/-/plugin-debug-3.6.3.tgz#4e62ddfbae4d597b073f8e3c632cc12d012339e3" + integrity sha512-zB9GXfIZNPRfzKnNjU6xGVrqn9bPXuGhpjgsuc/YtcTDjnjhasg38NdYd5LEqXex5G/zIorQgWB3n6x/Ut62vQ== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils" "3.6.3" + fs-extra "^11.1.1" + react-json-view-lite "^1.2.0" + tslib "^2.6.0" + +"@docusaurus/plugin-google-analytics@3.6.3", "@docusaurus/plugin-google-analytics@^3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-google-analytics/-/plugin-google-analytics-3.6.3.tgz#63648d469b1e3c50fad8878e7a7db9856e503d5f" + integrity sha512-rCDNy1QW8Dag7nZq67pcum0bpFLrwvxJhYuVprhFh8BMBDxV0bY+bAkGHbSf68P3Bk9C3hNOAXX1srGLIDvcTA== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + tslib "^2.6.0" + +"@docusaurus/plugin-google-gtag@3.6.3", "@docusaurus/plugin-google-gtag@^3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-google-gtag/-/plugin-google-gtag-3.6.3.tgz#8a1388b4123904be17e661ea7aa71d798d0c046e" + integrity sha512-+OyDvhM6rqVkQOmLVkQWVJAizEEfkPzVWtIHXlWPOCFGK9X4/AWeBSrU0WG4iMg9Z4zD4YDRrU+lvI4s6DSC+w== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + "@types/gtag.js" "^0.0.12" + tslib "^2.6.0" + +"@docusaurus/plugin-google-tag-manager@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-google-tag-manager/-/plugin-google-tag-manager-3.6.3.tgz#38cbe416803f29782807cebf3ebf240cb47c3c74" + integrity sha512-1M6UPB13gWUtN2UHX083/beTn85PlRI9ABItTl/JL1FJ5dJTWWFXXsHf9WW/6hrVwthwTeV/AGbGKvLKV+IlCA== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + tslib "^2.6.0" + +"@docusaurus/plugin-sitemap@3.6.3", "@docusaurus/plugin-sitemap@^3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/plugin-sitemap/-/plugin-sitemap-3.6.3.tgz#0458e6f7476ab6fd1466e01b153a3211d3223c53" + integrity sha512-94qOO4M9Fwv9KfVQJsgbe91k+fPJ4byf1L3Ez8TUa6TAFPo/BrLwQ80zclHkENlL1824TuxkcMKv33u6eydQCg== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/logger" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-common" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + fs-extra "^11.1.1" sitemap "^7.1.1" - tslib "^2.4.0" - -"@docusaurus/preset-classic@^2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/preset-classic/-/preset-classic-2.4.1.tgz" - integrity sha512-P4//+I4zDqQJ+UDgoFrjIFaQ1MeS9UD1cvxVQaI6O7iBmiHQm0MGROP1TbE7HlxlDPXFJjZUK3x3cAoK63smGQ== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/plugin-content-blog" "2.4.1" - "@docusaurus/plugin-content-docs" "2.4.1" - "@docusaurus/plugin-content-pages" "2.4.1" - "@docusaurus/plugin-debug" "2.4.1" - "@docusaurus/plugin-google-analytics" "2.4.1" - "@docusaurus/plugin-google-gtag" "2.4.1" - "@docusaurus/plugin-google-tag-manager" "2.4.1" - "@docusaurus/plugin-sitemap" "2.4.1" - "@docusaurus/theme-classic" "2.4.1" - "@docusaurus/theme-common" "2.4.1" - "@docusaurus/theme-search-algolia" "2.4.1" - "@docusaurus/types" "2.4.1" - -"@docusaurus/react-loadable@5.5.2": - version "5.5.2" - resolved "https://registry.npmjs.org/@docusaurus/react-loadable/-/react-loadable-5.5.2.tgz" - integrity sha512-A3dYjdBGuy0IGT+wyLIGIKLRE+sAk1iNk0f1HjNDysO7u8lhL4N3VEm+FAubmJbAztn94F7MxBTPmnixbiyFdQ== - dependencies: - "@types/react" "*" - prop-types "^15.6.2" - -"@docusaurus/theme-classic@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/theme-classic/-/theme-classic-2.4.1.tgz" - integrity sha512-Rz0wKUa+LTW1PLXmwnf8mn85EBzaGSt6qamqtmnh9Hflkc+EqiYMhtUJeLdV+wsgYq4aG0ANc+bpUDpsUhdnwg== - dependencies: - "@docusaurus/core" "2.4.1" - "@docusaurus/mdx-loader" "2.4.1" - "@docusaurus/module-type-aliases" "2.4.1" - "@docusaurus/plugin-content-blog" "2.4.1" - "@docusaurus/plugin-content-docs" "2.4.1" - "@docusaurus/plugin-content-pages" "2.4.1" - "@docusaurus/theme-common" "2.4.1" - "@docusaurus/theme-translations" "2.4.1" - "@docusaurus/types" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-common" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - "@mdx-js/react" "^1.6.22" - clsx "^1.2.1" - copy-text-to-clipboard "^3.0.1" - infima "0.2.0-alpha.43" + tslib "^2.6.0" + +"@docusaurus/preset-classic@^3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/preset-classic/-/preset-classic-3.6.3.tgz#072298b5b6d0de7d0346b1e9b550a30ef2add56d" + integrity sha512-VHSYWROT3flvNNI1SrnMOtW1EsjeHNK9dhU6s9eY5hryZe79lUqnZJyze/ymDe2LXAqzyj6y5oYvyBoZZk6ErA== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/plugin-content-blog" "3.6.3" + "@docusaurus/plugin-content-docs" "3.6.3" + "@docusaurus/plugin-content-pages" "3.6.3" + "@docusaurus/plugin-debug" "3.6.3" + "@docusaurus/plugin-google-analytics" "3.6.3" + "@docusaurus/plugin-google-gtag" "3.6.3" + "@docusaurus/plugin-google-tag-manager" "3.6.3" + "@docusaurus/plugin-sitemap" "3.6.3" + "@docusaurus/theme-classic" "3.6.3" + "@docusaurus/theme-common" "3.6.3" + "@docusaurus/theme-search-algolia" "3.6.3" + "@docusaurus/types" "3.6.3" + +"@docusaurus/theme-classic@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/theme-classic/-/theme-classic-3.6.3.tgz#00599a9de5fd5c122fd1b8c59d3b755878f2a72c" + integrity sha512-1RRLK1tSArI2c00qugWYO3jRocjOZwGF1mBzPPylDVRwWCS/rnWWR91ChdbbaxIupRJ+hX8ZBYrwr5bbU0oztQ== + dependencies: + "@docusaurus/core" "3.6.3" + "@docusaurus/logger" "3.6.3" + "@docusaurus/mdx-loader" "3.6.3" + "@docusaurus/module-type-aliases" "3.6.3" + "@docusaurus/plugin-content-blog" "3.6.3" + "@docusaurus/plugin-content-docs" "3.6.3" + "@docusaurus/plugin-content-pages" "3.6.3" + "@docusaurus/theme-common" "3.6.3" + "@docusaurus/theme-translations" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-common" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + "@mdx-js/react" "^3.0.0" + clsx "^2.0.0" + copy-text-to-clipboard "^3.2.0" + infima "0.2.0-alpha.45" lodash "^4.17.21" nprogress "^0.2.0" - postcss "^8.4.14" - prism-react-renderer "^1.3.5" - prismjs "^1.28.0" - react-router-dom "^5.3.3" - rtlcss "^3.5.0" - tslib "^2.4.0" + postcss "^8.4.26" + prism-react-renderer "^2.3.0" + prismjs "^1.29.0" + react-router-dom "^5.3.4" + rtlcss "^4.1.0" + tslib "^2.6.0" utility-types "^3.10.0" -"@docusaurus/theme-common@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/theme-common/-/theme-common-2.4.1.tgz" - integrity sha512-G7Zau1W5rQTaFFB3x3soQoZpkgMbl/SYNG8PfMFIjKa3M3q8n0m/GRf5/H/e5BqOvt8c+ZWIXGCiz+kUCSHovA== - dependencies: - "@docusaurus/mdx-loader" "2.4.1" - "@docusaurus/module-type-aliases" "2.4.1" - "@docusaurus/plugin-content-blog" "2.4.1" - "@docusaurus/plugin-content-docs" "2.4.1" - "@docusaurus/plugin-content-pages" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-common" "2.4.1" +"@docusaurus/theme-common@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/theme-common/-/theme-common-3.6.3.tgz#a8a6ebd2b0fd7a5cca4d0c6a2f9ccff905fa7438" + integrity sha512-b8ZkhczXHDxWWyvz+YJy4t/PlPbEogTTbgnHoflYnH7rmRtyoodTsu8WVM12la5LmlMJBclBXFl29OH8kPE7gg== + dependencies: + "@docusaurus/mdx-loader" "3.6.3" + "@docusaurus/module-type-aliases" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-common" "3.6.3" "@types/history" "^4.7.11" "@types/react" "*" "@types/react-router-config" "*" - clsx "^1.2.1" + clsx "^2.0.0" parse-numeric-range "^1.3.0" - prism-react-renderer "^1.3.5" - tslib "^2.4.0" - use-sync-external-store "^1.2.0" + prism-react-renderer "^2.3.0" + tslib "^2.6.0" utility-types "^3.10.0" -"@docusaurus/theme-search-algolia@2.4.1", "@docusaurus/theme-search-algolia@^2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/theme-search-algolia/-/theme-search-algolia-2.4.1.tgz" - integrity sha512-6BcqW2lnLhZCXuMAvPRezFs1DpmEKzXFKlYjruuas+Xy3AQeFzDJKTJFIm49N77WFCTyxff8d3E4Q9pi/+5McQ== - dependencies: - "@docsearch/react" "^3.1.1" - "@docusaurus/core" "2.4.1" - "@docusaurus/logger" "2.4.1" - "@docusaurus/plugin-content-docs" "2.4.1" - "@docusaurus/theme-common" "2.4.1" - "@docusaurus/theme-translations" "2.4.1" - "@docusaurus/utils" "2.4.1" - "@docusaurus/utils-validation" "2.4.1" - algoliasearch "^4.13.1" - algoliasearch-helper "^3.10.0" - clsx "^1.2.1" - eta "^2.0.0" - fs-extra "^10.1.0" +"@docusaurus/theme-search-algolia@3.6.3", "@docusaurus/theme-search-algolia@^3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/theme-search-algolia/-/theme-search-algolia-3.6.3.tgz#1a3331a489f392f5b032c4efc5f431e57eddf7ce" + integrity sha512-rt+MGCCpYgPyWCGXtbxlwFbTSobu15jWBTPI2LHsHNa5B0zSmOISX6FWYAPt5X1rNDOqMGM0FATnh7TBHRohVA== + dependencies: + "@docsearch/react" "^3.5.2" + "@docusaurus/core" "3.6.3" + "@docusaurus/logger" "3.6.3" + "@docusaurus/plugin-content-docs" "3.6.3" + "@docusaurus/theme-common" "3.6.3" + "@docusaurus/theme-translations" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-validation" "3.6.3" + algoliasearch "^4.18.0" + algoliasearch-helper "^3.13.3" + clsx "^2.0.0" + eta "^2.2.0" + fs-extra "^11.1.1" lodash "^4.17.21" - tslib "^2.4.0" + tslib "^2.6.0" utility-types "^3.10.0" -"@docusaurus/theme-translations@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/theme-translations/-/theme-translations-2.4.1.tgz" - integrity sha512-T1RAGP+f86CA1kfE8ejZ3T3pUU3XcyvrGMfC/zxCtc2BsnoexuNI9Vk2CmuKCb+Tacvhxjv5unhxXce0+NKyvA== +"@docusaurus/theme-translations@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/theme-translations/-/theme-translations-3.6.3.tgz#6e473835ea016ce4acd7d2997f411811db8c4f6b" + integrity sha512-Gb0regclToVlngSIIwUCtBMQBq48qVUaN1XQNKW4XwlsgUyk0vP01LULdqbem7czSwIeBAFXFoORJ0RPX7ht/w== dependencies: - fs-extra "^10.1.0" - tslib "^2.4.0" + fs-extra "^11.1.1" + tslib "^2.6.0" -"@docusaurus/types@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/types/-/types-2.4.1.tgz" - integrity sha512-0R+cbhpMkhbRXX138UOc/2XZFF8hiZa6ooZAEEJFp5scytzCw4tC1gChMFXrpa3d2tYE6AX8IrOEpSonLmfQuQ== +"@docusaurus/types@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/types/-/types-3.6.3.tgz#e87592e31616da1b8dc473e4c8205c61885a1518" + integrity sha512-xD9oTGDrouWzefkhe9ogB2fDV96/82cRpNGx2HIvI5L87JHNhQVIWimQ/3JIiiX/TEd5S9s+VO6FFguwKNRVow== dependencies: + "@mdx-js/mdx" "^3.0.0" "@types/history" "^4.7.11" "@types/react" "*" commander "^5.1.0" - joi "^17.6.0" + joi "^17.9.2" react-helmet-async "^1.3.0" utility-types "^3.10.0" - webpack "^5.73.0" - webpack-merge "^5.8.0" - -"@docusaurus/utils-common@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/utils-common/-/utils-common-2.4.1.tgz" - integrity sha512-bCVGdZU+z/qVcIiEQdyx0K13OC5mYwxhSuDUR95oFbKVuXYRrTVrwZIqQljuo1fyJvFTKHiL9L9skQOPokuFNQ== - dependencies: - tslib "^2.4.0" - -"@docusaurus/utils-validation@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/utils-validation/-/utils-validation-2.4.1.tgz" - integrity sha512-unII3hlJlDwZ3w8U+pMO3Lx3RhI4YEbY3YNsQj4yzrkZzlpqZOLuAiZK2JyULnD+TKbceKU0WyWkQXtYbLNDFA== - dependencies: - "@docusaurus/logger" "2.4.1" - "@docusaurus/utils" "2.4.1" - joi "^17.6.0" + webpack "^5.95.0" + webpack-merge "^5.9.0" + +"@docusaurus/utils-common@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/utils-common/-/utils-common-3.6.3.tgz#57f840bd6f0928cf10060198cb421f1b9212c8f5" + integrity sha512-v4nKDaANLgT3pMBewHYEMAl/ufY0LkXao1QkFWzI5huWFOmNQ2UFzv2BiKeHX5Ownis0/w6cAyoxPhVdDonlSQ== + dependencies: + "@docusaurus/types" "3.6.3" + tslib "^2.6.0" + +"@docusaurus/utils-validation@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/utils-validation/-/utils-validation-3.6.3.tgz#3eca7125235eb90983ff660b97a71f331e331f57" + integrity sha512-bhEGGiN5BE38h21vjqD70Gxg++j+PfYVddDUE5UFvLDup68QOcpD33CLr+2knPorlxRbEaNfz6HQDUMQ3HuqKw== + dependencies: + "@docusaurus/logger" "3.6.3" + "@docusaurus/utils" "3.6.3" + "@docusaurus/utils-common" "3.6.3" + fs-extra "^11.2.0" + joi "^17.9.2" js-yaml "^4.1.0" - tslib "^2.4.0" + lodash "^4.17.21" + tslib "^2.6.0" -"@docusaurus/utils@2.4.1": - version "2.4.1" - resolved "https://registry.npmjs.org/@docusaurus/utils/-/utils-2.4.1.tgz" - integrity sha512-1lvEZdAQhKNht9aPXPoh69eeKnV0/62ROhQeFKKxmzd0zkcuE/Oc5Gpnt00y/f5bIsmOsYMY7Pqfm/5rteT5GA== +"@docusaurus/utils@3.6.3": + version "3.6.3" + resolved "https://registry.yarnpkg.com/@docusaurus/utils/-/utils-3.6.3.tgz#8dcb1969e4011a84dfb0a031da806dadddebf0ea" + integrity sha512-0R/FR3bKVl4yl8QwbL4TYFfR+OXBRpVUaTJdENapBGR3YMwfM6/JnhGilWQO8AOwPJGtGoDK7ib8+8UF9f3OZQ== dependencies: - "@docusaurus/logger" "2.4.1" - "@svgr/webpack" "^6.2.1" + "@docusaurus/logger" "3.6.3" + "@docusaurus/types" "3.6.3" + "@docusaurus/utils-common" "3.6.3" + "@svgr/webpack" "^8.1.0" escape-string-regexp "^4.0.0" file-loader "^6.2.0" - fs-extra "^10.1.0" - github-slugger "^1.4.0" + fs-extra "^11.1.1" + github-slugger "^1.5.0" globby "^11.1.0" gray-matter "^4.0.3" + jiti "^1.20.0" js-yaml "^4.1.0" lodash "^4.17.21" micromatch "^4.0.5" + prompts "^2.4.2" resolve-pathname "^3.0.0" shelljs "^0.8.5" - tslib "^2.4.0" + tslib "^2.6.0" url-loader "^4.1.1" - webpack "^5.73.0" + utility-types "^3.10.0" + webpack "^5.88.1" "@fortawesome/fontawesome-common-types@6.3.0": version "6.3.0" @@ -1660,54 +2133,37 @@ dependencies: prop-types "^15.8.1" -"@hapi/hoek@^9.0.0": +"@hapi/hoek@^9.0.0", "@hapi/hoek@^9.3.0": version "9.3.0" - resolved "https://registry.npmjs.org/@hapi/hoek/-/hoek-9.3.0.tgz" + resolved "https://registry.yarnpkg.com/@hapi/hoek/-/hoek-9.3.0.tgz#8368869dcb735be2e7f5cb7647de78e167a251fb" integrity sha512-/c6rf4UJlmHlC9b5BaNvzAcFv7HZ2QHaV0D4/HNlBdvFnvQq8RI4kYdhyPCl7Xj+oWvTWQ8ujhqS53LIgAe6KQ== -"@hapi/topo@^5.0.0": +"@hapi/topo@^5.1.0": version "5.1.0" - resolved "https://registry.npmjs.org/@hapi/topo/-/topo-5.1.0.tgz" + resolved "https://registry.yarnpkg.com/@hapi/topo/-/topo-5.1.0.tgz#dc448e332c6c6e37a4dc02fd84ba8d44b9afb012" integrity sha512-foQZKJig7Ob0BMAYBfcJk8d77QtOe7Wo4ox7ff1lQYoNNAb6jwcY1ncdoy2e9wQZzvNy7ODZCYJkK8kzmcAnAg== dependencies: "@hapi/hoek" "^9.0.0" -"@jest/schemas@^29.4.0": - version "29.4.0" - resolved "https://registry.npmjs.org/@jest/schemas/-/schemas-29.4.0.tgz" - integrity sha512-0E01f/gOZeNTG76i5eWWSupvSHaIINrTie7vCyjiYFKgzNdyEGd12BUv4oNBFHOqlHDbtoJi3HrQ38KCC90NsQ== +"@jest/schemas@^29.6.3": + version "29.6.3" + resolved "https://registry.yarnpkg.com/@jest/schemas/-/schemas-29.6.3.tgz#430b5ce8a4e0044a7e3819663305a7b3091c8e03" + integrity sha512-mo5j5X+jIZmJQveBKeS/clAueipV7KgiX1vMgCxam1RNYiqE1w62n0/tJJnHtjW8ZHcQco5gY85jA3mi0L+nSA== dependencies: - "@sinclair/typebox" "^0.25.16" + "@sinclair/typebox" "^0.27.8" -"@jest/types@^29.4.1": - version "29.4.1" - resolved "https://registry.npmjs.org/@jest/types/-/types-29.4.1.tgz" - integrity sha512-zbrAXDUOnpJ+FMST2rV7QZOgec8rskg2zv8g2ajeqitp4tvZiyqTCYXANrKsM+ryj5o+LI+ZN2EgU9drrkiwSA== +"@jest/types@^29.6.3": + version "29.6.3" + resolved "https://registry.yarnpkg.com/@jest/types/-/types-29.6.3.tgz#1131f8cf634e7e84c5e77bab12f052af585fba59" + integrity sha512-u3UPsIilWKOM3F9CXtrG8LEJmNxwoCQC/XVj4IKYXvvpx7QIi/Kg1LI5uDmDpKlac62NUtX7eLjRh+jVZcLOzw== dependencies: - "@jest/schemas" "^29.4.0" + "@jest/schemas" "^29.6.3" "@types/istanbul-lib-coverage" "^2.0.0" "@types/istanbul-reports" "^3.0.0" "@types/node" "*" "@types/yargs" "^17.0.8" chalk "^4.0.0" -"@jridgewell/gen-mapping@^0.1.0": - version "0.1.1" - resolved "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.1.1.tgz" - integrity sha512-sQXCasFk+U8lWYEe66WxRDOE9PjVz4vSM51fTu3Hw+ClTpUSQb718772vH3pyS5pShp6lvQM7SxgIDXXXmOX7w== - dependencies: - "@jridgewell/set-array" "^1.0.0" - "@jridgewell/sourcemap-codec" "^1.4.10" - -"@jridgewell/gen-mapping@^0.3.2": - version "0.3.2" - resolved "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.2.tgz" - integrity sha512-mh65xKQAzI6iBcFzwv28KVWSmCkdRBWoOh+bYQGW3+6OZvbbN3TqMGo5hqYxQniRcH9F2VZIoJCm4pa3BPDK/A== - dependencies: - "@jridgewell/set-array" "^1.0.1" - "@jridgewell/sourcemap-codec" "^1.4.10" - "@jridgewell/trace-mapping" "^0.3.9" - "@jridgewell/gen-mapping@^0.3.5": version "0.3.5" resolved "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.5.tgz" @@ -1722,7 +2178,7 @@ resolved "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.1.0.tgz" integrity sha512-F2msla3tad+Mfht5cJq7LSXcdudKTWCVYUgw6pLFOOHSTtZlj6SWNYAp+AhuqLmWdBO2X5hPrLcu8cVP8fy28w== -"@jridgewell/set-array@^1.0.0", "@jridgewell/set-array@^1.0.1", "@jridgewell/set-array@^1.2.1": +"@jridgewell/set-array@^1.2.1": version "1.2.1" resolved "https://registry.npmjs.org/@jridgewell/set-array/-/set-array-1.2.1.tgz" integrity sha512-R8gLRTZeyp03ymzP/6Lil/28tGeGEzhx1q2k703KGWRAI1VdvPIXdG70VJc2pAMw3NA6JKL5hhFu1sJX0Mnn/A== @@ -1740,7 +2196,7 @@ resolved "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.14.tgz" integrity sha512-XPSJHWmi394fuUuzDnGz1wiKqWfo1yXecHQMRf2l6hztTO+nPru658AyDngaBe7isIxEkRsPR3FZh+s7iVa4Uw== -"@jridgewell/trace-mapping@^0.3.17", "@jridgewell/trace-mapping@^0.3.20", "@jridgewell/trace-mapping@^0.3.24", "@jridgewell/trace-mapping@^0.3.25", "@jridgewell/trace-mapping@^0.3.9": +"@jridgewell/trace-mapping@^0.3.18", "@jridgewell/trace-mapping@^0.3.20", "@jridgewell/trace-mapping@^0.3.24", "@jridgewell/trace-mapping@^0.3.25": version "0.3.25" resolved "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.25.tgz" integrity sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ== @@ -1753,40 +2209,42 @@ resolved "https://registry.npmjs.org/@leichtgewicht/ip-codec/-/ip-codec-2.0.4.tgz" integrity sha512-Hcv+nVC0kZnQ3tD9GVu5xSMR4VVYOteQIr/hwFPVEvPdlXqgGEuRjiheChHgdM+JyqdgNcmzZOX/tnl0JOiI7A== -"@mdx-js/mdx@^1.6.22": - version "1.6.22" - resolved "https://registry.npmjs.org/@mdx-js/mdx/-/mdx-1.6.22.tgz" - integrity sha512-AMxuLxPz2j5/6TpF/XSdKpQP1NlG0z11dFOlq+2IP/lSgl11GY8ji6S/rgsViN/L0BDvHvUMruRb7ub+24LUYA== - dependencies: - "@babel/core" "7.12.9" - "@babel/plugin-syntax-jsx" "7.12.1" - "@babel/plugin-syntax-object-rest-spread" "7.8.3" - "@mdx-js/util" "1.6.22" - babel-plugin-apply-mdx-type-prop "1.6.22" - babel-plugin-extract-import-names "1.6.22" - camelcase-css "2.0.1" - detab "2.0.4" - hast-util-raw "6.0.1" - lodash.uniq "4.5.0" - mdast-util-to-hast "10.0.1" - remark-footnotes "2.0.0" - remark-mdx "1.6.22" - remark-parse "8.0.3" - remark-squeeze-paragraphs "4.0.0" - style-to-object "0.3.0" - unified "9.2.0" - unist-builder "2.0.3" - unist-util-visit "2.0.3" - -"@mdx-js/react@^1.6.22": - version "1.6.22" - resolved "https://registry.npmjs.org/@mdx-js/react/-/react-1.6.22.tgz" - integrity sha512-TDoPum4SHdfPiGSAaRBw7ECyI8VaHpK8GJugbJIJuqyh6kzw9ZLJZW3HGL3NNrJGxcAixUvqROm+YuQOo5eXtg== - -"@mdx-js/util@1.6.22": - version "1.6.22" - resolved "https://registry.npmjs.org/@mdx-js/util/-/util-1.6.22.tgz" - integrity sha512-H1rQc1ZOHANWBvPcW+JpGwr+juXSxM8Q8YCkm3GhZd8REu1fHR3z99CErO1p9pkcfcxZnMdIZdIsXkOHY0NilA== +"@mdx-js/mdx@^3.0.0": + version "3.1.0" + resolved "https://registry.yarnpkg.com/@mdx-js/mdx/-/mdx-3.1.0.tgz#10235cab8ad7d356c262e8c21c68df5850a97dc3" + integrity sha512-/QxEhPAvGwbQmy1Px8F899L5Uc2KZ6JtXwlCgJmjSTBedwOZkByYcBG4GceIGPXRDsmfxhHazuS+hlOShRLeDw== + dependencies: + "@types/estree" "^1.0.0" + "@types/estree-jsx" "^1.0.0" + "@types/hast" "^3.0.0" + "@types/mdx" "^2.0.0" + collapse-white-space "^2.0.0" + devlop "^1.0.0" + estree-util-is-identifier-name "^3.0.0" + estree-util-scope "^1.0.0" + estree-walker "^3.0.0" + hast-util-to-jsx-runtime "^2.0.0" + markdown-extensions "^2.0.0" + recma-build-jsx "^1.0.0" + recma-jsx "^1.0.0" + recma-stringify "^1.0.0" + rehype-recma "^1.0.0" + remark-mdx "^3.0.0" + remark-parse "^11.0.0" + remark-rehype "^11.0.0" + source-map "^0.7.0" + unified "^11.0.0" + unist-util-position-from-estree "^2.0.0" + unist-util-stringify-position "^4.0.0" + unist-util-visit "^5.0.0" + vfile "^6.0.0" + +"@mdx-js/react@^3.0.0": + version "3.1.0" + resolved "https://registry.yarnpkg.com/@mdx-js/react/-/react-3.1.0.tgz#c4522e335b3897b9a845db1dbdd2f966ae8fb0ed" + integrity sha512-QjHtSaoameoalGnKDT3FoIl4+9RwyTmo9ZJGBdLOks/YOiWHoRDI3PUwEzOE7kEmGcV3AFcp9K6dYu9rEuKLAQ== + dependencies: + "@types/mdx" "^2.0.0" "@nodelib/fs.scandir@2.1.5": version "2.1.5" @@ -1809,21 +2267,42 @@ "@nodelib/fs.scandir" "2.1.5" fastq "^1.6.0" -"@polka/url@^1.0.0-next.20": - version "1.0.0-next.21" - resolved "https://registry.npmjs.org/@polka/url/-/url-1.0.0-next.21.tgz" - integrity sha512-a5Sab1C4/icpTZVzZc5Ghpz88yQtGOyNqYXcZgOssB2uuAr+wF/MvN6bgtW32q7HHrvBki+BsZ0OuNv6EV3K9g== +"@pnpm/config.env-replace@^1.1.0": + version "1.1.0" + resolved "https://registry.yarnpkg.com/@pnpm/config.env-replace/-/config.env-replace-1.1.0.tgz#ab29da53df41e8948a00f2433f085f54de8b3a4c" + integrity sha512-htyl8TWnKL7K/ESFa1oW2UB5lVDxuF5DpM7tBi6Hu2LNL3mWkIzNLG6N4zoCUP1lCKNxWy/3iu8mS8MvToGd6w== -"@sideway/address@^4.1.3": - version "4.1.4" - resolved "https://registry.npmjs.org/@sideway/address/-/address-4.1.4.tgz" - integrity sha512-7vwq+rOHVWjyXxVlR76Agnvhy8I9rpzjosTESvmhNeXOXdZZB15Fl+TI9x1SiHZH5Jv2wTGduSxFDIaq0m3DUw== +"@pnpm/network.ca-file@^1.0.1": + version "1.0.2" + resolved "https://registry.yarnpkg.com/@pnpm/network.ca-file/-/network.ca-file-1.0.2.tgz#2ab05e09c1af0cdf2fcf5035bea1484e222f7983" + integrity sha512-YcPQ8a0jwYU9bTdJDpXjMi7Brhkr1mXsXrUJvjqM2mQDgkRiz8jFaQGOdaLxgjtUfQgZhKy/O3cG/YwmgKaxLA== + dependencies: + graceful-fs "4.2.10" + +"@pnpm/npm-conf@^2.1.0": + version "2.3.1" + resolved "https://registry.yarnpkg.com/@pnpm/npm-conf/-/npm-conf-2.3.1.tgz#bb375a571a0bd63ab0a23bece33033c683e9b6b0" + integrity sha512-c83qWb22rNRuB0UaVCI0uRPNRr8Z0FWnEIvT47jiHAmOIUHbBOg5XvV7pM5x+rKn9HRpjxquDbXYSXr3fAKFcw== + dependencies: + "@pnpm/config.env-replace" "^1.1.0" + "@pnpm/network.ca-file" "^1.0.1" + config-chain "^1.1.11" + +"@polka/url@^1.0.0-next.24": + version "1.0.0-next.28" + resolved "https://registry.yarnpkg.com/@polka/url/-/url-1.0.0-next.28.tgz#d45e01c4a56f143ee69c54dd6b12eade9e270a73" + integrity sha512-8LduaNlMZGwdZ6qWrKlfa+2M4gahzFkprZiAt2TF8uS0qQgBizKXpXURqvTJ4WtmupWxaLqjRb2UCTe72mu+Aw== + +"@sideway/address@^4.1.5": + version "4.1.5" + resolved "https://registry.yarnpkg.com/@sideway/address/-/address-4.1.5.tgz#4bc149a0076623ced99ca8208ba780d65a99b9d5" + integrity sha512-IqO/DUQHUkPeixNQ8n0JA6102hT9CmaljNTPmQ1u8MEhBo/R4Q8eKLN/vGZxuebwOroDB4cbpjheD4+/sKFK4Q== dependencies: "@hapi/hoek" "^9.0.0" -"@sideway/formula@^3.0.0": +"@sideway/formula@^3.0.1": version "3.0.1" - resolved "https://registry.npmjs.org/@sideway/formula/-/formula-3.0.1.tgz" + resolved "https://registry.yarnpkg.com/@sideway/formula/-/formula-3.0.1.tgz#80fcbcbaf7ce031e0ef2dd29b1bfc7c3f583611f" integrity sha512-/poHZJJVjx3L+zVD6g9KgHfYnb443oi7wLu/XKojDviHy6HOEOA6z1Trk5aR1dGcmPenJEgb2sK2I80LeS3MIg== "@sideway/pinpoint@^2.0.0": @@ -1831,143 +2310,155 @@ resolved "https://registry.npmjs.org/@sideway/pinpoint/-/pinpoint-2.0.0.tgz" integrity sha512-RNiOoTPkptFtSVzQevY/yWtZwf/RxyVnPy/OcA9HBM3MlGDnBEYL5B41H0MTn0Uec8Hi+2qUtTfG2WWZBmMejQ== -"@sinclair/typebox@^0.25.16": - version "0.25.21" - resolved "https://registry.npmjs.org/@sinclair/typebox/-/typebox-0.25.21.tgz" - integrity sha512-gFukHN4t8K4+wVC+ECqeqwzBDeFeTzBXroBTqE6vcWrQGbEUpHO7LYdG0f4xnvYq4VOEwITSlHlp0JBAIFMS/g== +"@sinclair/typebox@^0.27.8": + version "0.27.8" + resolved "https://registry.yarnpkg.com/@sinclair/typebox/-/typebox-0.27.8.tgz#6667fac16c436b5434a387a34dedb013198f6e6e" + integrity sha512-+Fj43pSMwJs4KRrH/938Uf+uAELIgVBmQzg/q1YG10djyfA3TnrU8N8XzqCh/okZdszqBQTZf96idMfE5lnwTA== -"@sindresorhus/is@^0.14.0": - version "0.14.0" - resolved "https://registry.npmjs.org/@sindresorhus/is/-/is-0.14.0.tgz" - integrity sha512-9NET910DNaIPngYnLLPeg+Ogzqsi9uM4mSboU5y6p8S5DzMTVEsJZrawi+BoDNUVBa2DhJqQYUFvMDfgU062LQ== +"@sindresorhus/is@^4.6.0": + version "4.6.0" + resolved "https://registry.yarnpkg.com/@sindresorhus/is/-/is-4.6.0.tgz#3c7c9c46e678feefe7a2e5bb609d3dbd665ffb3f" + integrity sha512-t09vSN3MdfsyCHoFcTRCH/iUtG7OJ0CsjzB8cjAmKc/va/kIgeDI/TxsigdncE/4be734m0cvIYwNaV4i2XqAw== -"@slorber/static-site-generator-webpack-plugin@^4.0.7": - version "4.0.7" - resolved "https://registry.npmjs.org/@slorber/static-site-generator-webpack-plugin/-/static-site-generator-webpack-plugin-4.0.7.tgz" - integrity sha512-Ug7x6z5lwrz0WqdnNFOMYrDQNTPAprvHLSh6+/fmml3qUiz6l5eq+2MzLKWtn/q5K5NpSiFsZTP/fck/3vjSxA== +"@sindresorhus/is@^5.2.0": + version "5.6.0" + resolved "https://registry.yarnpkg.com/@sindresorhus/is/-/is-5.6.0.tgz#41dd6093d34652cddb5d5bdeee04eafc33826668" + integrity sha512-TV7t8GKYaJWsn00tFDqBw8+Uqmr8A0fRU1tvTQhyZzGv0sJCGRQL3JGMI3ucuKo3XIZdUP+Lx7/gh2t3lewy7g== + +"@slorber/remark-comment@^1.0.0": + version "1.0.0" + resolved "https://registry.yarnpkg.com/@slorber/remark-comment/-/remark-comment-1.0.0.tgz#2a020b3f4579c89dec0361673206c28d67e08f5a" + integrity sha512-RCE24n7jsOj1M0UPvIQCHTe7fI0sFL4S2nwKVWwHyVr/wI/H8GosgsJGyhnsZoGFnD/P2hLf1mSbrrgSLN93NA== dependencies: - eval "^0.1.8" - p-map "^4.0.0" - webpack-sources "^3.2.2" + micromark-factory-space "^1.0.0" + micromark-util-character "^1.1.0" + micromark-util-symbol "^1.0.1" -"@svgr/babel-plugin-add-jsx-attribute@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/babel-plugin-add-jsx-attribute/-/babel-plugin-add-jsx-attribute-6.5.1.tgz" - integrity sha512-9PYGcXrAxitycIjRmZB+Q0JaN07GZIWaTBIGQzfaZv+qr1n8X1XUEJ5rZ/vx6OVD9RRYlrNnXWExQXcmZeD/BQ== +"@svgr/babel-plugin-add-jsx-attribute@8.0.0": + version "8.0.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-add-jsx-attribute/-/babel-plugin-add-jsx-attribute-8.0.0.tgz#4001f5d5dd87fa13303e36ee106e3ff3a7eb8b22" + integrity sha512-b9MIk7yhdS1pMCZM8VeNfUlSKVRhsHZNMl5O9SfaX0l0t5wjdgu4IDzGB8bpnGBBOjGST3rRFVsaaEtI4W6f7g== -"@svgr/babel-plugin-remove-jsx-attribute@*": - version "6.5.0" - resolved "https://registry.npmjs.org/@svgr/babel-plugin-remove-jsx-attribute/-/babel-plugin-remove-jsx-attribute-6.5.0.tgz" - integrity sha512-8zYdkym7qNyfXpWvu4yq46k41pyNM9SOstoWhKlm+IfdCE1DdnRKeMUPsWIEO/DEkaWxJ8T9esNdG3QwQ93jBA== +"@svgr/babel-plugin-remove-jsx-attribute@8.0.0": + version "8.0.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-remove-jsx-attribute/-/babel-plugin-remove-jsx-attribute-8.0.0.tgz#69177f7937233caca3a1afb051906698f2f59186" + integrity sha512-BcCkm/STipKvbCl6b7QFrMh/vx00vIP63k2eM66MfHJzPr6O2U0jYEViXkHJWqXqQYjdeA9cuCl5KWmlwjDvbA== -"@svgr/babel-plugin-remove-jsx-empty-expression@*": - version "6.5.0" - resolved "https://registry.npmjs.org/@svgr/babel-plugin-remove-jsx-empty-expression/-/babel-plugin-remove-jsx-empty-expression-6.5.0.tgz" - integrity sha512-NFdxMq3xA42Kb1UbzCVxplUc0iqSyM9X8kopImvFnB+uSDdzIHOdbs1op8ofAvVRtbg4oZiyRl3fTYeKcOe9Iw== - -"@svgr/babel-plugin-replace-jsx-attribute-value@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/babel-plugin-replace-jsx-attribute-value/-/babel-plugin-replace-jsx-attribute-value-6.5.1.tgz" - integrity sha512-8DPaVVE3fd5JKuIC29dqyMB54sA6mfgki2H2+swh+zNJoynC8pMPzOkidqHOSc6Wj032fhl8Z0TVn1GiPpAiJg== - -"@svgr/babel-plugin-svg-dynamic-title@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/babel-plugin-svg-dynamic-title/-/babel-plugin-svg-dynamic-title-6.5.1.tgz" - integrity sha512-FwOEi0Il72iAzlkaHrlemVurgSQRDFbk0OC8dSvD5fSBPHltNh7JtLsxmZUhjYBZo2PpcU/RJvvi6Q0l7O7ogw== - -"@svgr/babel-plugin-svg-em-dimensions@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/babel-plugin-svg-em-dimensions/-/babel-plugin-svg-em-dimensions-6.5.1.tgz" - integrity sha512-gWGsiwjb4tw+ITOJ86ndY/DZZ6cuXMNE/SjcDRg+HLuCmwpcjOktwRF9WgAiycTqJD/QXqL2f8IzE2Rzh7aVXA== - -"@svgr/babel-plugin-transform-react-native-svg@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/babel-plugin-transform-react-native-svg/-/babel-plugin-transform-react-native-svg-6.5.1.tgz" - integrity sha512-2jT3nTayyYP7kI6aGutkyfJ7UMGtuguD72OjeGLwVNyfPRBD8zQthlvL+fAbAKk5n9ZNcvFkp/b1lZ7VsYqVJg== - -"@svgr/babel-plugin-transform-svg-component@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/babel-plugin-transform-svg-component/-/babel-plugin-transform-svg-component-6.5.1.tgz" - integrity sha512-a1p6LF5Jt33O3rZoVRBqdxL350oge54iZWHNI6LJB5tQ7EelvD/Mb1mfBiZNAan0dt4i3VArkFRjA4iObuNykQ== - -"@svgr/babel-preset@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/babel-preset/-/babel-preset-6.5.1.tgz" - integrity sha512-6127fvO/FF2oi5EzSQOAjo1LE3OtNVh11R+/8FXa+mHx1ptAaS4cknIjnUA7e6j6fwGGJ17NzaTJFUwOV2zwCw== - dependencies: - "@svgr/babel-plugin-add-jsx-attribute" "^6.5.1" - "@svgr/babel-plugin-remove-jsx-attribute" "*" - "@svgr/babel-plugin-remove-jsx-empty-expression" "*" - "@svgr/babel-plugin-replace-jsx-attribute-value" "^6.5.1" - "@svgr/babel-plugin-svg-dynamic-title" "^6.5.1" - "@svgr/babel-plugin-svg-em-dimensions" "^6.5.1" - "@svgr/babel-plugin-transform-react-native-svg" "^6.5.1" - "@svgr/babel-plugin-transform-svg-component" "^6.5.1" - -"@svgr/core@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/core/-/core-6.5.1.tgz" - integrity sha512-/xdLSWxK5QkqG524ONSjvg3V/FkNyCv538OIBdQqPNaAta3AsXj/Bd2FbvR87yMbXO2hFSWiAe/Q6IkVPDw+mw== - dependencies: - "@babel/core" "^7.19.6" - "@svgr/babel-preset" "^6.5.1" - "@svgr/plugin-jsx" "^6.5.1" +"@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0": + version "8.0.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-remove-jsx-empty-expression/-/babel-plugin-remove-jsx-empty-expression-8.0.0.tgz#c2c48104cfd7dcd557f373b70a56e9e3bdae1d44" + integrity sha512-5BcGCBfBxB5+XSDSWnhTThfI9jcO5f0Ai2V24gZpG+wXF14BzwxxdDb4g6trdOux0rhibGs385BeFMSmxtS3uA== + +"@svgr/babel-plugin-replace-jsx-attribute-value@8.0.0": + version "8.0.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-replace-jsx-attribute-value/-/babel-plugin-replace-jsx-attribute-value-8.0.0.tgz#8fbb6b2e91fa26ac5d4aa25c6b6e4f20f9c0ae27" + integrity sha512-KVQ+PtIjb1BuYT3ht8M5KbzWBhdAjjUPdlMtpuw/VjT8coTrItWX6Qafl9+ji831JaJcu6PJNKCV0bp01lBNzQ== + +"@svgr/babel-plugin-svg-dynamic-title@8.0.0": + version "8.0.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-svg-dynamic-title/-/babel-plugin-svg-dynamic-title-8.0.0.tgz#1d5ba1d281363fc0f2f29a60d6d936f9bbc657b0" + integrity sha512-omNiKqwjNmOQJ2v6ge4SErBbkooV2aAWwaPFs2vUY7p7GhVkzRkJ00kILXQvRhA6miHnNpXv7MRnnSjdRjK8og== + +"@svgr/babel-plugin-svg-em-dimensions@8.0.0": + version "8.0.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-svg-em-dimensions/-/babel-plugin-svg-em-dimensions-8.0.0.tgz#35e08df300ea8b1d41cb8f62309c241b0369e501" + integrity sha512-mURHYnu6Iw3UBTbhGwE/vsngtCIbHE43xCRK7kCw4t01xyGqb2Pd+WXekRRoFOBIY29ZoOhUCTEweDMdrjfi9g== + +"@svgr/babel-plugin-transform-react-native-svg@8.1.0": + version "8.1.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-transform-react-native-svg/-/babel-plugin-transform-react-native-svg-8.1.0.tgz#90a8b63998b688b284f255c6a5248abd5b28d754" + integrity sha512-Tx8T58CHo+7nwJ+EhUwx3LfdNSG9R2OKfaIXXs5soiy5HtgoAEkDay9LIimLOcG8dJQH1wPZp/cnAv6S9CrR1Q== + +"@svgr/babel-plugin-transform-svg-component@8.0.0": + version "8.0.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-plugin-transform-svg-component/-/babel-plugin-transform-svg-component-8.0.0.tgz#013b4bfca88779711f0ed2739f3f7efcefcf4f7e" + integrity sha512-DFx8xa3cZXTdb/k3kfPeaixecQLgKh5NVBMwD0AQxOzcZawK4oo1Jh9LbrcACUivsCA7TLG8eeWgrDXjTMhRmw== + +"@svgr/babel-preset@8.1.0": + version "8.1.0" + resolved "https://registry.yarnpkg.com/@svgr/babel-preset/-/babel-preset-8.1.0.tgz#0e87119aecdf1c424840b9d4565b7137cabf9ece" + integrity sha512-7EYDbHE7MxHpv4sxvnVPngw5fuR6pw79SkcrILHJ/iMpuKySNCl5W1qcwPEpU+LgyRXOaAFgH0KhwD18wwg6ug== + dependencies: + "@svgr/babel-plugin-add-jsx-attribute" "8.0.0" + "@svgr/babel-plugin-remove-jsx-attribute" "8.0.0" + "@svgr/babel-plugin-remove-jsx-empty-expression" "8.0.0" + "@svgr/babel-plugin-replace-jsx-attribute-value" "8.0.0" + "@svgr/babel-plugin-svg-dynamic-title" "8.0.0" + "@svgr/babel-plugin-svg-em-dimensions" "8.0.0" + "@svgr/babel-plugin-transform-react-native-svg" "8.1.0" + "@svgr/babel-plugin-transform-svg-component" "8.0.0" + +"@svgr/core@8.1.0": + version "8.1.0" + resolved "https://registry.yarnpkg.com/@svgr/core/-/core-8.1.0.tgz#41146f9b40b1a10beaf5cc4f361a16a3c1885e88" + integrity sha512-8QqtOQT5ACVlmsvKOJNEaWmRPmcojMOzCz4Hs2BGG/toAp/K38LcsMRyLp349glq5AzJbCEeimEoxaX6v/fLrA== + dependencies: + "@babel/core" "^7.21.3" + "@svgr/babel-preset" "8.1.0" camelcase "^6.2.0" - cosmiconfig "^7.0.1" + cosmiconfig "^8.1.3" + snake-case "^3.0.4" -"@svgr/hast-util-to-babel-ast@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/hast-util-to-babel-ast/-/hast-util-to-babel-ast-6.5.1.tgz" - integrity sha512-1hnUxxjd83EAxbL4a0JDJoD3Dao3hmjvyvyEV8PzWmLK3B9m9NPlW7GKjFyoWE8nM7HnXzPcmmSyOW8yOddSXw== +"@svgr/hast-util-to-babel-ast@8.0.0": + version "8.0.0" + resolved "https://registry.yarnpkg.com/@svgr/hast-util-to-babel-ast/-/hast-util-to-babel-ast-8.0.0.tgz#6952fd9ce0f470e1aded293b792a2705faf4ffd4" + integrity sha512-EbDKwO9GpfWP4jN9sGdYwPBU0kdomaPIL2Eu4YwmgP+sJeXT+L7bMwJUBnhzfH8Q2qMBqZ4fJwpCyYsAN3mt2Q== dependencies: - "@babel/types" "^7.20.0" + "@babel/types" "^7.21.3" entities "^4.4.0" -"@svgr/plugin-jsx@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/plugin-jsx/-/plugin-jsx-6.5.1.tgz" - integrity sha512-+UdQxI3jgtSjCykNSlEMuy1jSRQlGC7pqBCPvkG/2dATdWo082zHTTK3uhnAju2/6XpE6B5mZ3z4Z8Ns01S8Gw== +"@svgr/plugin-jsx@8.1.0": + version "8.1.0" + resolved "https://registry.yarnpkg.com/@svgr/plugin-jsx/-/plugin-jsx-8.1.0.tgz#96969f04a24b58b174ee4cd974c60475acbd6928" + integrity sha512-0xiIyBsLlr8quN+WyuxooNW9RJ0Dpr8uOnH/xrCVO8GLUcwHISwj1AG0k+LFzteTkAA0GbX0kj9q6Dk70PTiPA== dependencies: - "@babel/core" "^7.19.6" - "@svgr/babel-preset" "^6.5.1" - "@svgr/hast-util-to-babel-ast" "^6.5.1" + "@babel/core" "^7.21.3" + "@svgr/babel-preset" "8.1.0" + "@svgr/hast-util-to-babel-ast" "8.0.0" svg-parser "^2.0.4" -"@svgr/plugin-svgo@^6.5.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/plugin-svgo/-/plugin-svgo-6.5.1.tgz" - integrity sha512-omvZKf8ixP9z6GWgwbtmP9qQMPX4ODXi+wzbVZgomNFsUIlHA1sf4fThdwTWSsZGgvGAG6yE+b/F5gWUkcZ/iQ== +"@svgr/plugin-svgo@8.1.0": + version "8.1.0" + resolved "https://registry.yarnpkg.com/@svgr/plugin-svgo/-/plugin-svgo-8.1.0.tgz#b115b7b967b564f89ac58feae89b88c3decd0f00" + integrity sha512-Ywtl837OGO9pTLIN/onoWLmDQ4zFUycI1g76vuKGEz6evR/ZTJlJuz3G/fIkb6OVBJ2g0o6CGJzaEjfmEo3AHA== dependencies: - cosmiconfig "^7.0.1" - deepmerge "^4.2.2" - svgo "^2.8.0" + cosmiconfig "^8.1.3" + deepmerge "^4.3.1" + svgo "^3.0.2" -"@svgr/webpack@^6.2.1": - version "6.5.1" - resolved "https://registry.npmjs.org/@svgr/webpack/-/webpack-6.5.1.tgz" - integrity sha512-cQ/AsnBkXPkEK8cLbv4Dm7JGXq2XrumKnL1dRpJD9rIO2fTIlJI9a1uCciYG1F2aUsox/hJQyNGbt3soDxSRkA== +"@svgr/webpack@^8.1.0": + version "8.1.0" + resolved "https://registry.yarnpkg.com/@svgr/webpack/-/webpack-8.1.0.tgz#16f1b5346f102f89fda6ec7338b96a701d8be0c2" + integrity sha512-LnhVjMWyMQV9ZmeEy26maJk+8HTIbd59cH4F2MJ439k9DqejRisfFNGAPvRYlKETuh9LrImlS8aKsBgKjMA8WA== dependencies: - "@babel/core" "^7.19.6" - "@babel/plugin-transform-react-constant-elements" "^7.18.12" - "@babel/preset-env" "^7.19.4" + "@babel/core" "^7.21.3" + "@babel/plugin-transform-react-constant-elements" "^7.21.3" + "@babel/preset-env" "^7.20.2" "@babel/preset-react" "^7.18.6" - "@babel/preset-typescript" "^7.18.6" - "@svgr/core" "^6.5.1" - "@svgr/plugin-jsx" "^6.5.1" - "@svgr/plugin-svgo" "^6.5.1" + "@babel/preset-typescript" "^7.21.0" + "@svgr/core" "8.1.0" + "@svgr/plugin-jsx" "8.1.0" + "@svgr/plugin-svgo" "8.1.0" -"@szmarczak/http-timer@^1.1.2": - version "1.1.2" - resolved "https://registry.npmjs.org/@szmarczak/http-timer/-/http-timer-1.1.2.tgz" - integrity sha512-XIB2XbzHTN6ieIjfIMV9hlVcfPU26s2vafYWQcZHWXHOxiaRZYEDKEwdl129Zyg50+foYV2jCgtrqSA6qNuNSA== +"@szmarczak/http-timer@^5.0.1": + version "5.0.1" + resolved "https://registry.yarnpkg.com/@szmarczak/http-timer/-/http-timer-5.0.1.tgz#c7c1bf1141cdd4751b0399c8fc7b8b664cd5be3a" + integrity sha512-+PmQX0PiAYPMeVYe237LJAYvOMYW1j2rH5YROyS3b4CTVJum34HfRvKvAzozHAQG0TnHNdUfY9nCeUyRAs//cw== dependencies: - defer-to-connect "^1.0.1" + defer-to-connect "^2.0.1" "@trysound/sax@0.2.0": version "0.2.0" resolved "https://registry.npmjs.org/@trysound/sax/-/sax-0.2.0.tgz" integrity sha512-L7z9BgrNEcYyUYtF+HaEfiS5ebkh9jXqbszz7pC0hRBPaatV0XjSD3+eHrpqFemQfgwiFF0QPIarnIihIDn7OA== +"@types/acorn@^4.0.0": + version "4.0.6" + resolved "https://registry.yarnpkg.com/@types/acorn/-/acorn-4.0.6.tgz#d61ca5480300ac41a7d973dd5b84d0a591154a22" + integrity sha512-veQTnWP+1D/xbxVrPC3zHnCZRjSrKfhbMUlEA43iMZLu7EsnTtkJklIuwrCPbOi8YkvDQAiW05VQQFvvz9oieQ== + dependencies: + "@types/estree" "*" + "@types/body-parser@*": version "1.19.2" resolved "https://registry.npmjs.org/@types/body-parser/-/body-parser-1.19.2.tgz" @@ -1998,9 +2489,39 @@ dependencies: "@types/node" "*" -"@types/estree@^1.0.5": +"@types/debug@^4.0.0": + version "4.1.12" + resolved "https://registry.yarnpkg.com/@types/debug/-/debug-4.1.12.tgz#a155f21690871953410df4b6b6f53187f0500917" + integrity sha512-vIChWdVG3LG1SMxEvI/AK+FWJthlrqlTu7fbrlywTkkaONwk/UAGaULXRlf8vkzFBLVm0zkMdCquhL5aOjhXPQ== + dependencies: + "@types/ms" "*" + +"@types/eslint-scope@^3.7.7": + version "3.7.7" + resolved "https://registry.yarnpkg.com/@types/eslint-scope/-/eslint-scope-3.7.7.tgz#3108bd5f18b0cdb277c867b3dd449c9ed7079ac5" + integrity sha512-MzMFlSLBqNF2gcHWO0G1vP/YQyfvrxZ0bF+u7mzUdZ1/xK4A4sru+nraZz5i3iEIk1l1uyicaDVTB4QbbEkAYg== + dependencies: + "@types/eslint" "*" + "@types/estree" "*" + +"@types/eslint@*": + version "9.6.1" + resolved "https://registry.yarnpkg.com/@types/eslint/-/eslint-9.6.1.tgz#d5795ad732ce81715f27f75da913004a56751584" + integrity sha512-FXx2pKgId/WyYo2jXw63kk7/+TY7u7AziEJxJAnSFzHlqTAS3Ync6SvgYAN/k4/PQpnnVuzoMuVnByKK2qp0ag== + dependencies: + "@types/estree" "*" + "@types/json-schema" "*" + +"@types/estree-jsx@^1.0.0": + version "1.0.5" + resolved "https://registry.yarnpkg.com/@types/estree-jsx/-/estree-jsx-1.0.5.tgz#858a88ea20f34fe65111f005a689fa1ebf70dc18" + integrity sha512-52CcUVNFyfb1A2ALocQw/Dd1BQFNmSdkuC3BkZ6iqhdMfQz7JWOFRuJFloOzjk+6WijU56m9oKXFAXc7o3Towg== + dependencies: + "@types/estree" "*" + +"@types/estree@*", "@types/estree@^1.0.0", "@types/estree@^1.0.5", "@types/estree@^1.0.6": version "1.0.6" - resolved "https://registry.npmjs.org/@types/estree/-/estree-1.0.6.tgz" + resolved "https://registry.yarnpkg.com/@types/estree/-/estree-1.0.6.tgz#628effeeae2064a1b4e79f78e81d87b7e5fc7b50" integrity sha512-AYnb1nQyY49te+VRAVgmzfcgjYS91mY5P0TKUDCLEM+gNnA+3T6rWITXRLYCpahpqSQbN5cE+gHpnPyXjHWxcw== "@types/express-serve-static-core@*", "@types/express-serve-static-core@^4.17.31": @@ -2034,10 +2555,15 @@ dependencies: "@types/node" "*" -"@types/hast@^2.0.0": - version "2.3.4" - resolved "https://registry.npmjs.org/@types/hast/-/hast-2.3.4.tgz" - integrity sha512-wLEm0QvaoawEDoTRwzTXp4b4jpwiJDvR5KMnFnVodm3scufTlBOWRD6N1OBf9TZMhjlNsSfcO5V+7AF4+Vy+9g== +"@types/gtag.js@^0.0.12": + version "0.0.12" + resolved "https://registry.yarnpkg.com/@types/gtag.js/-/gtag.js-0.0.12.tgz#095122edca896689bdfcdd73b057e23064d23572" + integrity sha512-YQV9bUsemkzG81Ea295/nF/5GijnD2Af7QhEofh7xu+kvCN6RdodgNwwGWXB5GMI3NoyvQo0odNctoH/qLMIpg== + +"@types/hast@^3.0.0": + version "3.0.4" + resolved "https://registry.yarnpkg.com/@types/hast/-/hast-3.0.4.tgz#1d6b39993b82cea6ad783945b0508c25903e15aa" + integrity sha512-WPs+bbQw5aCj+x6laNGWLH3wviHtoCv/P3+otBhbOhJgG8qtpdAMlTCxLtsTWA7LH1Oh/bFCHsBn0TPS5m30EQ== dependencies: "@types/unist" "*" @@ -2051,6 +2577,11 @@ resolved "https://registry.npmjs.org/@types/html-minifier-terser/-/html-minifier-terser-6.1.0.tgz" integrity sha512-oh/6byDPnL1zeNXFrDXFLyZjkr1MsBG667IM792caf1L2UPOOMf65NFzjUH/ltyfwjAGfs1rsX1eftK0jC/KIg== +"@types/http-cache-semantics@^4.0.2": + version "4.0.4" + resolved "https://registry.yarnpkg.com/@types/http-cache-semantics/-/http-cache-semantics-4.0.4.tgz#b979ebad3919799c979b17c72621c0bc0a31c6c4" + integrity sha512-1m0bIFVc7eJWyve9S0RnuRgcQqF/Xd5QsUZAZeQFr1Q3/p9JWoQQEqmVy+DPTNpGXwhgIetAoYF8JSc33q29QA== + "@types/http-proxy@^1.17.8": version "1.17.9" resolved "https://registry.npmjs.org/@types/http-proxy/-/http-proxy-1.17.9.tgz" @@ -2077,6 +2608,11 @@ dependencies: "@types/istanbul-lib-report" "*" +"@types/json-schema@*": + version "7.0.15" + resolved "https://registry.yarnpkg.com/@types/json-schema/-/json-schema-7.0.15.tgz#596a1747233694d50f6ad8a7869fcb6f56cf5841" + integrity sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA== + "@types/json-schema@^7.0.4", "@types/json-schema@^7.0.5", "@types/json-schema@^7.0.8", "@types/json-schema@^7.0.9": version "7.0.11" resolved "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.11.tgz" @@ -2094,18 +2630,28 @@ resolved "https://registry.npmjs.org/@types/lodash/-/lodash-4.14.182.tgz" integrity sha512-/THyiqyQAP9AfARo4pF+aCGcyiQ94tX/Is2I7HofNRqoYLgN1PBoOWu2/zTA5zMxzP5EFutMtWtGAFRKUe961Q== -"@types/mdast@^3.0.0": - version "3.0.10" - resolved "https://registry.npmjs.org/@types/mdast/-/mdast-3.0.10.tgz" - integrity sha512-W864tg/Osz1+9f4lrGTZpCSO5/z4608eUp19tbozkq2HJK6i3z1kT0H9tlADXuYIb1YYOBByU4Jsqkk75q48qA== +"@types/mdast@^4.0.0", "@types/mdast@^4.0.2": + version "4.0.4" + resolved "https://registry.yarnpkg.com/@types/mdast/-/mdast-4.0.4.tgz#7ccf72edd2f1aa7dd3437e180c64373585804dd6" + integrity sha512-kGaNbPh1k7AFzgpud/gMdvIm5xuECykRR+JnWKQno9TAXVa6WIVCGTPvYGekIDL4uwCZQSYbUxNBSb1aUo79oA== dependencies: "@types/unist" "*" +"@types/mdx@^2.0.0": + version "2.0.13" + resolved "https://registry.yarnpkg.com/@types/mdx/-/mdx-2.0.13.tgz#68f6877043d377092890ff5b298152b0a21671bd" + integrity sha512-+OWZQfAYyio6YkJb3HLxDrvnx6SWWDbC0zVPfBRzUk0/nqoDyf6dNxQi3eArPe8rJ473nobTMQ/8Zk+LxJ+Yuw== + "@types/mime@*": version "3.0.1" resolved "https://registry.npmjs.org/@types/mime/-/mime-3.0.1.tgz" integrity sha512-Y4XFY5VJAuw0FgAqPNd6NNoV44jbq9Bz2L7Rh/J6jLTiHBSBJa9fxqQIvkIld4GsoDOcCbvzOUAbLPsSKKg+uA== +"@types/ms@*": + version "0.7.34" + resolved "https://registry.yarnpkg.com/@types/ms/-/ms-0.7.34.tgz#10964ba0dee6ac4cd462e2795b6bebd407303433" + integrity sha512-nG96G3Wp6acyAgJqGasjODb+acrI7KltPiRxzHPXnP3NgI28bpQDRv53olbqGXbfcgF5aiiHmO3xpwEpS5Ld9g== + "@types/node@*": version "18.11.18" resolved "https://registry.npmjs.org/@types/node/-/node-18.11.18.tgz" @@ -2121,10 +2667,10 @@ resolved "https://registry.npmjs.org/@types/parse-json/-/parse-json-4.0.0.tgz" integrity sha512-//oorEZjL6sbPcKUaCdIGlIUeH26mgzimjBB77G6XRgnDl/L5wOnpyBGRe/Mmf5CVW3PwEBE1NjiMZ/ssFh4wA== -"@types/parse5@^5.0.0": - version "5.0.3" - resolved "https://registry.npmjs.org/@types/parse5/-/parse5-5.0.3.tgz" - integrity sha512-kUNnecmtkunAoQ3CnjmMkzNU/gtxG8guhi+Fk2U/kOpIKjIMKnXGp4IJCgQJrXSgMsWYimYG4TGjz/UzbGEBTw== +"@types/prismjs@^1.26.0": + version "1.26.5" + resolved "https://registry.yarnpkg.com/@types/prismjs/-/prismjs-1.26.5.tgz#72499abbb4c4ec9982446509d2f14fb8483869d6" + integrity sha512-AUZTa7hQ2KY5L7AmtSiqxlhWxb4ina0yd8hNbl4TWuqnv/pFP0nDMb3YrfSBf4hJVGLh2YEIBfKaBW/9UEl6IQ== "@types/prop-types@*": version "15.7.5" @@ -2141,7 +2687,7 @@ resolved "https://registry.npmjs.org/@types/range-parser/-/range-parser-1.2.4.tgz" integrity sha512-EEhsLsD6UsDM1yFhAvy0Cjr6VwmpMWqFBCb9w07wVugF7w9nfajxLuVmngTIpgS6svCnm6Vaw+MZhoDCKnOfsw== -"@types/react-router-config@*", "@types/react-router-config@^5.0.6": +"@types/react-router-config@*": version "5.0.6" resolved "https://registry.npmjs.org/@types/react-router-config/-/react-router-config-5.0.6.tgz" integrity sha512-db1mx37a1EJDf1XeX8jJN7R3PZABmJQXR8r28yUjVMFSjkmnQo6X6pOEEmNl+Tp2gYQOGPdYbFIipBtdElZ3Yg== @@ -2150,6 +2696,15 @@ "@types/react" "*" "@types/react-router" "*" +"@types/react-router-config@^5.0.7": + version "5.0.11" + resolved "https://registry.yarnpkg.com/@types/react-router-config/-/react-router-config-5.0.11.tgz#2761a23acc7905a66a94419ee40294a65aaa483a" + integrity sha512-WmSAg7WgqW7m4x8Mt4N6ZyKz0BubSj/2tVUMsAHp+Yd2AMwcSbeFq9WympT19p5heCFmF97R9eD5uUR/t4HEqw== + dependencies: + "@types/history" "^4.7.11" + "@types/react" "*" + "@types/react-router" "^5.1.0" + "@types/react-router-dom@*": version "5.3.3" resolved "https://registry.npmjs.org/@types/react-router-dom/-/react-router-dom-5.3.3.tgz" @@ -2159,7 +2714,7 @@ "@types/react" "*" "@types/react-router" "*" -"@types/react-router@*": +"@types/react-router@*", "@types/react-router@^5.1.0": version "5.1.20" resolved "https://registry.npmjs.org/@types/react-router/-/react-router-5.1.20.tgz" integrity sha512-jGjmu/ZqS7FjSH6owMcD5qpq19+1RS9DeVRqfl1FeBMxTDQAGwlMWOcs52NDoXaNKyG3d1cYQFMs9rCrb88o9Q== @@ -2220,15 +2775,20 @@ dependencies: "@types/node" "*" -"@types/unist@*", "@types/unist@^2.0.0", "@types/unist@^2.0.2", "@types/unist@^2.0.3": +"@types/unist@*", "@types/unist@^2.0.0": version "2.0.6" resolved "https://registry.npmjs.org/@types/unist/-/unist-2.0.6.tgz" integrity sha512-PBjIUxZHOuj0R15/xuwJYjFi+KZdNFrehocChv4g5hu6aFroHue8m0lBP0POdK2nKzbw0cgV1mws8+V/JAcEkQ== -"@types/ws@^8.5.1": - version "8.5.4" - resolved "https://registry.npmjs.org/@types/ws/-/ws-8.5.4.tgz" - integrity sha512-zdQDHKUgcX/zBc4GrwsE/7dVdAD8JR4EuiAXiiUhhfyIJXXb2+PrGshFyeXWQPMmmZ2XxgaqclgpIC7eTXc1mg== +"@types/unist@^3.0.0": + version "3.0.3" + resolved "https://registry.yarnpkg.com/@types/unist/-/unist-3.0.3.tgz#acaab0f919ce69cce629c2d4ed2eb4adc1b6c20c" + integrity sha512-ko/gIFJRv177XgZsZcBwnqJN5x/Gien8qNOn0D5bQU/zAzVf9Zt3BlcUiLqhV9y4ARk0GbT3tnUiPNgnTXzc/Q== + +"@types/ws@^8.5.5": + version "8.5.13" + resolved "https://registry.yarnpkg.com/@types/ws/-/ws-8.5.13.tgz#6414c280875e2691d0d1e080b05addbf5cb91e20" + integrity sha512-osM/gWBTPKgHV8XkTunnegTRIsvF6owmf5w+JtAfOw472dptdm0dlGv4xCt6GwQRcC2XVOvvRE/0bAoQcL2QkA== dependencies: "@types/node" "*" @@ -2249,9 +2809,14 @@ resolved "https://registry.npmjs.org/@types/yarnpkg__lockfile/-/yarnpkg__lockfile-1.1.5.tgz" integrity sha512-8NYnGOctzsI4W0ApsP/BIHD/LnxpJ6XaGf2AZmz4EyDYJMxtprN4279dLNI1CPZcwC9H18qYcaFv4bXi0wmokg== -"@webassemblyjs/ast@1.14.1", "@webassemblyjs/ast@^1.12.1": +"@ungap/structured-clone@^1.0.0": + version "1.2.1" + resolved "https://registry.yarnpkg.com/@ungap/structured-clone/-/structured-clone-1.2.1.tgz#28fa185f67daaf7b7a1a8c1d445132c5d979f8bd" + integrity sha512-fEzPV3hSkSMltkw152tJKNARhOupqbH96MZWyRjNaYZOMIzbrTeQDG+MTc6Mr2pgzFQzFxAfmhGDNP5QK++2ZA== + +"@webassemblyjs/ast@1.14.1", "@webassemblyjs/ast@^1.12.1", "@webassemblyjs/ast@^1.14.1": version "1.14.1" - resolved "https://registry.npmjs.org/@webassemblyjs/ast/-/ast-1.14.1.tgz" + resolved "https://registry.yarnpkg.com/@webassemblyjs/ast/-/ast-1.14.1.tgz#a9f6a07f2b03c95c8d38c4536a1fdfb521ff55b6" integrity sha512-nuBEDgQfm1ccRp/8bCQrx1frohyufl4JlbMMZ4P1wpeOfDhF6FQkxZJ1b/e+PLwr6X1Nhw6OLme5usuBWYBvuQ== dependencies: "@webassemblyjs/helper-numbers" "1.13.2" @@ -2315,9 +2880,9 @@ resolved "https://registry.npmjs.org/@webassemblyjs/utf8/-/utf8-1.13.2.tgz" integrity sha512-3NQWGjKTASY1xV5m7Hr0iPeXD9+RDobLll3T9d2AO+g3my8xy5peVyjSag4I50mR1bBSN/Ct12lo+R9tJk0NZQ== -"@webassemblyjs/wasm-edit@^1.12.1": +"@webassemblyjs/wasm-edit@^1.12.1", "@webassemblyjs/wasm-edit@^1.14.1": version "1.14.1" - resolved "https://registry.npmjs.org/@webassemblyjs/wasm-edit/-/wasm-edit-1.14.1.tgz" + resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-edit/-/wasm-edit-1.14.1.tgz#ac6689f502219b59198ddec42dcd496b1004d597" integrity sha512-RNJUIQH/J8iA/1NzlE4N7KtyZNHi3w7at7hDjvRNm5rcUXa00z1vRz3glZoULfJ5mpvYhLybmVcwcjGrC1pRrQ== dependencies: "@webassemblyjs/ast" "1.14.1" @@ -2350,7 +2915,7 @@ "@webassemblyjs/wasm-gen" "1.14.1" "@webassemblyjs/wasm-parser" "1.14.1" -"@webassemblyjs/wasm-parser@1.14.1", "@webassemblyjs/wasm-parser@^1.12.1": +"@webassemblyjs/wasm-parser@1.14.1", "@webassemblyjs/wasm-parser@^1.12.1", "@webassemblyjs/wasm-parser@^1.14.1": version "1.14.1" resolved "https://registry.npmjs.org/@webassemblyjs/wasm-parser/-/wasm-parser-1.14.1.tgz" integrity sha512-JLBl+KZ0R5qB7mCnud/yyX08jWFw5MsoalJ1pQ4EdFlgj9VdXKGuENGsiCIjegI1W7p91rUlcB/LB5yRJKNTcQ== @@ -2398,12 +2963,17 @@ acorn-import-attributes@^1.9.5: resolved "https://registry.npmjs.org/acorn-import-attributes/-/acorn-import-attributes-1.9.5.tgz" integrity sha512-n02Vykv5uA3eHGM/Z2dQrcD56kL8TyDb2p1+0P83PClMnC/nc+anbQRhIOWnSq4Ke/KvDPrY3C9hDtC/A3eHnQ== +acorn-jsx@^5.0.0: + version "5.3.2" + resolved "https://registry.yarnpkg.com/acorn-jsx/-/acorn-jsx-5.3.2.tgz#7ed5bb55908b3b2f1bc55c6af1653bada7f07937" + integrity sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ== + acorn-walk@^8.0.0: version "8.2.0" resolved "https://registry.npmjs.org/acorn-walk/-/acorn-walk-8.2.0.tgz" integrity sha512-k+iyHEuPgSw6SbuDpGQM+06HQUa04DZ3o+F6CSzXMvvI5KMvnaEqXe+YVe555R9nn6GPt404fos4wcgpw12SDA== -acorn@^8.0.4, acorn@^8.7.1, acorn@^8.8.2: +acorn@^8.0.0, acorn@^8.0.4, acorn@^8.14.0, acorn@^8.7.1, acorn@^8.8.2: version "8.14.0" resolved "https://registry.npmjs.org/acorn/-/acorn-8.14.0.tgz" integrity sha512-cl669nCJTZBsL97OF4kUQm5g5hC2uihk0NxY3WENAC0TYdILVkAyHymAntgxGkl7K+t0cXIrH5siy5S4XkFycA== @@ -2433,14 +3003,14 @@ ajv-keywords@^3.4.1, ajv-keywords@^3.5.2: resolved "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-3.5.2.tgz" integrity sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ== -ajv-keywords@^5.0.0: +ajv-keywords@^5.0.0, ajv-keywords@^5.1.0: version "5.1.0" resolved "https://registry.npmjs.org/ajv-keywords/-/ajv-keywords-5.1.0.tgz" integrity sha512-YCS/JNFAUyr5vAuhk1DWm1CBxRHW9LbJ2ozWeemrIqpbsqKjHVxYPyi5GC0rjZIT5JxJ3virVTS8wk4i/Z+krw== dependencies: fast-deep-equal "^3.1.3" -ajv@^6.12.2, ajv@^6.12.4, ajv@^6.12.5: +ajv@^6.12.2, ajv@^6.12.5: version "6.12.6" resolved "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz" integrity sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g== @@ -2460,40 +3030,77 @@ ajv@^8.0.0, ajv@^8.8.0: require-from-string "^2.0.2" uri-js "^4.2.2" -algoliasearch-helper@^3.10.0: - version "3.11.3" - resolved "https://registry.npmjs.org/algoliasearch-helper/-/algoliasearch-helper-3.11.3.tgz" - integrity sha512-TbaEvLwiuGygHQIB8y+OsJKQQ40+JKUua5B91X66tMUHyyhbNHvqyr0lqd3wCoyKx7WybyQrC0WJvzoIeh24Aw== +ajv@^8.9.0: + version "8.17.1" + resolved "https://registry.yarnpkg.com/ajv/-/ajv-8.17.1.tgz#37d9a5c776af6bc92d7f4f9510eba4c0a60d11a6" + integrity sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g== + dependencies: + fast-deep-equal "^3.1.3" + fast-uri "^3.0.1" + json-schema-traverse "^1.0.0" + require-from-string "^2.0.2" + +algoliasearch-helper@^3.13.3: + version "3.22.6" + resolved "https://registry.yarnpkg.com/algoliasearch-helper/-/algoliasearch-helper-3.22.6.tgz#6a31c67d277a32f3f7ae1b8a6e57ca73f1e1a0b0" + integrity sha512-F2gSb43QHyvZmvH/2hxIjbk/uFdO2MguQYTFP7J+RowMW1csjIODMobEnpLI8nbLQuzZnGZdIxl5Bpy1k9+CFQ== dependencies: "@algolia/events" "^4.0.1" -algoliasearch@^4.0.0, algoliasearch@^4.13.1: - version "4.14.3" - resolved "https://registry.npmjs.org/algoliasearch/-/algoliasearch-4.14.3.tgz" - integrity sha512-GZTEuxzfWbP/vr7ZJfGzIl8fOsoxN916Z6FY2Egc9q2TmZ6hvq5KfAxY89pPW01oW/2HDEKA8d30f9iAH9eXYg== - dependencies: - "@algolia/cache-browser-local-storage" "4.14.3" - "@algolia/cache-common" "4.14.3" - "@algolia/cache-in-memory" "4.14.3" - "@algolia/client-account" "4.14.3" - "@algolia/client-analytics" "4.14.3" - "@algolia/client-common" "4.14.3" - "@algolia/client-personalization" "4.14.3" - "@algolia/client-search" "4.14.3" - "@algolia/logger-common" "4.14.3" - "@algolia/logger-console" "4.14.3" - "@algolia/requester-browser-xhr" "4.14.3" - "@algolia/requester-common" "4.14.3" - "@algolia/requester-node-http" "4.14.3" - "@algolia/transporter" "4.14.3" - -ansi-align@^3.0.0, ansi-align@^3.0.1: +algoliasearch@^4.18.0: + version "4.24.0" + resolved "https://registry.yarnpkg.com/algoliasearch/-/algoliasearch-4.24.0.tgz#b953b3e2309ef8f25da9de311b95b994ac918275" + integrity sha512-bf0QV/9jVejssFBmz2HQLxUadxk574t4iwjCKp5E7NBzwKkrDEhKPISIIjAU/p6K5qDx3qoeh4+26zWN1jmw3g== + dependencies: + "@algolia/cache-browser-local-storage" "4.24.0" + "@algolia/cache-common" "4.24.0" + "@algolia/cache-in-memory" "4.24.0" + "@algolia/client-account" "4.24.0" + "@algolia/client-analytics" "4.24.0" + "@algolia/client-common" "4.24.0" + "@algolia/client-personalization" "4.24.0" + "@algolia/client-search" "4.24.0" + "@algolia/logger-common" "4.24.0" + "@algolia/logger-console" "4.24.0" + "@algolia/recommend" "4.24.0" + "@algolia/requester-browser-xhr" "4.24.0" + "@algolia/requester-common" "4.24.0" + "@algolia/requester-node-http" "4.24.0" + "@algolia/transporter" "4.24.0" + +algoliasearch@^5.14.2: + version "5.18.0" + resolved "https://registry.yarnpkg.com/algoliasearch/-/algoliasearch-5.18.0.tgz#2023232151f2ee9a580ea84d4a36676871979ce4" + integrity sha512-/tfpK2A4FpS0o+S78o3YSdlqXr0MavJIDlFK3XZrlXLy7vaRXJvW5jYg3v5e/wCaF8y0IpMjkYLhoV6QqfpOgw== + dependencies: + "@algolia/client-abtesting" "5.18.0" + "@algolia/client-analytics" "5.18.0" + "@algolia/client-common" "5.18.0" + "@algolia/client-insights" "5.18.0" + "@algolia/client-personalization" "5.18.0" + "@algolia/client-query-suggestions" "5.18.0" + "@algolia/client-search" "5.18.0" + "@algolia/ingestion" "1.18.0" + "@algolia/monitoring" "1.18.0" + "@algolia/recommend" "5.18.0" + "@algolia/requester-browser-xhr" "5.18.0" + "@algolia/requester-fetch" "5.18.0" + "@algolia/requester-node-http" "5.18.0" + +ansi-align@^3.0.1: version "3.0.1" resolved "https://registry.npmjs.org/ansi-align/-/ansi-align-3.0.1.tgz" integrity sha512-IOfwwBF5iczOjp/WeY4YxyjqAFMQoZufdQWDd19SEExbVLNXqvpzSJ/M7Za4/sCPmQ0+GRquoA7bGcINcxew6w== dependencies: string-width "^4.1.0" +ansi-escapes@^4.3.2: + version "4.3.2" + resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-4.3.2.tgz#6b2291d1db7d98b6521d5f1efa42d0f3a9feb65e" + integrity sha512-gKXj5ALrKWQLsYG9jlTRmR/xKluxHV+Z9QEwNIgCfM1/uwPMCuzVVnh5mwTd+OuBZcwSIMbqssNWRm1lE51QaQ== + dependencies: + type-fest "^0.21.3" + ansi-html-community@^0.0.8: version "0.0.8" resolved "https://registry.npmjs.org/ansi-html-community/-/ansi-html-community-0.0.8.tgz" @@ -2573,52 +3180,35 @@ array-union@^2.1.0: resolved "https://registry.npmjs.org/array-union/-/array-union-2.1.0.tgz" integrity sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw== -asap@~2.0.3: - version "2.0.6" - resolved "https://registry.npmjs.org/asap/-/asap-2.0.6.tgz" - integrity sha512-BSHWgDSAiKs50o2Re8ppvp3seVHXSRM44cdSsT9FfNEUUZLOGWVCsiWaRPWM1Znn+mqZ1OfVZ3z3DWEzSp7hRA== +astring@^1.8.0: + version "1.9.0" + resolved "https://registry.yarnpkg.com/astring/-/astring-1.9.0.tgz#cc73e6062a7eb03e7d19c22d8b0b3451fd9bfeef" + integrity sha512-LElXdjswlqjWrPpJFg1Fx4wpkOCxj1TDHlSV4PlaRxHGWko024xICaa97ZkMfs6DRKlCguiAI+rbXv5GWwXIkg== at-least-node@^1.0.0: version "1.0.0" resolved "https://registry.npmjs.org/at-least-node/-/at-least-node-1.0.0.tgz" integrity sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg== -autoprefixer@^10.4.12, autoprefixer@^10.4.7: - version "10.4.13" - resolved "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.4.13.tgz" - integrity sha512-49vKpMqcZYsJjwotvt4+h/BCjJVnhGwcLpDt5xkcaOG3eLrG/HUYLagrihYsQ+qrIBgIzX1Rw7a6L8I/ZA1Atg== +autoprefixer@^10.4.19: + version "10.4.20" + resolved "https://registry.yarnpkg.com/autoprefixer/-/autoprefixer-10.4.20.tgz#5caec14d43976ef42e32dcb4bd62878e96be5b3b" + integrity sha512-XY25y5xSv/wEoqzDyXXME4AFfkZI0P23z6Fs3YgymDnKJkCGOnkL0iTxCa85UTqaSgfcqyf3UA6+c7wUvx/16g== dependencies: - browserslist "^4.21.4" - caniuse-lite "^1.0.30001426" - fraction.js "^4.2.0" + browserslist "^4.23.3" + caniuse-lite "^1.0.30001646" + fraction.js "^4.3.7" normalize-range "^0.1.2" - picocolors "^1.0.0" + picocolors "^1.0.1" postcss-value-parser "^4.2.0" -axios@^0.25.0: - version "0.25.0" - resolved "https://registry.npmjs.org/axios/-/axios-0.25.0.tgz" - integrity sha512-cD8FOb0tRH3uuEe6+evtAbgJtfxr7ly3fQjYcMcuPlgkwVS9xboaVIpcDV+cYQe+yGykgwZCs1pzjntcGa6l5g== +babel-loader@^9.2.1: + version "9.2.1" + resolved "https://registry.yarnpkg.com/babel-loader/-/babel-loader-9.2.1.tgz#04c7835db16c246dd19ba0914418f3937797587b" + integrity sha512-fqe8naHt46e0yIdkjUZYqddSXfej3AHajX+CSO5X7oy0EmPc6o5Xh+RClNoHjnieWz9AW4kZxW9yyFMhVB1QLA== dependencies: - follow-redirects "^1.14.7" - -babel-loader@^8.2.5: - version "8.3.0" - resolved "https://registry.npmjs.org/babel-loader/-/babel-loader-8.3.0.tgz" - integrity sha512-H8SvsMF+m9t15HNLMipppzkC+Y2Yq+v3SonZyU70RBL/h1gxPkH08Ot8pEE9Z4Kd+czyWJClmFS8qzIP9OZ04Q== - dependencies: - find-cache-dir "^3.3.1" - loader-utils "^2.0.0" - make-dir "^3.1.0" - schema-utils "^2.6.5" - -babel-plugin-apply-mdx-type-prop@1.6.22: - version "1.6.22" - resolved "https://registry.npmjs.org/babel-plugin-apply-mdx-type-prop/-/babel-plugin-apply-mdx-type-prop-1.6.22.tgz" - integrity sha512-VefL+8o+F/DfK24lPZMtJctrCVOfgbqLAGZSkxwhazQv4VxPg3Za/i40fu22KR2m8eEda+IfSOlPLUSIiLcnCQ== - dependencies: - "@babel/helper-plugin-utils" "7.10.4" - "@mdx-js/util" "1.6.22" + find-cache-dir "^4.0.0" + schema-utils "^4.0.0" babel-plugin-dynamic-import-node@^2.3.3: version "2.3.3" @@ -2627,52 +3217,40 @@ babel-plugin-dynamic-import-node@^2.3.3: dependencies: object.assign "^4.1.0" -babel-plugin-extract-import-names@1.6.22: - version "1.6.22" - resolved "https://registry.npmjs.org/babel-plugin-extract-import-names/-/babel-plugin-extract-import-names-1.6.22.tgz" - integrity sha512-yJ9BsJaISua7d8zNT7oRG1ZLBJCIdZ4PZqmH8qa9N5AK01ifk3fnkc98AXhtzE7UkfCsEumvoQWgoYLhOnJ7jQ== - dependencies: - "@babel/helper-plugin-utils" "7.10.4" - -babel-plugin-polyfill-corejs2@^0.3.3: - version "0.3.3" - resolved "https://registry.npmjs.org/babel-plugin-polyfill-corejs2/-/babel-plugin-polyfill-corejs2-0.3.3.tgz" - integrity sha512-8hOdmFYFSZhqg2C/JgLUQ+t52o5nirNwaWM2B9LWteozwIvM14VSwdsCAUET10qT+kmySAlseadmfeeSWFCy+Q== +babel-plugin-polyfill-corejs2@^0.4.10: + version "0.4.12" + resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-corejs2/-/babel-plugin-polyfill-corejs2-0.4.12.tgz#ca55bbec8ab0edeeef3d7b8ffd75322e210879a9" + integrity sha512-CPWT6BwvhrTO2d8QVorhTCQw9Y43zOu7G9HigcfxvepOU6b8o3tcWad6oVgZIsZCTt42FFv97aA7ZJsbM4+8og== dependencies: - "@babel/compat-data" "^7.17.7" - "@babel/helper-define-polyfill-provider" "^0.3.3" - semver "^6.1.1" + "@babel/compat-data" "^7.22.6" + "@babel/helper-define-polyfill-provider" "^0.6.3" + semver "^6.3.1" -babel-plugin-polyfill-corejs3@^0.6.0: - version "0.6.0" - resolved "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.6.0.tgz" - integrity sha512-+eHqR6OPcBhJOGgsIar7xoAB1GcSwVUA3XjAd7HJNzOXT4wv6/H7KIdA/Nc60cvUlDbKApmqNvD1B1bzOt4nyA== +babel-plugin-polyfill-corejs3@^0.10.6: + version "0.10.6" + resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.10.6.tgz#2deda57caef50f59c525aeb4964d3b2f867710c7" + integrity sha512-b37+KR2i/khY5sKmWNVQAnitvquQbNdWy6lJdsr0kmquCKEEUgMKK4SboVM3HtfnZilfjr4MMQ7vY58FVWDtIA== dependencies: - "@babel/helper-define-polyfill-provider" "^0.3.3" - core-js-compat "^3.25.1" + "@babel/helper-define-polyfill-provider" "^0.6.2" + core-js-compat "^3.38.0" -babel-plugin-polyfill-regenerator@^0.4.1: - version "0.4.1" - resolved "https://registry.npmjs.org/babel-plugin-polyfill-regenerator/-/babel-plugin-polyfill-regenerator-0.4.1.tgz" - integrity sha512-NtQGmyQDXjQqQ+IzRkBVwEOz9lQ4zxAQZgoAYEtU9dJjnl1Oc98qnN7jcp+bE7O7aYzVpavXE3/VKXNzUbh7aw== +babel-plugin-polyfill-regenerator@^0.6.1: + version "0.6.3" + resolved "https://registry.yarnpkg.com/babel-plugin-polyfill-regenerator/-/babel-plugin-polyfill-regenerator-0.6.3.tgz#abeb1f3f1c762eace37587f42548b08b57789bc8" + integrity sha512-LiWSbl4CRSIa5x/JAU6jZiG9eit9w6mz+yVMFwDE83LAWvt0AfGBoZ7HS/mkhrKuh2ZlzfVZYKoLjXdqw6Yt7Q== dependencies: - "@babel/helper-define-polyfill-provider" "^0.3.3" + "@babel/helper-define-polyfill-provider" "^0.6.3" -bail@^1.0.0: - version "1.0.5" - resolved "https://registry.npmjs.org/bail/-/bail-1.0.5.tgz" - integrity sha512-xFbRxM1tahm08yHBP16MMjVUAvDaBMD38zsM9EMAUN61omwLmKlOpB/Zku5QkjZ8TZ4vn53pj+t518cH0S03RQ== +bail@^2.0.0: + version "2.0.2" + resolved "https://registry.yarnpkg.com/bail/-/bail-2.0.2.tgz#d26f5cd8fe5d6f832a31517b9f7c356040ba6d5d" + integrity sha512-0xO6mYd7JB2YesxDKplafRpsiOzPt9V02ddPCLbY1xYGPOX24NTyN50qnUxgCPcSoYMhKpAuBTjQoRZCAkUDRw== balanced-match@^1.0.0: version "1.0.2" resolved "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz" integrity sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw== -base16@^1.0.0: - version "1.0.0" - resolved "https://registry.npmjs.org/base16/-/base16-1.0.0.tgz" - integrity sha512-pNdYkNPiJUnEhnfXV56+sQy8+AaPcG3POZAUnwr4EeqCUZFz4u2PePbo3e5Gj4ziYPCWGUZT9RHisvJKnwFuBQ== - bash-glob@^2.0.0: version "2.0.0" resolved "https://registry.npmjs.org/bash-glob/-/bash-glob-2.0.0.tgz" @@ -2742,20 +3320,6 @@ boolbase@^1.0.0: resolved "https://registry.npmjs.org/boolbase/-/boolbase-1.0.0.tgz" integrity sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww== -boxen@^5.0.0: - version "5.1.2" - resolved "https://registry.npmjs.org/boxen/-/boxen-5.1.2.tgz" - integrity sha512-9gYgQKXx+1nP8mP7CzFyaUARhg7D3n1dF/FnErWmu9l6JvGpNUN278h0aSb+QjoiKSWG+iZ3uHrcqk0qrY9RQQ== - dependencies: - ansi-align "^3.0.0" - camelcase "^6.2.0" - chalk "^4.1.0" - cli-boxes "^2.2.1" - string-width "^4.2.2" - type-fest "^0.20.2" - widest-line "^3.1.0" - wrap-ansi "^7.0.0" - boxen@^6.2.1: version "6.2.1" resolved "https://registry.npmjs.org/boxen/-/boxen-6.2.1.tgz" @@ -2770,6 +3334,20 @@ boxen@^6.2.1: widest-line "^4.0.1" wrap-ansi "^8.0.1" +boxen@^7.0.0: + version "7.1.1" + resolved "https://registry.yarnpkg.com/boxen/-/boxen-7.1.1.tgz#f9ba525413c2fec9cdb88987d835c4f7cad9c8f4" + integrity sha512-2hCgjEmP8YLWQ130n2FerGv7rYpfBmnmp9Uy2Le1vge6X3gZIfSmEzP5QTDElFxcvVcXlEn8Aq6MU/PZygIOog== + dependencies: + ansi-align "^3.0.1" + camelcase "^7.0.1" + chalk "^5.2.0" + cli-boxes "^3.0.0" + string-width "^5.1.2" + type-fest "^2.13.0" + widest-line "^4.0.1" + wrap-ansi "^8.1.0" + brace-expansion@^1.1.7: version "1.1.11" resolved "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz" @@ -2785,7 +3363,7 @@ braces@^3.0.3, braces@~3.0.2: dependencies: fill-range "^7.1.1" -browserslist@^4.0.0, browserslist@^4.16.6, browserslist@^4.18.1, browserslist@^4.21.10, browserslist@^4.21.3, browserslist@^4.21.4: +browserslist@^4.0.0, browserslist@^4.18.1, browserslist@^4.21.10: version "4.24.2" resolved "https://registry.npmjs.org/browserslist/-/browserslist-4.24.2.tgz" integrity sha512-ZIc+Q62revdMcqC6aChtW4jz3My3klmCO1fEmINZY/8J3EpBg5/A/D0AKmBveUh6pgoeycoMkVMko84tuYS+Gg== @@ -2795,6 +3373,16 @@ browserslist@^4.0.0, browserslist@^4.16.6, browserslist@^4.18.1, browserslist@^4 node-releases "^2.0.18" update-browserslist-db "^1.1.1" +browserslist@^4.23.0, browserslist@^4.23.1, browserslist@^4.23.3, browserslist@^4.24.0, browserslist@^4.24.2: + version "4.24.3" + resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.24.3.tgz#5fc2725ca8fb3c1432e13dac278c7cc103e026d2" + integrity sha512-1CPmv8iobE2fyRMV97dAcMVegvvWKxmq94hkLiAkUGwKVTyDLw33K+ZxiFrREKmmps4rIw6grcCFCnTMSZ/YiA== + dependencies: + caniuse-lite "^1.0.30001688" + electron-to-chromium "^1.5.73" + node-releases "^2.0.19" + update-browserslist-db "^1.1.1" + buffer-from@^1.0.0: version "1.1.2" resolved "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.2.tgz" @@ -2810,18 +3398,23 @@ bytes@3.1.2: resolved "https://registry.npmjs.org/bytes/-/bytes-3.1.2.tgz" integrity sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg== -cacheable-request@^6.0.0: - version "6.1.0" - resolved "https://registry.npmjs.org/cacheable-request/-/cacheable-request-6.1.0.tgz" - integrity sha512-Oj3cAGPCqOZX7Rz64Uny2GYAZNliQSqfbePrgAQ1wKAihYmCUnraBtJtKcGR4xz7wF+LoJC+ssFZvv5BgF9Igg== - dependencies: - clone-response "^1.0.2" - get-stream "^5.1.0" - http-cache-semantics "^4.0.0" - keyv "^3.0.0" - lowercase-keys "^2.0.0" - normalize-url "^4.1.0" - responselike "^1.0.2" +cacheable-lookup@^7.0.0: + version "7.0.0" + resolved "https://registry.yarnpkg.com/cacheable-lookup/-/cacheable-lookup-7.0.0.tgz#3476a8215d046e5a3202a9209dd13fec1f933a27" + integrity sha512-+qJyx4xiKra8mZrcwhjMRMUhD5NR1R8esPkzIYxX96JiecFoxAXFuz/GpR3+ev4PE1WamHip78wV0vcmPQtp8w== + +cacheable-request@^10.2.8: + version "10.2.14" + resolved "https://registry.yarnpkg.com/cacheable-request/-/cacheable-request-10.2.14.tgz#eb915b665fda41b79652782df3f553449c406b9d" + integrity sha512-zkDT5WAF4hSSoUgyfg5tFIxz8XQK+25W/TLVojJTMKBaxevLBBtLxgqguAuVQB8PVW79FVjHcU+GJ9tVbDZ9mQ== + dependencies: + "@types/http-cache-semantics" "^4.0.2" + get-stream "^6.0.1" + http-cache-semantics "^4.1.1" + keyv "^4.5.3" + mimic-response "^4.0.0" + normalize-url "^8.0.0" + responselike "^3.0.0" call-bind@^1.0.2, call-bind@^1.0.7: version "1.0.7" @@ -2847,16 +3440,16 @@ camel-case@^4.1.2: pascal-case "^3.1.2" tslib "^2.0.3" -camelcase-css@2.0.1: - version "2.0.1" - resolved "https://registry.npmjs.org/camelcase-css/-/camelcase-css-2.0.1.tgz" - integrity sha512-QOSvevhslijgYwRx6Rv7zKdMF8lbRmx+uQGx2+vDc+KI/eBnsy9kit5aj23AgGu3pa4t9AgwbnXWqS+iOY+2aA== - camelcase@^6.2.0: version "6.3.0" resolved "https://registry.npmjs.org/camelcase/-/camelcase-6.3.0.tgz" integrity sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA== +camelcase@^7.0.1: + version "7.0.1" + resolved "https://registry.yarnpkg.com/camelcase/-/camelcase-7.0.1.tgz#f02e50af9fd7782bc8b88a3558c32fd3a388f048" + integrity sha512-xlx1yCK2Oc1APsPXDL2LdlNP6+uu8OCDdhOBSVT279M/S+y75O30C2VuD8T2ogdePBBl7PfPF4504tnLgX3zfw== + caniuse-api@^3.0.0: version "3.0.0" resolved "https://registry.npmjs.org/caniuse-api/-/caniuse-api-3.0.0.tgz" @@ -2867,15 +3460,20 @@ caniuse-api@^3.0.0: lodash.memoize "^4.1.2" lodash.uniq "^4.5.0" -caniuse-lite@^1.0.0, caniuse-lite@^1.0.30001426, caniuse-lite@^1.0.30001669: +caniuse-lite@^1.0.0, caniuse-lite@^1.0.30001669: version "1.0.30001680" resolved "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001680.tgz" integrity sha512-rPQy70G6AGUMnbwS1z6Xg+RkHYPAi18ihs47GH0jcxIG7wArmPgY3XbS2sRdBbxJljp3thdT8BIqv9ccCypiPA== -ccount@^1.0.0: - version "1.1.0" - resolved "https://registry.npmjs.org/ccount/-/ccount-1.1.0.tgz" - integrity sha512-vlNK021QdI7PNeiUh/lKkC/mNHHfV0m/Ad5JoI0TYtlBnJAslM/JIkm/tGC88bkLIwO6OQ5uV6ztS6kVAtCDlg== +caniuse-lite@^1.0.30001646, caniuse-lite@^1.0.30001688: + version "1.0.30001690" + resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001690.tgz#f2d15e3aaf8e18f76b2b8c1481abde063b8104c8" + integrity sha512-5ExiE3qQN6oF8Clf8ifIDcMRCRE/dMGcETG/XGMD8/XiXm6HXQgQTh1yZYLXXpSOsEUlJm1Xr7kGULZTuGtP/w== + +ccount@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/ccount/-/ccount-2.0.1.tgz#17a3bf82302e0870d6da43a01311a8bc02a3ecf5" + integrity sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg== chalk@^2.4.2: version "2.4.2" @@ -2899,20 +3497,35 @@ chalk@^5.0.1: resolved "https://registry.npmjs.org/chalk/-/chalk-5.0.1.tgz" integrity sha512-Fo07WOYGqMfCWHOzSXOt2CxDbC6skS/jO9ynEcmpANMoPrD+W1r1K6Vx7iNm+AQmETU1Xr2t+n8nzkV9t6xh3w== -character-entities-legacy@^1.0.0: - version "1.1.4" - resolved "https://registry.npmjs.org/character-entities-legacy/-/character-entities-legacy-1.1.4.tgz" - integrity sha512-3Xnr+7ZFS1uxeiUDvV02wQ+QDbc55o97tIV5zHScSPJpcLm/r0DFPcoY3tYRp+VZukxuMeKgXYmsXQHO05zQeA== +chalk@^5.2.0: + version "5.4.1" + resolved "https://registry.yarnpkg.com/chalk/-/chalk-5.4.1.tgz#1b48bf0963ec158dce2aacf69c093ae2dd2092d8" + integrity sha512-zgVZuo2WcZgfUEmsn6eO3kINexW8RAE4maiQ8QNs8CtpPCSyMiYsULR3HQYkm3w8FIA3SberyMJMSldGsW+U3w== -character-entities@^1.0.0: - version "1.2.4" - resolved "https://registry.npmjs.org/character-entities/-/character-entities-1.2.4.tgz" - integrity sha512-iBMyeEHxfVnIakwOuDXpVkc54HijNgCyQB2w0VfGQThle6NXn50zU6V/u+LDhxHcDUPojn6Kpga3PTAD8W1bQw== +char-regex@^1.0.2: + version "1.0.2" + resolved "https://registry.yarnpkg.com/char-regex/-/char-regex-1.0.2.tgz#d744358226217f981ed58f479b1d6bcc29545dcf" + integrity sha512-kWWXztvZ5SBQV+eRgKFeh8q5sLuZY2+8WUIzlxWVTg+oGwY14qylx1KbKzHd8P6ZYkAg0xyIDU9JMHhyJMZ1jw== -character-reference-invalid@^1.0.0: - version "1.1.4" - resolved "https://registry.npmjs.org/character-reference-invalid/-/character-reference-invalid-1.1.4.tgz" - integrity sha512-mKKUkUbhPpQlCOfIuZkvSEgktjPFIsZKRRbC6KWVEMvlzblj3i3asQv5ODsrwt0N3pHAEvjP8KTQPHkp0+6jOg== +character-entities-html4@^2.0.0: + version "2.1.0" + resolved "https://registry.yarnpkg.com/character-entities-html4/-/character-entities-html4-2.1.0.tgz#1f1adb940c971a4b22ba39ddca6b618dc6e56b2b" + integrity sha512-1v7fgQRj6hnSwFpq1Eu0ynr/CDEw0rXo2B61qXrLNdHZmPKgb7fqS1a2JwF0rISo9q77jDI8VMEHoApn8qDoZA== + +character-entities-legacy@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/character-entities-legacy/-/character-entities-legacy-3.0.0.tgz#76bc83a90738901d7bc223a9e93759fdd560125b" + integrity sha512-RpPp0asT/6ufRm//AJVwpViZbGM/MkjQFxJccQRHmISF/22NBtsHqAWmL+/pmkPWoIUJdWyeVleTl1wydHATVQ== + +character-entities@^2.0.0: + version "2.0.2" + resolved "https://registry.yarnpkg.com/character-entities/-/character-entities-2.0.2.tgz#2d09c2e72cd9523076ccb21157dff66ad43fcc22" + integrity sha512-shx7oQ0Awen/BRIdkjkvz54PnEEI/EjwXDSIZp86/KKdbafHh1Df/RYGBhn4hbe2+uKC9FnT5UCEdyPz3ai9hQ== + +character-reference-invalid@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/character-reference-invalid/-/character-reference-invalid-2.0.1.tgz#85c66b041e43b47210faf401278abf808ac45cb9" + integrity sha512-iBZ4F4wRbyORVsu0jPV7gXkOsGYjGHPmAyv+HiHG8gi5PtC9KI2j1+v8/tlibRvjoWX027ypmG/n0HtO5t7unw== cheerio-select@^2.1.0: version "2.1.0" @@ -2926,9 +3539,9 @@ cheerio-select@^2.1.0: domhandler "^5.0.3" domutils "^3.0.1" -cheerio@^1.0.0-rc.12: +cheerio@1.0.0-rc.12: version "1.0.0-rc.12" - resolved "https://registry.npmjs.org/cheerio/-/cheerio-1.0.0-rc.12.tgz" + resolved "https://registry.yarnpkg.com/cheerio/-/cheerio-1.0.0-rc.12.tgz#788bf7466506b1c6bf5fae51d24a2c4d62e47683" integrity sha512-VqR8m68vM46BNnuZ5NtnGBKIE/DfN0cRIzg9n40EIq9NOv90ayxLBXA8fXC5gquFRGJSTRqBq25Jt2ECLR431Q== dependencies: cheerio-select "^2.1.0" @@ -2959,42 +3572,39 @@ chrome-trace-event@^1.0.2: resolved "https://registry.npmjs.org/chrome-trace-event/-/chrome-trace-event-1.0.3.tgz" integrity sha512-p3KULyQg4S7NIHixdwbGX+nFHkoBiA4YQmyWtjb8XngSKV124nJmRysgAeujbUVb15vh+RvFUfCPqU7rXk+hZg== -ci-info@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/ci-info/-/ci-info-2.0.0.tgz" - integrity sha512-5tK7EtrZ0N+OLFMthtqOj4fI2Jeb88C4CAZPu25LDVUgXJ0A3Js4PMGqrn0JU1W0Mh1/Z8wZzYPxqUrXeBboCQ== - ci-info@^3.2.0: version "3.7.1" resolved "https://registry.npmjs.org/ci-info/-/ci-info-3.7.1.tgz" integrity sha512-4jYS4MOAaCIStSRwiuxc4B8MYhIe676yO1sYGzARnjXkWpmzZMMYxY6zu8WYWDhSuth5zhrQ1rhNSibyyvv4/w== -clean-css@^5.2.2, clean-css@^5.3.0: +clean-css@^5.2.2: version "5.3.2" resolved "https://registry.npmjs.org/clean-css/-/clean-css-5.3.2.tgz" integrity sha512-JVJbM+f3d3Q704rF4bqQ5UUyTtuJ0JRKNbTKVEeujCCBoMdkEi+V+e8oktO9qGQNSvHrFTM6JZRXrUvGR1czww== dependencies: source-map "~0.6.0" +clean-css@^5.3.2, clean-css@~5.3.2: + version "5.3.3" + resolved "https://registry.yarnpkg.com/clean-css/-/clean-css-5.3.3.tgz#b330653cd3bd6b75009cc25c714cae7b93351ccd" + integrity sha512-D5J+kHaVb/wKSFcyyV75uCn8fiY4sV38XJoe4CUyGQ+mOU/fMVYUdH1hJC+CJQ5uY3EnW27SbJYS4X8BiLrAFg== + dependencies: + source-map "~0.6.0" + clean-stack@^2.0.0: version "2.2.0" resolved "https://registry.npmjs.org/clean-stack/-/clean-stack-2.2.0.tgz" integrity sha512-4diC9HaTE+KRAMWhDhrGOECgWZxoevMc5TlkObMqNSsVU62PYzXZ/SMTjzyGAFF1YusgxGcSWTEXBhp0CPwQ1A== -cli-boxes@^2.2.1: - version "2.2.1" - resolved "https://registry.npmjs.org/cli-boxes/-/cli-boxes-2.2.1.tgz" - integrity sha512-y4coMcylgSCdVinjiDBuR8PCC2bLjyGTwEmPb9NHR/QaNU6EUOXcTY/s6VjGMD6ENSEaeQYHCY0GNGS5jfMwPw== - cli-boxes@^3.0.0: version "3.0.0" resolved "https://registry.npmjs.org/cli-boxes/-/cli-boxes-3.0.0.tgz" integrity sha512-/lzGpEWL/8PfI0BmBOPRwp0c/wFNX1RdUML3jK/RcSBA9T8mZDdQpqYBKtCFTOfQbwPqWEOpjqW+Fnayc0969g== -cli-table3@^0.6.2: - version "0.6.3" - resolved "https://registry.npmjs.org/cli-table3/-/cli-table3-0.6.3.tgz" - integrity sha512-w5Jac5SykAeZJKntOxJCrm63Eg5/4dhMWIcuTbo9rpE+brgaSZo0RuNJZeOyMgsUdhDeojvgyQLmjI+K50ZGyg== +cli-table3@^0.6.3: + version "0.6.5" + resolved "https://registry.yarnpkg.com/cli-table3/-/cli-table3-0.6.5.tgz#013b91351762739c16a9567c21a04632e449bf2f" + integrity sha512-+W/5efTR7y5HRD7gACw9yQjqMVvEMLBHmboM/kPWam+H+Hmyrgjh6YncVKK122YZkXrLudzTuAukUw9FnMf7IQ== dependencies: string-width "^4.2.0" optionalDependencies: @@ -3009,22 +3619,15 @@ clone-deep@^4.0.1: kind-of "^6.0.2" shallow-clone "^3.0.0" -clone-response@^1.0.2: - version "1.0.3" - resolved "https://registry.npmjs.org/clone-response/-/clone-response-1.0.3.tgz" - integrity sha512-ROoL94jJH2dUVML2Y/5PEDNaSHgeOdSDicUyS7izcF63G6sTc/FTjLub4b8Il9S8S0beOfYt0TaA5qvFK+w0wA== - dependencies: - mimic-response "^1.0.0" - -clsx@^1.2.1: - version "1.2.1" - resolved "https://registry.npmjs.org/clsx/-/clsx-1.2.1.tgz" - integrity sha512-EcR6r5a8bj6pu3ycsa/E/cKVGuTgZJZdsyUYHOksG/UHIiKfjxzRxYJpyVBwYaQeOvghal9fcc4PidlgzugAQg== +clsx@^2.0.0: + version "2.1.1" + resolved "https://registry.yarnpkg.com/clsx/-/clsx-2.1.1.tgz#eed397c9fd8bd882bfb18deab7102049a2f32999" + integrity sha512-eYm0QWBtUrBWZWG0d386OGAw16Z995PiOVo2B7bjWSbHedGl5e0ZWaq65kOGgUSNesEIDkB9ISbTg/JK9dhCZA== -collapse-white-space@^1.0.2: - version "1.0.6" - resolved "https://registry.npmjs.org/collapse-white-space/-/collapse-white-space-1.0.6.tgz" - integrity sha512-jEovNnrhMuqyCcjfEJA56v0Xq8SkIoPKDyaHahwo3POf4qcSXqMYuwNcOTzp74vTsR9Tn08z4MxWqAhcekogkQ== +collapse-white-space@^2.0.0: + version "2.1.0" + resolved "https://registry.yarnpkg.com/collapse-white-space/-/collapse-white-space-2.1.0.tgz#640257174f9f42c740b40f3b55ee752924feefca" + integrity sha512-loKTxY1zCOuG4j9f6EPnuyyYkf58RnhhWTvRoZEokgB+WbdXehfjFviyOVYkqzEWz1Q5kRiZdBYS5SwxbQYwzw== color-convert@^1.9.0: version "1.9.3" @@ -3050,9 +3653,9 @@ color-name@~1.1.4: resolved "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz" integrity sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA== -colord@^2.9.1: +colord@^2.9.3: version "2.9.3" - resolved "https://registry.npmjs.org/colord/-/colord-2.9.3.tgz" + resolved "https://registry.yarnpkg.com/colord/-/colord-2.9.3.tgz#4f8ce919de456f1d5c1c368c307fe20f3e59fb43" integrity sha512-jeC1axXpnb0/2nn/Y1LPuLdgXBLH7aDcHu4KEKfqw3CUhX7ZpfBSlPKyqXE6btIgEzfWtrX3/tyBCaCvXvMkOw== colorette@^2.0.10: @@ -3070,10 +3673,15 @@ combine-promises@^1.1.0: resolved "https://registry.npmjs.org/combine-promises/-/combine-promises-1.1.0.tgz" integrity sha512-ZI9jvcLDxqwaXEixOhArm3r7ReIivsXkpbyEWyeOhzz1QS0iSgBPnWvEqvIQtYyamGCYA88gFhmUrs9hrrQ0pg== -comma-separated-tokens@^1.0.0: - version "1.0.8" - resolved "https://registry.npmjs.org/comma-separated-tokens/-/comma-separated-tokens-1.0.8.tgz" - integrity sha512-GHuDRO12Sypu2cV70d1dkA2EUmXHgntrzbpvOB+Qy+49ypNfGgFQIC2fhhXbnyrJRynDCAARsT7Ou0M6hirpfw== +comma-separated-tokens@^2.0.0: + version "2.0.3" + resolved "https://registry.yarnpkg.com/comma-separated-tokens/-/comma-separated-tokens-2.0.3.tgz#4e89c9458acb61bc8fef19f4529973b2392839ee" + integrity sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg== + +commander@^10.0.0: + version "10.0.1" + resolved "https://registry.yarnpkg.com/commander/-/commander-10.0.1.tgz#881ee46b4f77d1c1dccc5823433aa39b022cbe06" + integrity sha512-y4Mg2tXshplEbSGzx7amzPwKKOCGuoSRP/CjEdwwk0FOGlUbq6lKuoyDZTNZkmxHdJtp54hdfY/JUrdL7Xfdug== commander@^2.11.0, commander@^2.20.0: version "2.20.3" @@ -3100,6 +3708,11 @@ commander@^9.2.0: resolved "https://registry.npmjs.org/commander/-/commander-9.2.0.tgz" integrity sha512-e2i4wANQiSXgnrBlIatyHtP1odfUp0BbV5Y5nEGbxtIrStkEOAAzCUirvLBNXHLr7kwLvJl6V+4V3XV9x7Wd9w== +common-path-prefix@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/common-path-prefix/-/common-path-prefix-3.0.0.tgz#7d007a7e07c58c4b4d5f433131a19141b29f11e0" + integrity sha512-QE33hToZseCH3jS0qN96O/bSh3kaw/h+Tq7ngyY9eWDUnTlTNUyqfqvCXioLe5Na5jFsL78ra/wuBU4iuEgd4w== + commondir@^1.0.1: version "1.0.1" resolved "https://registry.npmjs.org/commondir/-/commondir-1.0.1.tgz" @@ -3135,27 +3748,34 @@ concat-map@0.0.1: resolved "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz" integrity sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg== -configstore@^5.0.1: - version "5.0.1" - resolved "https://registry.npmjs.org/configstore/-/configstore-5.0.1.tgz" - integrity sha512-aMKprgk5YhBNyH25hj8wGt2+D52Sw1DRRIzqBwLp2Ya9mFmY8KPvvtvmna8SxVR9JMZ4kzMD68N22vlaRpkeFA== +config-chain@^1.1.11: + version "1.1.13" + resolved "https://registry.yarnpkg.com/config-chain/-/config-chain-1.1.13.tgz#fad0795aa6a6cdaff9ed1b68e9dff94372c232f4" + integrity sha512-qj+f8APARXHrM0hraqXYb2/bOVSV4PvJQlNZ/DVj0QrmNM2q2euizkeuVckQ57J+W0mRH6Hvi+k50M4Jul2VRQ== dependencies: - dot-prop "^5.2.0" - graceful-fs "^4.1.2" - make-dir "^3.0.0" - unique-string "^2.0.0" - write-file-atomic "^3.0.0" - xdg-basedir "^4.0.0" + ini "^1.3.4" + proto-list "~1.2.1" + +configstore@^6.0.0: + version "6.0.0" + resolved "https://registry.yarnpkg.com/configstore/-/configstore-6.0.0.tgz#49eca2ebc80983f77e09394a1a56e0aca8235566" + integrity sha512-cD31W1v3GqUlQvbBCGcXmd2Nj9SvLDOP1oQ0YFuLETufzSPaKp11rYBsSOm7rCsW3OnIRAFM3OxRhceaXNYHkA== + dependencies: + dot-prop "^6.0.1" + graceful-fs "^4.2.6" + unique-string "^3.0.0" + write-file-atomic "^3.0.3" + xdg-basedir "^5.0.1" connect-history-api-fallback@^2.0.0: version "2.0.0" resolved "https://registry.npmjs.org/connect-history-api-fallback/-/connect-history-api-fallback-2.0.0.tgz" integrity sha512-U73+6lQFmfiNPrYbXqr6kZ1i1wiRqXnp2nhMsINseWXO8lDau0LGEffJ8kQi4EjLZympVgRdvqjAgiZ1tgzDDA== -consola@^2.15.3: - version "2.15.3" - resolved "https://registry.npmjs.org/consola/-/consola-2.15.3.tgz" - integrity sha512-9vAdYbHj6x2fLKC4+oPH0kFzY/orMZyG2Aj+kNylHxKGJ/Ed4dpNyAQYwJOdqO4zdM7XpVHmyejQDcQHrnuXbw== +consola@^3.2.3: + version "3.3.1" + resolved "https://registry.yarnpkg.com/consola/-/consola-3.3.1.tgz#e60b4bfcd9e36cd766cc9afe2c93c14fe64c9356" + integrity sha512-GyKnPG3/I+a4RtJxgHquJXWr70g9I3c4NT3dvqh0LPHQP2nZFQBOBszb7a5u/pGzqr40AKplQA6UxM1BSynSXg== content-disposition@0.5.2: version "0.5.2" @@ -3174,10 +3794,10 @@ content-type@~1.0.4, content-type@~1.0.5: resolved "https://registry.npmjs.org/content-type/-/content-type-1.0.5.tgz" integrity sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA== -convert-source-map@^1.7.0: - version "1.9.0" - resolved "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.9.0.tgz" - integrity sha512-ASFBup0Mz1uyiIjANan1jzLQami9z1PoYSZCiiYW2FczPbenXc45FZdBZLzOT+r6+iciuEModtmCti+hjaAk0A== +convert-source-map@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-2.0.0.tgz#4b560f649fc4e918dd0ab75cf4961e8bc882d82a" + integrity sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg== cookie-signature@1.0.6: version "1.0.6" @@ -3189,10 +3809,10 @@ cookie@0.7.1: resolved "https://registry.npmjs.org/cookie/-/cookie-0.7.1.tgz" integrity sha512-6DnInpx7SJ2AK3+CTUE/ZM0vWTUboZCegxhC2xiIydHR9jNuTAASBrfEpHhiGOZw/nX51bHt6YQl8jsGo4y/0w== -copy-text-to-clipboard@^3.0.1: - version "3.0.1" - resolved "https://registry.npmjs.org/copy-text-to-clipboard/-/copy-text-to-clipboard-3.0.1.tgz" - integrity sha512-rvVsHrpFcL4F2P8ihsoLdFHmd404+CMg71S756oRSeQgqk51U3kicGdnvfkrxva0xXH92SjGS62B0XIJsbh+9Q== +copy-text-to-clipboard@^3.2.0: + version "3.2.0" + resolved "https://registry.yarnpkg.com/copy-text-to-clipboard/-/copy-text-to-clipboard-3.2.0.tgz#0202b2d9bdae30a49a53f898626dcc3b49ad960b" + integrity sha512-RnJFp1XR/LOBDckxTib5Qjr/PMfkatD0MUCQgdpqS8MdKiNUzBjAQBEN6oUy+jW7LI93BBG3DtMB2KOOKpGs2Q== copy-webpack-plugin@^11.0.0: version "11.0.0" @@ -3206,22 +3826,22 @@ copy-webpack-plugin@^11.0.0: schema-utils "^4.0.0" serialize-javascript "^6.0.0" -core-js-compat@^3.25.1: - version "3.27.2" - resolved "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.27.2.tgz" - integrity sha512-welaYuF7ZtbYKGrIy7y3eb40d37rG1FvzEOfe7hSLd2iD6duMDqUhRfSvCGyC46HhR6Y8JXXdZ2lnRUMkPBpvg== +core-js-compat@^3.38.0, core-js-compat@^3.38.1: + version "3.39.0" + resolved "https://registry.yarnpkg.com/core-js-compat/-/core-js-compat-3.39.0.tgz#b12dccb495f2601dc860bdbe7b4e3ffa8ba63f61" + integrity sha512-VgEUx3VwlExr5no0tXlBt+silBvhTryPwCXRI2Id1PN8WTKu7MreethvddqOubrYxkFdv/RnYrqlv1sFNAUelw== dependencies: - browserslist "^4.21.4" + browserslist "^4.24.2" -core-js-pure@^3.25.1: - version "3.27.2" - resolved "https://registry.npmjs.org/core-js-pure/-/core-js-pure-3.27.2.tgz" - integrity sha512-Cf2jqAbXgWH3VVzjyaaFkY1EBazxugUepGymDoeteyYr9ByX51kD2jdHZlsEF/xnJMyN3Prua7mQuzwMg6Zc9A== +core-js-pure@^3.30.2: + version "3.39.0" + resolved "https://registry.yarnpkg.com/core-js-pure/-/core-js-pure-3.39.0.tgz#aa0d54d70a15bdc13e7c853db87c10abc30d68f3" + integrity sha512-7fEcWwKI4rJinnK+wLTezeg2smbFFdSBP6E2kQZNbnzM2s1rpKQ6aaRteZSSg7FLU3P0HGGVo/gbpfanU36urg== -core-js@^3.23.3: - version "3.27.2" - resolved "https://registry.npmjs.org/core-js/-/core-js-3.27.2.tgz" - integrity sha512-9ashVQskuh5AZEZ1JdQWp1GqSoC1e1G87MzRqg2gIfVAQ7Qn9K+uFj8EcniUFA4P2NLZfV+TOlX1SzoKfo+s7w== +core-js@^3.31.1: + version "3.39.0" + resolved "https://registry.yarnpkg.com/core-js/-/core-js-3.39.0.tgz#57f7647f4d2d030c32a72ea23a0555b2eaa30f83" + integrity sha512-raM0ew0/jJUqkJ0E6e8UDtl+y/7ktFivgWvqw8dNSQeNWoSDLvQ1H/RN3aPXB9tBd4/FhyR4RDPGhsNIMsAn7g== core-util-is@~1.0.0: version "1.0.3" @@ -3239,23 +3859,15 @@ cosmiconfig@^6.0.0: path-type "^4.0.0" yaml "^1.7.2" -cosmiconfig@^7.0.0, cosmiconfig@^7.0.1: - version "7.1.0" - resolved "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-7.1.0.tgz" - integrity sha512-AdmX6xUzdNASswsFtmwSt7Vj8po9IuqXm0UXz7QKPuEUmPB4XyjGfaAr2PSuELMwkRMVH1EpIkX5bTZGRB3eCA== +cosmiconfig@^8.1.3, cosmiconfig@^8.3.5: + version "8.3.6" + resolved "https://registry.yarnpkg.com/cosmiconfig/-/cosmiconfig-8.3.6.tgz#060a2b871d66dba6c8538ea1118ba1ac16f5fae3" + integrity sha512-kcZ6+W5QzcJ3P1Mt+83OUv/oHFqZHIx8DuxG6eZ5RGMERoLqp4BuGjhHLYGK+Kf5XVkQvqBSmAy/nGWN3qDgEA== dependencies: - "@types/parse-json" "^4.0.0" - import-fresh "^3.2.1" - parse-json "^5.0.0" + import-fresh "^3.3.0" + js-yaml "^4.1.0" + parse-json "^5.2.0" path-type "^4.0.0" - yaml "^1.10.0" - -cross-fetch@^3.1.5: - version "3.1.5" - resolved "https://registry.npmjs.org/cross-fetch/-/cross-fetch-3.1.5.tgz" - integrity sha512-lvb1SBsI0Z7GDwmuid+mU3kWVBwTVUbe7S0H52yaaAdQOXq2YktTCZdlAcNKFzE6QtRz0snpw9bNiPeOIkkQvw== - dependencies: - node-fetch "2.6.7" cross-spawn@^5.1.0: version "5.1.0" @@ -3275,41 +3887,64 @@ cross-spawn@^7.0.3: shebang-command "^2.0.0" which "^2.0.1" -crypto-random-string@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/crypto-random-string/-/crypto-random-string-2.0.0.tgz" - integrity sha512-v1plID3y9r/lPhviJ1wrXpLeyUIGAZ2SHNYTEapm7/8A9nLPoyvVp3RK/EPFqn5kEznyWgYZNsRtYYIWbuG8KA== +crypto-random-string@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/crypto-random-string/-/crypto-random-string-4.0.0.tgz#5a3cc53d7dd86183df5da0312816ceeeb5bb1fc2" + integrity sha512-x8dy3RnvYdlUcPOjkEHqozhiwzKNSq7GcPuXFbnyMOCHxX8V3OgIg/pYuabl2sbUPfIJaeAQB7PMOK8DFIdoRA== + dependencies: + type-fest "^1.0.1" -css-declaration-sorter@^6.3.1: - version "6.3.1" - resolved "https://registry.npmjs.org/css-declaration-sorter/-/css-declaration-sorter-6.3.1.tgz" - integrity sha512-fBffmak0bPAnyqc/HO8C3n2sHrp9wcqQz6ES9koRF2/mLOVAx9zIQ3Y7R29sYCteTPqMCwns4WYQoCX91Xl3+w== +css-blank-pseudo@^7.0.1: + version "7.0.1" + resolved "https://registry.yarnpkg.com/css-blank-pseudo/-/css-blank-pseudo-7.0.1.tgz#32020bff20a209a53ad71b8675852b49e8d57e46" + integrity sha512-jf+twWGDf6LDoXDUode+nc7ZlrqfaNphrBIBrcmeP3D8yw1uPaix1gCC8LUQUGQ6CycuK2opkbFFWFuq/a94ag== + dependencies: + postcss-selector-parser "^7.0.0" + +css-declaration-sorter@^7.2.0: + version "7.2.0" + resolved "https://registry.yarnpkg.com/css-declaration-sorter/-/css-declaration-sorter-7.2.0.tgz#6dec1c9523bc4a643e088aab8f09e67a54961024" + integrity sha512-h70rUM+3PNFuaBDTLe8wF/cdWu+dOZmb7pJt8Z2sedYbAcQVQV/tEchueg3GWxwqS0cxtbxmaHEdkNACqcvsow== + +css-has-pseudo@^7.0.2: + version "7.0.2" + resolved "https://registry.yarnpkg.com/css-has-pseudo/-/css-has-pseudo-7.0.2.tgz#fb42e8de7371f2896961e1f6308f13c2c7019b72" + integrity sha512-nzol/h+E0bId46Kn2dQH5VElaknX2Sr0hFuB/1EomdC7j+OISt2ZzK7EHX9DZDY53WbIVAR7FYKSO2XnSf07MQ== + dependencies: + "@csstools/selector-specificity" "^5.0.0" + postcss-selector-parser "^7.0.0" + postcss-value-parser "^4.2.0" -css-loader@^6.7.1: - version "6.7.3" - resolved "https://registry.npmjs.org/css-loader/-/css-loader-6.7.3.tgz" - integrity sha512-qhOH1KlBMnZP8FzRO6YCH9UHXQhVMcEGLyNdb7Hv2cpcmJbW0YrddO+tG1ab5nT41KpHIYGsbeHqxB9xPu1pKQ== +css-loader@^6.8.1: + version "6.11.0" + resolved "https://registry.yarnpkg.com/css-loader/-/css-loader-6.11.0.tgz#33bae3bf6363d0a7c2cf9031c96c744ff54d85ba" + integrity sha512-CTJ+AEQJjq5NzLga5pE39qdiSV56F8ywCIsqNIRF0r7BDgWsN25aazToqAFg7ZrtA/U016xudB3ffgweORxX7g== dependencies: icss-utils "^5.1.0" - postcss "^8.4.19" - postcss-modules-extract-imports "^3.0.0" - postcss-modules-local-by-default "^4.0.0" - postcss-modules-scope "^3.0.0" + postcss "^8.4.33" + postcss-modules-extract-imports "^3.1.0" + postcss-modules-local-by-default "^4.0.5" + postcss-modules-scope "^3.2.0" postcss-modules-values "^4.0.0" postcss-value-parser "^4.2.0" - semver "^7.3.8" + semver "^7.5.4" -css-minimizer-webpack-plugin@^4.0.0: - version "4.2.2" - resolved "https://registry.npmjs.org/css-minimizer-webpack-plugin/-/css-minimizer-webpack-plugin-4.2.2.tgz" - integrity sha512-s3Of/4jKfw1Hj9CxEO1E5oXhQAxlayuHO2y/ML+C6I9sQ7FdzfEV6QgMLN3vI+qFsjJGIAFLKtQK7t8BOXAIyA== - dependencies: - cssnano "^5.1.8" - jest-worker "^29.1.2" - postcss "^8.4.17" - schema-utils "^4.0.0" - serialize-javascript "^6.0.0" - source-map "^0.6.1" +css-minimizer-webpack-plugin@^5.0.1: + version "5.0.1" + resolved "https://registry.yarnpkg.com/css-minimizer-webpack-plugin/-/css-minimizer-webpack-plugin-5.0.1.tgz#33effe662edb1a0bf08ad633c32fa75d0f7ec565" + integrity sha512-3caImjKFQkS+ws1TGcFn0V1HyDJFq1Euy589JlD6/3rV2kj+w7r5G9WDMgSHvpvXHNZ2calVypZWuEDQd9wfLg== + dependencies: + "@jridgewell/trace-mapping" "^0.3.18" + cssnano "^6.0.1" + jest-worker "^29.4.3" + postcss "^8.4.24" + schema-utils "^4.0.1" + serialize-javascript "^6.0.1" + +css-prefers-color-scheme@^10.0.0: + version "10.0.0" + resolved "https://registry.yarnpkg.com/css-prefers-color-scheme/-/css-prefers-color-scheme-10.0.0.tgz#ba001b99b8105b8896ca26fc38309ddb2278bd3c" + integrity sha512-VCtXZAWivRglTZditUfB4StnsWr6YVZ2PRtuxQLKTNRdtAf8tpzaVPE9zXIF3VaSc7O70iK/j1+NXxyQCqdPjQ== css-select@^4.1.3: version "4.3.0" @@ -3333,97 +3968,116 @@ css-select@^5.1.0: domutils "^3.0.1" nth-check "^2.0.1" -css-tree@^1.1.2, css-tree@^1.1.3: - version "1.1.3" - resolved "https://registry.npmjs.org/css-tree/-/css-tree-1.1.3.tgz" - integrity sha512-tRpdppF7TRazZrjJ6v3stzv93qxRcSsFmW6cX0Zm2NVKpxE1WV1HblnghVv9TreireHkqI/VDEsfolRF1p6y7Q== +css-tree@^2.3.1: + version "2.3.1" + resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-2.3.1.tgz#10264ce1e5442e8572fc82fbe490644ff54b5c20" + integrity sha512-6Fv1DV/TYw//QF5IzQdqsNDjx/wc8TrMBZsqjL9eW01tWb7R7k/mq+/VXfJCl7SoD5emsJop9cOByJZfs8hYIw== + dependencies: + mdn-data "2.0.30" + source-map-js "^1.0.1" + +css-tree@~2.2.0: + version "2.2.1" + resolved "https://registry.yarnpkg.com/css-tree/-/css-tree-2.2.1.tgz#36115d382d60afd271e377f9c5f67d02bd48c032" + integrity sha512-OA0mILzGc1kCOCSJerOeqDxDQ4HOh+G8NbOJFOTgOCzpw7fCBubk0fEyxp8AgOL/jvLgYA/uV0cMbe43ElF1JA== dependencies: - mdn-data "2.0.14" - source-map "^0.6.1" + mdn-data "2.0.28" + source-map-js "^1.0.1" css-what@^6.0.1, css-what@^6.1.0: version "6.1.0" resolved "https://registry.npmjs.org/css-what/-/css-what-6.1.0.tgz" integrity sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw== +cssdb@^8.2.3: + version "8.2.3" + resolved "https://registry.yarnpkg.com/cssdb/-/cssdb-8.2.3.tgz#7e6980bb5a785a9b4eb2a21bd38d50624b56cb46" + integrity sha512-9BDG5XmJrJQQnJ51VFxXCAtpZ5ebDlAREmO8sxMOVU0aSxN/gocbctjIG5LMh3WBUq+xTlb/jw2LoljBEqraTA== + cssesc@^3.0.0: version "3.0.0" resolved "https://registry.npmjs.org/cssesc/-/cssesc-3.0.0.tgz" integrity sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg== -cssnano-preset-advanced@^5.3.8: - version "5.3.9" - resolved "https://registry.npmjs.org/cssnano-preset-advanced/-/cssnano-preset-advanced-5.3.9.tgz" - integrity sha512-njnh4pp1xCsibJcEHnWZb4EEzni0ePMqPuPNyuWT4Z+YeXmsgqNuTPIljXFEXhxGsWs9183JkXgHxc1TcsahIg== - dependencies: - autoprefixer "^10.4.12" - cssnano-preset-default "^5.2.13" - postcss-discard-unused "^5.1.0" - postcss-merge-idents "^5.1.1" - postcss-reduce-idents "^5.2.0" - postcss-zindex "^5.1.0" - -cssnano-preset-default@^5.2.13: - version "5.2.13" - resolved "https://registry.npmjs.org/cssnano-preset-default/-/cssnano-preset-default-5.2.13.tgz" - integrity sha512-PX7sQ4Pb+UtOWuz8A1d+Rbi+WimBIxJTRyBdgGp1J75VU0r/HFQeLnMYgHiCAp6AR4rqrc7Y4R+1Rjk3KJz6DQ== - dependencies: - css-declaration-sorter "^6.3.1" - cssnano-utils "^3.1.0" - postcss-calc "^8.2.3" - postcss-colormin "^5.3.0" - postcss-convert-values "^5.1.3" - postcss-discard-comments "^5.1.2" - postcss-discard-duplicates "^5.1.0" - postcss-discard-empty "^5.1.1" - postcss-discard-overridden "^5.1.0" - postcss-merge-longhand "^5.1.7" - postcss-merge-rules "^5.1.3" - postcss-minify-font-values "^5.1.0" - postcss-minify-gradients "^5.1.1" - postcss-minify-params "^5.1.4" - postcss-minify-selectors "^5.2.1" - postcss-normalize-charset "^5.1.0" - postcss-normalize-display-values "^5.1.0" - postcss-normalize-positions "^5.1.1" - postcss-normalize-repeat-style "^5.1.1" - postcss-normalize-string "^5.1.0" - postcss-normalize-timing-functions "^5.1.0" - postcss-normalize-unicode "^5.1.1" - postcss-normalize-url "^5.1.0" - postcss-normalize-whitespace "^5.1.1" - postcss-ordered-values "^5.1.3" - postcss-reduce-initial "^5.1.1" - postcss-reduce-transforms "^5.1.0" - postcss-svgo "^5.1.0" - postcss-unique-selectors "^5.1.1" - -cssnano-utils@^3.1.0: - version "3.1.0" - resolved "https://registry.npmjs.org/cssnano-utils/-/cssnano-utils-3.1.0.tgz" - integrity sha512-JQNR19/YZhz4psLX/rQ9M83e3z2Wf/HdJbryzte4a3NSuafyp9w/I4U+hx5C2S9g41qlstH7DEWnZaaj83OuEA== +cssnano-preset-advanced@^6.1.2: + version "6.1.2" + resolved "https://registry.yarnpkg.com/cssnano-preset-advanced/-/cssnano-preset-advanced-6.1.2.tgz#82b090872b8f98c471f681d541c735acf8b94d3f" + integrity sha512-Nhao7eD8ph2DoHolEzQs5CfRpiEP0xa1HBdnFZ82kvqdmbwVBUr2r1QuQ4t1pi+D1ZpqpcO4T+wy/7RxzJ/WPQ== + dependencies: + autoprefixer "^10.4.19" + browserslist "^4.23.0" + cssnano-preset-default "^6.1.2" + postcss-discard-unused "^6.0.5" + postcss-merge-idents "^6.0.3" + postcss-reduce-idents "^6.0.3" + postcss-zindex "^6.0.2" + +cssnano-preset-default@^6.1.2: + version "6.1.2" + resolved "https://registry.yarnpkg.com/cssnano-preset-default/-/cssnano-preset-default-6.1.2.tgz#adf4b89b975aa775f2750c89dbaf199bbd9da35e" + integrity sha512-1C0C+eNaeN8OcHQa193aRgYexyJtU8XwbdieEjClw+J9d94E41LwT6ivKH0WT+fYwYWB0Zp3I3IZ7tI/BbUbrg== + dependencies: + browserslist "^4.23.0" + css-declaration-sorter "^7.2.0" + cssnano-utils "^4.0.2" + postcss-calc "^9.0.1" + postcss-colormin "^6.1.0" + postcss-convert-values "^6.1.0" + postcss-discard-comments "^6.0.2" + postcss-discard-duplicates "^6.0.3" + postcss-discard-empty "^6.0.3" + postcss-discard-overridden "^6.0.2" + postcss-merge-longhand "^6.0.5" + postcss-merge-rules "^6.1.1" + postcss-minify-font-values "^6.1.0" + postcss-minify-gradients "^6.0.3" + postcss-minify-params "^6.1.0" + postcss-minify-selectors "^6.0.4" + postcss-normalize-charset "^6.0.2" + postcss-normalize-display-values "^6.0.2" + postcss-normalize-positions "^6.0.2" + postcss-normalize-repeat-style "^6.0.2" + postcss-normalize-string "^6.0.2" + postcss-normalize-timing-functions "^6.0.2" + postcss-normalize-unicode "^6.1.0" + postcss-normalize-url "^6.0.2" + postcss-normalize-whitespace "^6.0.2" + postcss-ordered-values "^6.0.2" + postcss-reduce-initial "^6.1.0" + postcss-reduce-transforms "^6.0.2" + postcss-svgo "^6.0.3" + postcss-unique-selectors "^6.0.4" + +cssnano-utils@^4.0.2: + version "4.0.2" + resolved "https://registry.yarnpkg.com/cssnano-utils/-/cssnano-utils-4.0.2.tgz#56f61c126cd0f11f2eef1596239d730d9fceff3c" + integrity sha512-ZR1jHg+wZ8o4c3zqf1SIUSTIvm/9mU343FMR6Obe/unskbvpGhZOo1J6d/r8D1pzkRQYuwbcH3hToOuoA2G7oQ== -cssnano@^5.1.12, cssnano@^5.1.8: - version "5.1.14" - resolved "https://registry.npmjs.org/cssnano/-/cssnano-5.1.14.tgz" - integrity sha512-Oou7ihiTocbKqi0J1bB+TRJIQX5RMR3JghA8hcWSw9mjBLQ5Y3RWqEDoYG3sRNlAbCIXpqMoZGbq5KDR3vdzgw== +cssnano@^6.0.1, cssnano@^6.1.2: + version "6.1.2" + resolved "https://registry.yarnpkg.com/cssnano/-/cssnano-6.1.2.tgz#4bd19e505bd37ee7cf0dc902d3d869f6d79c66b8" + integrity sha512-rYk5UeX7VAM/u0lNqewCdasdtPK81CgX8wJFLEIXHbV2oldWRgJAsZrdhRXkV1NJzA2g850KiFm9mMU2HxNxMA== dependencies: - cssnano-preset-default "^5.2.13" - lilconfig "^2.0.3" - yaml "^1.10.2" + cssnano-preset-default "^6.1.2" + lilconfig "^3.1.1" -csso@^4.2.0: - version "4.2.0" - resolved "https://registry.npmjs.org/csso/-/csso-4.2.0.tgz" - integrity sha512-wvlcdIbf6pwKEk7vHj8/Bkc0B4ylXZruLvOgs9doS5eOsOpuodOV2zJChSpkp+pRpYQLQMeF04nr3Z68Sta9jA== +csso@^5.0.5: + version "5.0.5" + resolved "https://registry.yarnpkg.com/csso/-/csso-5.0.5.tgz#f9b7fe6cc6ac0b7d90781bb16d5e9874303e2ca6" + integrity sha512-0LrrStPOdJj+SPCCrGhzryycLjwcgUSHBtxNA8aIDxf0GLsRh1cKYhB00Gd1lDOS4yGH69+SNn13+TWbVHETFQ== dependencies: - css-tree "^1.1.2" + css-tree "~2.2.0" csstype@^3.0.2: version "3.1.1" resolved "https://registry.npmjs.org/csstype/-/csstype-3.1.1.tgz" integrity sha512-DJR/VvkAvSZW9bTouZue2sSxDwdTN92uHjqeKVm+0dAqdfNykRzQ95tay8aXMBAAPpUiq4Qcug2L7neoRh2Egw== +debounce@^1.2.1: + version "1.2.1" + resolved "https://registry.yarnpkg.com/debounce/-/debounce-1.2.1.tgz#38881d8f4166a5c5848020c11827b834bcb3e0a5" + integrity sha512-XRRe6Glud4rd/ZGQfiV1ruXSfbvfJedlV9Y6zOlP+2K04vBYiJEte6stfFkCP03aMnY5tsipamumUjL14fofug== + debug@2.6.9, debug@^2.6.0: version "2.6.9" resolved "https://registry.npmjs.org/debug/-/debug-2.6.9.tgz" @@ -3438,12 +4092,26 @@ debug@4, debug@^4.1.0, debug@^4.1.1: dependencies: ms "2.1.2" -decompress-response@^3.3.0: - version "3.3.0" - resolved "https://registry.npmjs.org/decompress-response/-/decompress-response-3.3.0.tgz" - integrity sha512-BzRPQuY1ip+qDonAOz42gRm/pg9F768C+npV/4JOsxRC2sq+Rlk+Q4ZCAsOhnIaMrgarILY+RMUIvMmmX1qAEA== +debug@^4.0.0, debug@^4.3.1: + version "4.4.0" + resolved "https://registry.yarnpkg.com/debug/-/debug-4.4.0.tgz#2b3f2aea2ffeb776477460267377dc8710faba8a" + integrity sha512-6WTZ/IxCY/T6BALoZHaE4ctp9xm+Z5kY/pzYaCHRFeyVhojxlrm+46y68HA6hr0TcwEssoxNiDEUJQjfPZ/RYA== + dependencies: + ms "^2.1.3" + +decode-named-character-reference@^1.0.0: + version "1.0.2" + resolved "https://registry.yarnpkg.com/decode-named-character-reference/-/decode-named-character-reference-1.0.2.tgz#daabac9690874c394c81e4162a0304b35d824f0e" + integrity sha512-O8x12RzrUF8xyVcY0KJowWsmaJxQbmy0/EtnNtHRpsOcT7dFk5W598coHqBVpmWo1oQQfsCqfCmkZN5DJrZVdg== dependencies: - mimic-response "^1.0.0" + character-entities "^2.0.0" + +decompress-response@^6.0.0: + version "6.0.0" + resolved "https://registry.yarnpkg.com/decompress-response/-/decompress-response-6.0.0.tgz#ca387612ddb7e104bd16d85aab00d5ecf09c66fc" + integrity sha512-aW35yZM6Bb/4oJlZncMH2LCoZtJXTRxES17vE3hoRiowU2kWHaJKFkSBDnDR+cm9J+9QhXmREyIfv0pji9ejCQ== + dependencies: + mimic-response "^3.1.0" deep-extend@^0.6.0: version "0.6.0" @@ -3455,6 +4123,11 @@ deepmerge@^4.0.0, deepmerge@^4.2.2: resolved "https://registry.npmjs.org/deepmerge/-/deepmerge-4.3.0.tgz" integrity sha512-z2wJZXrmeHdvYJp/Ux55wIjqo81G5Bp4c+oELTW+7ar6SogWHajt5a9gO3s3IDaGSAXjDk0vlQKN3rms8ab3og== +deepmerge@^4.3.1: + version "4.3.1" + resolved "https://registry.yarnpkg.com/deepmerge/-/deepmerge-4.3.1.tgz#44b5f2147cd3b00d4b56137685966f26fd25dd4a" + integrity sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A== + default-gateway@^6.0.3: version "6.0.3" resolved "https://registry.npmjs.org/default-gateway/-/default-gateway-6.0.3.tgz" @@ -3462,10 +4135,10 @@ default-gateway@^6.0.3: dependencies: execa "^5.0.0" -defer-to-connect@^1.0.1: - version "1.1.3" - resolved "https://registry.npmjs.org/defer-to-connect/-/defer-to-connect-1.1.3.tgz" - integrity sha512-0ISdNousHvZT2EiFlZeZAHBUvSxmKswVCEf8hW7KWgG4a8MVEu/3Vb6uWYozkjylyCxe0JBIiRB1jV45S70WVQ== +defer-to-connect@^2.0.1: + version "2.0.1" + resolved "https://registry.yarnpkg.com/defer-to-connect/-/defer-to-connect-2.0.1.tgz#8016bdb4143e4632b77a3449c6236277de520587" + integrity sha512-4tvttepXG1VaYGrRibk5EwJd1t4udunSOVMdLSAL6mId1ix438oPwPZMALY41FCijukO1L0twNcGsdzS7dHgDg== define-data-property@^1.1.4: version "1.1.4" @@ -3513,18 +4186,16 @@ depd@~1.1.2: resolved "https://registry.npmjs.org/depd/-/depd-1.1.2.tgz" integrity sha512-7emPTl6Dpo6JRXOXjLRxck+FlLRX5847cLKEn00PLAgc3g2hTZZgr+e4c2v6QpSmLeFP3n5yUo7ft6avBK/5jQ== +dequal@^2.0.0: + version "2.0.3" + resolved "https://registry.yarnpkg.com/dequal/-/dequal-2.0.3.tgz#2644214f1997d39ed0ee0ece72335490a7ac67be" + integrity sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA== + destroy@1.2.0: version "1.2.0" resolved "https://registry.npmjs.org/destroy/-/destroy-1.2.0.tgz" integrity sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg== -detab@2.0.4: - version "2.0.4" - resolved "https://registry.npmjs.org/detab/-/detab-2.0.4.tgz" - integrity sha512-8zdsQA5bIkoRECvCrNKPla84lyoR7DSAyf7p0YgXzBO9PDJx8KntPUay7NS6yp+KdxdVtiE5SpHKtbp2ZQyA9g== - dependencies: - repeat-string "^1.5.4" - detect-node@^2.0.4: version "2.1.0" resolved "https://registry.npmjs.org/detect-node/-/detect-node-2.1.0.tgz" @@ -3538,14 +4209,21 @@ detect-port-alt@^1.1.6: address "^1.0.1" debug "^2.6.0" -detect-port@^1.3.0: - version "1.5.1" - resolved "https://registry.npmjs.org/detect-port/-/detect-port-1.5.1.tgz" - integrity sha512-aBzdj76lueB6uUst5iAs7+0H/oOjqI5D16XUWxlWMIMROhcM0rfsNVk93zTngq1dDNpoXRr++Sus7ETAExppAQ== +detect-port@^1.5.1: + version "1.6.1" + resolved "https://registry.yarnpkg.com/detect-port/-/detect-port-1.6.1.tgz#45e4073997c5f292b957cb678fb0bb8ed4250a67" + integrity sha512-CmnVc+Hek2egPx1PeTFVta2W78xy2K/9Rkf6cC4T59S50tVnzKj+tnx5mmx5lwvCkujZ4uRrpRSuV+IVs3f90Q== dependencies: address "^1.0.1" debug "4" +devlop@^1.0.0, devlop@^1.1.0: + version "1.1.0" + resolved "https://registry.yarnpkg.com/devlop/-/devlop-1.1.0.tgz#4db7c2ca4dc6e0e834c30be70c94bbc976dc7018" + integrity sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA== + dependencies: + dequal "^2.0.0" + dir-glob@^3.0.1: version "3.0.1" resolved "https://registry.npmjs.org/dir-glob/-/dir-glob-3.0.1.tgz" @@ -3635,18 +4313,13 @@ dot-case@^3.0.4: no-case "^3.0.4" tslib "^2.0.3" -dot-prop@^5.2.0: - version "5.3.0" - resolved "https://registry.npmjs.org/dot-prop/-/dot-prop-5.3.0.tgz" - integrity sha512-QM8q3zDe58hqUqjraQOmzZ1LIH9SWQJTlEKCH4kJ2oQvLZk7RbQXvtDM2XEq3fwkV9CCvvH4LA0AV+ogFsBM2Q== +dot-prop@^6.0.1: + version "6.0.1" + resolved "https://registry.yarnpkg.com/dot-prop/-/dot-prop-6.0.1.tgz#fc26b3cf142b9e59b74dbd39ed66ce620c681083" + integrity sha512-tE7ztYzXHIeyvc7N+hR3oi7FIbf/NIjVP9hmAt3yMXzrQ072/fpjGLx2GxNxGxUl5V73MEqYzioOMoVhGMJ5cA== dependencies: is-obj "^2.0.0" -duplexer3@^0.1.4: - version "0.1.5" - resolved "https://registry.npmjs.org/duplexer3/-/duplexer3-0.1.5.tgz" - integrity sha512-1A8za6ws41LQgv9HrE/66jyC5yuSjQ3L/KOpFtoBilsAK2iA2wuS5rTt1OCzIvtS2V7nVmedsUU+DGRcjBmOYA== - duplexer@^0.1.2: version "0.1.2" resolved "https://registry.npmjs.org/duplexer/-/duplexer-0.1.2.tgz" @@ -3672,6 +4345,11 @@ electron-to-chromium@^1.5.41: resolved "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.57.tgz" integrity sha512-xS65H/tqgOwUBa5UmOuNSLuslDo7zho0y/lgQw35pnrqiZh7UOWHCeL/Bt6noJATbA6tpQJGCifsFsIRZj1Fqg== +electron-to-chromium@^1.5.73: + version "1.5.76" + resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.5.76.tgz#db20295c5061b68f07c8ea4dfcbd701485d94a3d" + integrity sha512-CjVQyG7n7Sr+eBXE86HIulnL5N8xZY1sgmOPGuq/F0Rr0FJq63lg0kEtOIDfZBk44FnDLf6FUJ+dsJcuiUDdDQ== + emoji-regex@^8.0.0: version "8.0.0" resolved "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz" @@ -3682,15 +4360,20 @@ emoji-regex@^9.2.2: resolved "https://registry.npmjs.org/emoji-regex/-/emoji-regex-9.2.2.tgz" integrity sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg== +emojilib@^2.4.0: + version "2.4.0" + resolved "https://registry.yarnpkg.com/emojilib/-/emojilib-2.4.0.tgz#ac518a8bb0d5f76dda57289ccb2fdf9d39ae721e" + integrity sha512-5U0rVMU5Y2n2+ykNLQqMoqklN9ICBT/KsvC1Gz6vqHbz2AXXGkG+Pm5rMWk/8Vjrr/mY9985Hi8DYzn1F09Nyw== + emojis-list@^3.0.0: version "3.0.0" resolved "https://registry.npmjs.org/emojis-list/-/emojis-list-3.0.0.tgz" integrity sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q== -emoticon@^3.2.0: - version "3.2.0" - resolved "https://registry.npmjs.org/emoticon/-/emoticon-3.2.0.tgz" - integrity sha512-SNujglcLTTg+lDAcApPNgEdudaqQFiAbJCqzjNxJkvN9vAwCGi0uu8IUVvx+f16h+V44KCY6Y2yboroc9pilHg== +emoticon@^4.0.1: + version "4.1.0" + resolved "https://registry.yarnpkg.com/emoticon/-/emoticon-4.1.0.tgz#d5a156868ee173095627a33de3f1e914c3dde79e" + integrity sha512-VWZfnxqwNcc51hIy/sbOdEem6D+cVtpPzEEtVAFdaas30+1dgkyaOQ4sQ6Bp0tOMqWO1v+HQfYaoodOkdhK6SQ== encodeurl@~1.0.2: version "1.0.2" @@ -3702,13 +4385,6 @@ encodeurl@~2.0.0: resolved "https://registry.npmjs.org/encodeurl/-/encodeurl-2.0.0.tgz" integrity sha512-Q0n9HRi4m6JuGIV1eFlmvJB7ZEVxu93IrMyiMsGC0lrMJMWzRgx6WGquyfQgZVb31vhGgXnfmPNNXmxnOkRBrg== -end-of-stream@^1.1.0: - version "1.4.4" - resolved "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.4.4.tgz" - integrity sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q== - dependencies: - once "^1.4.0" - enhanced-resolve@^5.17.1: version "5.17.1" resolved "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-5.17.1.tgz" @@ -3756,15 +4432,35 @@ es-module-lexer@^1.2.1: resolved "https://registry.npmjs.org/es-module-lexer/-/es-module-lexer-1.5.4.tgz" integrity sha512-MVNK56NiMrOwitFB7cqDwq0CQutbw+0BvLshJSse0MUNU+y1FC3bUS/AQg7oUng+/wKrrki7JfmwtVHkVfPLlw== -escalade@^3.2.0: +esast-util-from-estree@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/esast-util-from-estree/-/esast-util-from-estree-2.0.0.tgz#8d1cfb51ad534d2f159dc250e604f3478a79f1ad" + integrity sha512-4CyanoAudUSBAn5K13H4JhsMH6L9ZP7XbLVe/dKybkxMO7eDyLsT8UHl9TRNrU2Gr9nz+FovfSIjuXWJ81uVwQ== + dependencies: + "@types/estree-jsx" "^1.0.0" + devlop "^1.0.0" + estree-util-visit "^2.0.0" + unist-util-position-from-estree "^2.0.0" + +esast-util-from-js@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/esast-util-from-js/-/esast-util-from-js-2.0.1.tgz#5147bec34cc9da44accf52f87f239a40ac3e8225" + integrity sha512-8Ja+rNJ0Lt56Pcf3TAmpBZjmx8ZcK5Ts4cAzIOjsjevg9oSXJnl6SUQ2EevU8tv3h6ZLWmoKL5H4fgWvdvfETw== + dependencies: + "@types/estree-jsx" "^1.0.0" + acorn "^8.0.0" + esast-util-from-estree "^2.0.0" + vfile-message "^4.0.0" + +escalade@^3.1.1, escalade@^3.2.0: version "3.2.0" resolved "https://registry.npmjs.org/escalade/-/escalade-3.2.0.tgz" integrity sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA== -escape-goat@^2.0.0: - version "2.1.1" - resolved "https://registry.npmjs.org/escape-goat/-/escape-goat-2.1.1.tgz" - integrity sha512-8/uIhbG12Csjy2JEW7D9pHbreaVaS/OpN3ycnyvElTdwM5n6GY6W6e2IPemfvGZeUMqZ9A/3GqIZMgKnBhAw/Q== +escape-goat@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/escape-goat/-/escape-goat-4.0.0.tgz#9424820331b510b0666b98f7873fe11ac4aa8081" + integrity sha512-2Sd4ShcWxbx6OY1IHyla/CVNwvg7XwZVoXZHcSu9w9SReNP1EzzD5T8NWKIR38fIqEns9kDWKUQTXXAmlDrdPg== escape-html@^1.0.3, escape-html@~1.0.3: version "1.0.3" @@ -3781,6 +4477,11 @@ escape-string-regexp@^4.0.0: resolved "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz" integrity sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA== +escape-string-regexp@^5.0.0: + version "5.0.0" + resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-5.0.0.tgz#4683126b500b61762f2dbebace1806e8be31b1c8" + integrity sha512-/veY75JbMK4j1yjvuUxuVsiS/hr/4iHs9FTT6cgTexxdE0Ly/glccBAkloH/DofkjRbZU3bnoj38mOmhkZ0lHw== + eslint-scope@5.1.1: version "5.1.1" resolved "https://registry.npmjs.org/eslint-scope/-/eslint-scope-5.1.1.tgz" @@ -3811,15 +4512,76 @@ estraverse@^5.2.0: resolved "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz" integrity sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA== +estree-util-attach-comments@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/estree-util-attach-comments/-/estree-util-attach-comments-3.0.0.tgz#344bde6a64c8a31d15231e5ee9e297566a691c2d" + integrity sha512-cKUwm/HUcTDsYh/9FgnuFqpfquUbwIqwKM26BVCGDPVgvaCl/nDCCjUfiLlx6lsEZ3Z4RFxNbOQ60pkaEwFxGw== + dependencies: + "@types/estree" "^1.0.0" + +estree-util-build-jsx@^3.0.0: + version "3.0.1" + resolved "https://registry.yarnpkg.com/estree-util-build-jsx/-/estree-util-build-jsx-3.0.1.tgz#b6d0bced1dcc4f06f25cf0ceda2b2dcaf98168f1" + integrity sha512-8U5eiL6BTrPxp/CHbs2yMgP8ftMhR5ww1eIKoWRMlqvltHF8fZn5LRDvTKuxD3DUn+shRbLGqXemcP51oFCsGQ== + dependencies: + "@types/estree-jsx" "^1.0.0" + devlop "^1.0.0" + estree-util-is-identifier-name "^3.0.0" + estree-walker "^3.0.0" + +estree-util-is-identifier-name@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/estree-util-is-identifier-name/-/estree-util-is-identifier-name-3.0.0.tgz#0b5ef4c4ff13508b34dcd01ecfa945f61fce5dbd" + integrity sha512-hFtqIDZTIUZ9BXLb8y4pYGyk6+wekIivNVTcmvk8NoOh+VeRn5y6cEHzbURrWbfp1fIqdVipilzj+lfaadNZmg== + +estree-util-scope@^1.0.0: + version "1.0.0" + resolved "https://registry.yarnpkg.com/estree-util-scope/-/estree-util-scope-1.0.0.tgz#9cbdfc77f5cb51e3d9ed4ad9c4adbff22d43e585" + integrity sha512-2CAASclonf+JFWBNJPndcOpA8EMJwa0Q8LUFJEKqXLW6+qBvbFZuF5gItbQOs/umBUkjviCSDCbBwU2cXbmrhQ== + dependencies: + "@types/estree" "^1.0.0" + devlop "^1.0.0" + +estree-util-to-js@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/estree-util-to-js/-/estree-util-to-js-2.0.0.tgz#10a6fb924814e6abb62becf0d2bc4dea51d04f17" + integrity sha512-WDF+xj5rRWmD5tj6bIqRi6CkLIXbbNQUcxQHzGysQzvHmdYG2G7p/Tf0J0gpxGgkeMZNTIjT/AoSvC9Xehcgdg== + dependencies: + "@types/estree-jsx" "^1.0.0" + astring "^1.8.0" + source-map "^0.7.0" + +estree-util-value-to-estree@^3.0.1: + version "3.2.1" + resolved "https://registry.yarnpkg.com/estree-util-value-to-estree/-/estree-util-value-to-estree-3.2.1.tgz#f8083e56f51efb4889794490730c036ba6167ee6" + integrity sha512-Vt2UOjyPbNQQgT5eJh+K5aATti0OjCIAGc9SgMdOFYbohuifsWclR74l0iZTJwePMgWYdX1hlVS+dedH9XV8kw== + dependencies: + "@types/estree" "^1.0.0" + +estree-util-visit@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/estree-util-visit/-/estree-util-visit-2.0.0.tgz#13a9a9f40ff50ed0c022f831ddf4b58d05446feb" + integrity sha512-m5KgiH85xAhhW8Wta0vShLcUvOsh3LLPI2YVwcbio1l7E09NTLL1EyMZFM1OyWowoH0skScNbhOPl4kcBgzTww== + dependencies: + "@types/estree-jsx" "^1.0.0" + "@types/unist" "^3.0.0" + +estree-walker@^3.0.0: + version "3.0.3" + resolved "https://registry.yarnpkg.com/estree-walker/-/estree-walker-3.0.3.tgz#67c3e549ec402a487b4fc193d1953a524752340d" + integrity sha512-7RUKfXgSMMkzt6ZuXmqapOurLGPPfgj6l9uRZ7lRGolvk0y2yocc35LdcxKC5PQZdn2DMqioAQ2NoWcrTKmm6g== + dependencies: + "@types/estree" "^1.0.0" + esutils@^2.0.2: version "2.0.3" resolved "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz" integrity sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g== -eta@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/eta/-/eta-2.0.0.tgz" - integrity sha512-NqE7S2VmVwgMS8yBxsH4VgNQjNjLq1gfGU0u9I6Cjh468nPRMoDfGdK9n1p/3Dvsw3ebklDkZsFAnKJ9sefjBA== +eta@^2.2.0: + version "2.2.0" + resolved "https://registry.yarnpkg.com/eta/-/eta-2.2.0.tgz#eb8b5f8c4e8b6306561a455e62cd7492fe3a9b8a" + integrity sha512-UVQ72Rqjy/ZKQalzV5dCCJP80GrmPrMxh6NlNf+erV6ObL0ZFkhCstWRawS85z3smdr3d2wXPsZEY7rDPfGd2g== etag@~1.8.1: version "1.8.1" @@ -3929,12 +4691,10 @@ fast-json-stable-stringify@^2.0.0: resolved "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz" integrity sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw== -fast-url-parser@1.1.3: - version "1.1.3" - resolved "https://registry.npmjs.org/fast-url-parser/-/fast-url-parser-1.1.3.tgz" - integrity sha512-5jOCVXADYNuRkKFzNJ0dCCewsZiYo0dz8QNYljkOpFC6r2U4OBmKtvm/Tsuh4w1YYdDqDb31a8TVhBJ2OJKdqQ== - dependencies: - punycode "^1.3.2" +fast-uri@^3.0.1: + version "3.0.3" + resolved "https://registry.yarnpkg.com/fast-uri/-/fast-uri-3.0.3.tgz#892a1c91802d5d7860de728f18608a0573142241" + integrity sha512-aLrHthzCjH5He4Z2H9YZ+v6Ujb9ocRuW6ZzkJQOrTxleEijANq4v1TsaPaVG1PZcuurEzrLcWRyYBYXD5cEiaw== fastq@^1.6.0: version "1.15.0" @@ -3943,6 +4703,13 @@ fastq@^1.6.0: dependencies: reusify "^1.0.4" +fault@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/fault/-/fault-2.0.1.tgz#d47ca9f37ca26e4bd38374a7c500b5a384755b6c" + integrity sha512-WtySTkS4OKev5JtpHXnib4Gxiurzh5NCGvWrFaZ34m6JehfTUhKZvn9njTfw48t6JumVQOmrKqpmGcdwxnhqBQ== + dependencies: + format "^0.2.0" + faye-websocket@^0.11.3: version "0.11.4" resolved "https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.11.4.tgz" @@ -3950,31 +4717,6 @@ faye-websocket@^0.11.3: dependencies: websocket-driver ">=0.5.1" -fbemitter@^3.0.0: - version "3.0.0" - resolved "https://registry.npmjs.org/fbemitter/-/fbemitter-3.0.0.tgz" - integrity sha512-KWKaceCwKQU0+HPoop6gn4eOHk50bBv/VxjJtGMfwmJt3D29JpN4H4eisCtIPA+a8GVBam+ldMMpMjJUvpDyHw== - dependencies: - fbjs "^3.0.0" - -fbjs-css-vars@^1.0.0: - version "1.0.2" - resolved "https://registry.npmjs.org/fbjs-css-vars/-/fbjs-css-vars-1.0.2.tgz" - integrity sha512-b2XGFAFdWZWg0phtAWLHCk836A1Xann+I+Dgd3Gk64MHKZO44FfoD1KxyvbSh0qZsIoXQGGlVztIY+oitJPpRQ== - -fbjs@^3.0.0, fbjs@^3.0.1: - version "3.0.4" - resolved "https://registry.npmjs.org/fbjs/-/fbjs-3.0.4.tgz" - integrity sha512-ucV0tDODnGV3JCnnkmoszb5lf4bNpzjv80K41wd4k798Etq+UYD0y0TIfalLjZoKgjive6/adkRnszwapiDgBQ== - dependencies: - cross-fetch "^3.1.5" - fbjs-css-vars "^1.0.0" - loose-envify "^1.0.0" - object-assign "^4.1.0" - promise "^7.1.1" - setimmediate "^1.0.5" - ua-parser-js "^0.7.30" - feed@^4.2.2: version "4.2.2" resolved "https://registry.npmjs.org/feed/-/feed-4.2.2.tgz" @@ -3982,6 +4724,13 @@ feed@^4.2.2: dependencies: xml-js "^1.6.11" +figures@^3.2.0: + version "3.2.0" + resolved "https://registry.yarnpkg.com/figures/-/figures-3.2.0.tgz#625c18bd293c604dc4a8ddb2febf0c88341746af" + integrity sha512-yaduQFRKLXYOGgEn6AZau90j3ggSOyiqXU0F9JZfeXYhNa+Jk4X+s45A2zg5jns87GAFa34BBm2kXw4XpNcbdg== + dependencies: + escape-string-regexp "^1.0.5" + file-loader@^6.2.0: version "6.2.0" resolved "https://registry.npmjs.org/file-loader/-/file-loader-6.2.0.tgz" @@ -4015,7 +4764,7 @@ finalhandler@1.3.1: statuses "2.0.1" unpipe "~1.0.0" -find-cache-dir@^3.3.1, find-cache-dir@^3.3.2: +find-cache-dir@^3.3.2: version "3.3.2" resolved "https://registry.npmjs.org/find-cache-dir/-/find-cache-dir-3.3.2.tgz" integrity sha512-wXZV5emFEjrridIgED11OoUKLxiYjAcqot/NJdAkOhlJ+vGzwhOAfcG5OX1jP+S0PcjEn8bdMJv+g2jwQ3Onig== @@ -4024,6 +4773,14 @@ find-cache-dir@^3.3.1, find-cache-dir@^3.3.2: make-dir "^3.0.2" pkg-dir "^4.1.0" +find-cache-dir@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/find-cache-dir/-/find-cache-dir-4.0.0.tgz#a30ee0448f81a3990708f6453633c733e2f6eec2" + integrity sha512-9ZonPT4ZAK4a+1pUPVPZJapbi7O5qbbJPdYw/NOQWZZbVLdDTYM3A4R9z/DpAM08IDaFGsvPgiGZ82WEwUDWjg== + dependencies: + common-path-prefix "^3.0.0" + pkg-dir "^7.0.0" + find-up@^3.0.0: version "3.0.0" resolved "https://registry.npmjs.org/find-up/-/find-up-3.0.0.tgz" @@ -4055,15 +4812,12 @@ find-up@^6.1.0, find-up@^6.3.0: locate-path "^7.1.0" path-exists "^5.0.0" -flux@^4.0.1: - version "4.0.3" - resolved "https://registry.npmjs.org/flux/-/flux-4.0.3.tgz" - integrity sha512-yKAbrp7JhZhj6uiT1FTuVMlIAT1J4jqEyBpFApi1kxpGZCvacMVc/t1pMQyotqHhAgvoE3bNvAykhCo2CLjnYw== - dependencies: - fbemitter "^3.0.0" - fbjs "^3.0.1" +flat@^5.0.2: + version "5.0.2" + resolved "https://registry.yarnpkg.com/flat/-/flat-5.0.2.tgz#8ca6fe332069ffa9d324c327198c598259ceb241" + integrity sha512-b6suED+5/3rTpUBdG1gupIl8MPFCAMA0QXwmljLhvCUKcUvdE4gWky9zpuGCcXHOsz4J9wPGNWq6OKpmIzz3hQ== -follow-redirects@^1.0.0, follow-redirects@^1.14.7: +follow-redirects@^1.0.0: version "1.15.9" resolved "https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.15.9.tgz" integrity sha512-gew4GsXizNgdoRyqmyfMHyAmXsZDk6mHkSxZFCzW9gwlbtOW44CDtYavM+y+72qD/Vq2l550kMF52DT8fOLJqQ== @@ -4087,15 +4841,25 @@ fork-ts-checker-webpack-plugin@^6.5.0: semver "^7.3.2" tapable "^1.0.0" +form-data-encoder@^2.1.2: + version "2.1.4" + resolved "https://registry.yarnpkg.com/form-data-encoder/-/form-data-encoder-2.1.4.tgz#261ea35d2a70d48d30ec7a9603130fa5515e9cd5" + integrity sha512-yDYSgNMraqvnxiEXO4hi88+YZxaHC6QKzb5N84iRCTDeRO7ZALpir/lVmf/uXUhnwUr2O4HU8s/n6x+yNjQkHw== + +format@^0.2.0: + version "0.2.2" + resolved "https://registry.yarnpkg.com/format/-/format-0.2.2.tgz#d6170107e9efdc4ed30c9dc39016df942b5cb58b" + integrity sha512-wzsgA6WOq+09wrU1tsJ09udeR/YZRaeArL9e1wPbFg3GG2yDnC2ldKpxs4xunpFF9DgqCqOIra3bc1HWrJ37Ww== + forwarded@0.2.0: version "0.2.0" resolved "https://registry.npmjs.org/forwarded/-/forwarded-0.2.0.tgz" integrity sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow== -fraction.js@^4.2.0: - version "4.2.0" - resolved "https://registry.npmjs.org/fraction.js/-/fraction.js-4.2.0.tgz" - integrity sha512-MhLuK+2gUcnZe8ZHlaaINnQLl0xRIGRfcGk2yl8xoQAfHrSsL3rYu6FCmBdkdbhc9EPlwyGHewaRsvwRMJtAlA== +fraction.js@^4.3.7: + version "4.3.7" + resolved "https://registry.yarnpkg.com/fraction.js/-/fraction.js-4.3.7.tgz#06ca0085157e42fda7f9e726e79fefc4068840f7" + integrity sha512-ZsDfxO51wGAXREY55a7la9LScWpwv9RxIrYABrlvOFBlH/ShPnrtsXeuUIfXKKOVicNxQ+o8JTbJvjS4M89yew== fresh@0.5.2: version "0.5.2" @@ -4111,6 +4875,15 @@ fs-extra@^10.1.0: jsonfile "^6.0.1" universalify "^2.0.0" +fs-extra@^11.1.1, fs-extra@^11.2.0: + version "11.2.0" + resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-11.2.0.tgz#e70e17dfad64232287d01929399e0ea7c86b0e5b" + integrity sha512-PmDi3uwK5nFuXh7XDTlVnS17xJS7vW36is2+w3xcv8SVxiB4NyATf4ctkVY5bkSjX0Y4nbvZCq1/EjtEyr9ktw== + dependencies: + graceful-fs "^4.2.0" + jsonfile "^6.0.1" + universalify "^2.0.0" + fs-extra@^9.0.0: version "9.1.0" resolved "https://registry.npmjs.org/fs-extra/-/fs-extra-9.1.0.tgz" @@ -4141,7 +4914,7 @@ function-bind@^1.1.1, function-bind@^1.1.2: resolved "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz" integrity sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA== -gensync@^1.0.0-beta.1, gensync@^1.0.0-beta.2: +gensync@^1.0.0-beta.2: version "1.0.0-beta.2" resolved "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz" integrity sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg== @@ -4162,28 +4935,14 @@ get-own-enumerable-property-symbols@^3.0.0: resolved "https://registry.npmjs.org/get-own-enumerable-property-symbols/-/get-own-enumerable-property-symbols-3.0.2.tgz" integrity sha512-I0UBV/XOz1XkIJHEUDMZAbzCThU/H8DxmSfmdGcKPnVhu2VfFqr34jr9777IyaTYvxjedWhqVIilEDsCdP5G6g== -get-stream@^4.1.0: - version "4.1.0" - resolved "https://registry.npmjs.org/get-stream/-/get-stream-4.1.0.tgz" - integrity sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w== - dependencies: - pump "^3.0.0" - -get-stream@^5.1.0: - version "5.2.0" - resolved "https://registry.npmjs.org/get-stream/-/get-stream-5.2.0.tgz" - integrity sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA== - dependencies: - pump "^3.0.0" - -get-stream@^6.0.0: +get-stream@^6.0.0, get-stream@^6.0.1: version "6.0.1" resolved "https://registry.npmjs.org/get-stream/-/get-stream-6.0.1.tgz" integrity sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg== -github-slugger@^1.4.0: +github-slugger@^1.5.0: version "1.5.0" - resolved "https://registry.npmjs.org/github-slugger/-/github-slugger-1.5.0.tgz" + resolved "https://registry.yarnpkg.com/github-slugger/-/github-slugger-1.5.0.tgz#17891bbc73232051474d68bd867a34625c955f7d" integrity sha512-wIh+gKBI9Nshz2o46B0B3f5k/W+WI9ZAv6y5Dn5WJ5SK1t0TnDimB4WE5rmTD05ZAIn8HALCZVmCsvj0w0v0lw== glob-parent@^5.1.2, glob-parent@~5.1.2: @@ -4275,22 +5034,27 @@ gopd@^1.0.1: dependencies: get-intrinsic "^1.1.3" -got@^9.6.0: - version "9.6.0" - resolved "https://registry.npmjs.org/got/-/got-9.6.0.tgz" - integrity sha512-R7eWptXuGYxwijs0eV+v3o6+XH1IqVK8dJOEecQfTmkncw9AV4dcw/Dhxi8MdlqPthxxpZyizMzyg8RTmEsG+Q== - dependencies: - "@sindresorhus/is" "^0.14.0" - "@szmarczak/http-timer" "^1.1.2" - cacheable-request "^6.0.0" - decompress-response "^3.3.0" - duplexer3 "^0.1.4" - get-stream "^4.1.0" - lowercase-keys "^1.0.1" - mimic-response "^1.0.1" - p-cancelable "^1.0.0" - to-readable-stream "^1.0.0" - url-parse-lax "^3.0.0" +got@^12.1.0: + version "12.6.1" + resolved "https://registry.yarnpkg.com/got/-/got-12.6.1.tgz#8869560d1383353204b5a9435f782df9c091f549" + integrity sha512-mThBblvlAF1d4O5oqyvN+ZxLAYwIJK7bpMxgYqPD9okW0C3qm5FFn7k811QrcuEBwaogR3ngOFoCfs6mRv7teQ== + dependencies: + "@sindresorhus/is" "^5.2.0" + "@szmarczak/http-timer" "^5.0.1" + cacheable-lookup "^7.0.0" + cacheable-request "^10.2.8" + decompress-response "^6.0.0" + form-data-encoder "^2.1.2" + get-stream "^6.0.1" + http2-wrapper "^2.1.10" + lowercase-keys "^3.0.0" + p-cancelable "^3.0.0" + responselike "^3.0.0" + +graceful-fs@4.2.10: + version "4.2.10" + resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.10.tgz#147d3a006da4ca3ce14728c7aefc287c367d7a6c" + integrity sha512-9ByhssR2fPVsNZj478qUUbKfmL0+t5BDVyjShtyZZLiK7ZDAArFFfopyOTj0M05wE2tJPisA4iTnnXl2YoPvOA== graceful-fs@^4.1.2, graceful-fs@^4.1.6, graceful-fs@^4.2.0, graceful-fs@^4.2.11, graceful-fs@^4.2.4, graceful-fs@^4.2.6, graceful-fs@^4.2.9: version "4.2.11" @@ -4346,10 +5110,10 @@ has-symbols@^1.0.3: resolved "https://registry.npmjs.org/has-symbols/-/has-symbols-1.0.3.tgz" integrity sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A== -has-yarn@^2.1.0: - version "2.1.0" - resolved "https://registry.npmjs.org/has-yarn/-/has-yarn-2.1.0.tgz" - integrity sha512-UqBRqi4ju7T+TqGNdqAO0PaSVGsDGJUBQvk9eUWNGRY1CFGDzYhLWoM7JQEemnlvVcv/YEmc2wNW8BC24EnUsw== +has-yarn@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/has-yarn/-/has-yarn-3.0.0.tgz#c3c21e559730d1d3b57e28af1f30d06fac38147d" + integrity sha512-IrsVwUHhEULx3R8f/aA8AHuEzAorplsab/v8HBzEiIukwq5i/EC+xmOW+HfP1OaDP+2JkgT1yILHN2O3UFIbcA== has@^1.0.3: version "1.0.3" @@ -4365,73 +5129,119 @@ hasown@^2.0.0: dependencies: function-bind "^1.1.2" -hast-to-hyperscript@^9.0.0: - version "9.0.1" - resolved "https://registry.npmjs.org/hast-to-hyperscript/-/hast-to-hyperscript-9.0.1.tgz" - integrity sha512-zQgLKqF+O2F72S1aa4y2ivxzSlko3MAvxkwG8ehGmNiqd98BIN3JM1rAJPmplEyLmGLO2QZYJtIneOSZ2YbJuA== - dependencies: - "@types/unist" "^2.0.3" - comma-separated-tokens "^1.0.0" - property-information "^5.3.0" - space-separated-tokens "^1.0.0" - style-to-object "^0.3.0" - unist-util-is "^4.0.0" - web-namespaces "^1.0.0" - -hast-util-from-parse5@^6.0.0: - version "6.0.1" - resolved "https://registry.npmjs.org/hast-util-from-parse5/-/hast-util-from-parse5-6.0.1.tgz" - integrity sha512-jeJUWiN5pSxW12Rh01smtVkZgZr33wBokLzKLwinYOUfSzm1Nl/c3GUGebDyOKjdsRgMvoVbV0VpAcpjF4NrJA== - dependencies: - "@types/parse5" "^5.0.0" - hastscript "^6.0.0" - property-information "^5.0.0" - vfile "^4.0.0" - vfile-location "^3.2.0" - web-namespaces "^1.0.0" - -hast-util-parse-selector@^2.0.0: - version "2.2.5" - resolved "https://registry.npmjs.org/hast-util-parse-selector/-/hast-util-parse-selector-2.2.5.tgz" - integrity sha512-7j6mrk/qqkSehsM92wQjdIgWM2/BW61u/53G6xmC8i1OmEdKLHbk419QKQUjz6LglWsfqoiHmyMRkP1BGjecNQ== - -hast-util-raw@6.0.1: - version "6.0.1" - resolved "https://registry.npmjs.org/hast-util-raw/-/hast-util-raw-6.0.1.tgz" - integrity sha512-ZMuiYA+UF7BXBtsTBNcLBF5HzXzkyE6MLzJnL605LKE8GJylNjGc4jjxazAHUtcwT5/CEt6afRKViYB4X66dig== - dependencies: - "@types/hast" "^2.0.0" - hast-util-from-parse5 "^6.0.0" - hast-util-to-parse5 "^6.0.0" - html-void-elements "^1.0.0" - parse5 "^6.0.0" - unist-util-position "^3.0.0" - vfile "^4.0.0" - web-namespaces "^1.0.0" - xtend "^4.0.0" - zwitch "^1.0.0" - -hast-util-to-parse5@^6.0.0: - version "6.0.0" - resolved "https://registry.npmjs.org/hast-util-to-parse5/-/hast-util-to-parse5-6.0.0.tgz" - integrity sha512-Lu5m6Lgm/fWuz8eWnrKezHtVY83JeRGaNQ2kn9aJgqaxvVkFCZQBEhgodZUDUvoodgyROHDb3r5IxAEdl6suJQ== +hast-util-from-parse5@^8.0.0: + version "8.0.2" + resolved "https://registry.yarnpkg.com/hast-util-from-parse5/-/hast-util-from-parse5-8.0.2.tgz#29b42758ba96535fd6021f0f533c000886c0f00f" + integrity sha512-SfMzfdAi/zAoZ1KkFEyyeXBn7u/ShQrfd675ZEE9M3qj+PMFX05xubzRyF76CCSJu8au9jgVxDV1+okFvgZU4A== + dependencies: + "@types/hast" "^3.0.0" + "@types/unist" "^3.0.0" + devlop "^1.0.0" + hastscript "^9.0.0" + property-information "^6.0.0" + vfile "^6.0.0" + vfile-location "^5.0.0" + web-namespaces "^2.0.0" + +hast-util-parse-selector@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/hast-util-parse-selector/-/hast-util-parse-selector-4.0.0.tgz#352879fa86e25616036037dd8931fb5f34cb4a27" + integrity sha512-wkQCkSYoOGCRKERFWcxMVMOcYE2K1AaNLU8DXS9arxnLOUEWbOXKXiJUNzEpqZ3JOKpnha3jkFrumEjVliDe7A== dependencies: - hast-to-hyperscript "^9.0.0" - property-information "^5.0.0" - web-namespaces "^1.0.0" - xtend "^4.0.0" - zwitch "^1.0.0" + "@types/hast" "^3.0.0" -hastscript@^6.0.0: - version "6.0.0" - resolved "https://registry.npmjs.org/hastscript/-/hastscript-6.0.0.tgz" - integrity sha512-nDM6bvd7lIqDUiYEiu5Sl/+6ReP0BMk/2f4U/Rooccxkj0P5nm+acM5PrGJ/t5I8qPGiqZSE6hVAwZEdZIvP4w== +hast-util-raw@^9.0.0: + version "9.1.0" + resolved "https://registry.yarnpkg.com/hast-util-raw/-/hast-util-raw-9.1.0.tgz#79b66b26f6f68fb50dfb4716b2cdca90d92adf2e" + integrity sha512-Y8/SBAHkZGoNkpzqqfCldijcuUKh7/su31kEBp67cFY09Wy0mTRgtsLYsiIxMJxlu0f6AA5SUTbDR8K0rxnbUw== + dependencies: + "@types/hast" "^3.0.0" + "@types/unist" "^3.0.0" + "@ungap/structured-clone" "^1.0.0" + hast-util-from-parse5 "^8.0.0" + hast-util-to-parse5 "^8.0.0" + html-void-elements "^3.0.0" + mdast-util-to-hast "^13.0.0" + parse5 "^7.0.0" + unist-util-position "^5.0.0" + unist-util-visit "^5.0.0" + vfile "^6.0.0" + web-namespaces "^2.0.0" + zwitch "^2.0.0" + +hast-util-to-estree@^3.0.0: + version "3.1.0" + resolved "https://registry.yarnpkg.com/hast-util-to-estree/-/hast-util-to-estree-3.1.0.tgz#f2afe5e869ddf0cf690c75f9fc699f3180b51b19" + integrity sha512-lfX5g6hqVh9kjS/B9E2gSkvHH4SZNiQFiqWS0x9fENzEl+8W12RqdRxX6d/Cwxi30tPQs3bIO+aolQJNp1bIyw== + dependencies: + "@types/estree" "^1.0.0" + "@types/estree-jsx" "^1.0.0" + "@types/hast" "^3.0.0" + comma-separated-tokens "^2.0.0" + devlop "^1.0.0" + estree-util-attach-comments "^3.0.0" + estree-util-is-identifier-name "^3.0.0" + hast-util-whitespace "^3.0.0" + mdast-util-mdx-expression "^2.0.0" + mdast-util-mdx-jsx "^3.0.0" + mdast-util-mdxjs-esm "^2.0.0" + property-information "^6.0.0" + space-separated-tokens "^2.0.0" + style-to-object "^0.4.0" + unist-util-position "^5.0.0" + zwitch "^2.0.0" + +hast-util-to-jsx-runtime@^2.0.0: + version "2.3.2" + resolved "https://registry.yarnpkg.com/hast-util-to-jsx-runtime/-/hast-util-to-jsx-runtime-2.3.2.tgz#6d11b027473e69adeaa00ca4cfb5bb68e3d282fa" + integrity sha512-1ngXYb+V9UT5h+PxNRa1O1FYguZK/XL+gkeqvp7EdHlB9oHUG0eYRo/vY5inBdcqo3RkPMC58/H94HvkbfGdyg== + dependencies: + "@types/estree" "^1.0.0" + "@types/hast" "^3.0.0" + "@types/unist" "^3.0.0" + comma-separated-tokens "^2.0.0" + devlop "^1.0.0" + estree-util-is-identifier-name "^3.0.0" + hast-util-whitespace "^3.0.0" + mdast-util-mdx-expression "^2.0.0" + mdast-util-mdx-jsx "^3.0.0" + mdast-util-mdxjs-esm "^2.0.0" + property-information "^6.0.0" + space-separated-tokens "^2.0.0" + style-to-object "^1.0.0" + unist-util-position "^5.0.0" + vfile-message "^4.0.0" + +hast-util-to-parse5@^8.0.0: + version "8.0.0" + resolved "https://registry.yarnpkg.com/hast-util-to-parse5/-/hast-util-to-parse5-8.0.0.tgz#477cd42d278d4f036bc2ea58586130f6f39ee6ed" + integrity sha512-3KKrV5ZVI8if87DVSi1vDeByYrkGzg4mEfeu4alwgmmIeARiBLKCZS2uw5Gb6nU9x9Yufyj3iudm6i7nl52PFw== + dependencies: + "@types/hast" "^3.0.0" + comma-separated-tokens "^2.0.0" + devlop "^1.0.0" + property-information "^6.0.0" + space-separated-tokens "^2.0.0" + web-namespaces "^2.0.0" + zwitch "^2.0.0" + +hast-util-whitespace@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/hast-util-whitespace/-/hast-util-whitespace-3.0.0.tgz#7778ed9d3c92dd9e8c5c8f648a49c21fc51cb621" + integrity sha512-88JUN06ipLwsnv+dVn+OIYOvAuvBMy/Qoi6O7mQHxdPXpjy+Cd6xRkWwux7DKO+4sYILtLBRIKgsdpS2gQc7qw== + dependencies: + "@types/hast" "^3.0.0" + +hastscript@^9.0.0: + version "9.0.0" + resolved "https://registry.yarnpkg.com/hastscript/-/hastscript-9.0.0.tgz#2b76b9aa3cba8bf6d5280869f6f6f7165c230763" + integrity sha512-jzaLBGavEDKHrc5EfFImKN7nZKKBdSLIdGvCwDZ9TfzbF2ffXiov8CKE445L2Z1Ek2t/m4SKQ2j6Ipv7NyUolw== dependencies: - "@types/hast" "^2.0.0" - comma-separated-tokens "^1.0.0" - hast-util-parse-selector "^2.0.0" - property-information "^5.0.0" - space-separated-tokens "^1.0.0" + "@types/hast" "^3.0.0" + comma-separated-tokens "^2.0.0" + hast-util-parse-selector "^4.0.0" + property-information "^6.0.0" + space-separated-tokens "^2.0.0" he@^1.2.0: version "1.2.0" @@ -4472,7 +5282,12 @@ html-entities@^2.3.2: resolved "https://registry.npmjs.org/html-entities/-/html-entities-2.3.3.tgz" integrity sha512-DV5Ln36z34NNTDgnz0EWGBLZENelNAtkiFA4kyNOG2tDI6Mz1uSWiq1wAKdyjnJwyDiDO7Fa2SO1CTxPXL8VxA== -html-minifier-terser@^6.0.2, html-minifier-terser@^6.1.0: +html-escaper@^2.0.2: + version "2.0.2" + resolved "https://registry.yarnpkg.com/html-escaper/-/html-escaper-2.0.2.tgz#dfd60027da36a36dfcbe236262c00a5822681453" + integrity sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg== + +html-minifier-terser@^6.0.2: version "6.1.0" resolved "https://registry.npmjs.org/html-minifier-terser/-/html-minifier-terser-6.1.0.tgz" integrity sha512-YXxSlJBZTP7RS3tWnQw74ooKa6L9b9i9QYXY21eUEvhZ3u9XLfv6OnFsQq6RxkhHygsaUMvYsZRV5rU/OVNZxw== @@ -4485,20 +5300,33 @@ html-minifier-terser@^6.0.2, html-minifier-terser@^6.1.0: relateurl "^0.2.7" terser "^5.10.0" -html-tags@^3.2.0: - version "3.2.0" - resolved "https://registry.npmjs.org/html-tags/-/html-tags-3.2.0.tgz" - integrity sha512-vy7ClnArOZwCnqZgvv+ddgHgJiAFXe3Ge9ML5/mBctVJoUoYPCdxVucOywjDARn6CVoh3dRSFdPHy2sX80L0Wg== +html-minifier-terser@^7.2.0: + version "7.2.0" + resolved "https://registry.yarnpkg.com/html-minifier-terser/-/html-minifier-terser-7.2.0.tgz#18752e23a2f0ed4b0f550f217bb41693e975b942" + integrity sha512-tXgn3QfqPIpGl9o+K5tpcj3/MN4SfLtsx2GWwBC3SSd0tXQGyF3gsSqad8loJgKZGM3ZxbYDd5yhiBIdWpmvLA== + dependencies: + camel-case "^4.1.2" + clean-css "~5.3.2" + commander "^10.0.0" + entities "^4.4.0" + param-case "^3.0.4" + relateurl "^0.2.7" + terser "^5.15.1" -html-void-elements@^1.0.0: - version "1.0.5" - resolved "https://registry.npmjs.org/html-void-elements/-/html-void-elements-1.0.5.tgz" - integrity sha512-uE/TxKuyNIcx44cIWnjr/rfIATDH7ZaOMmstu0CwhFG1Dunhlp4OC6/NMbhiwoq5BpW0ubi303qnEk/PZj614w== +html-tags@^3.3.1: + version "3.3.1" + resolved "https://registry.yarnpkg.com/html-tags/-/html-tags-3.3.1.tgz#a04026a18c882e4bba8a01a3d39cfe465d40b5ce" + integrity sha512-ztqyC3kLto0e9WbNp0aeP+M3kTt+nbaIveGmUxAtZa+8iFgKLUOD4YKM5j+f3QD89bra7UeumolZHKuOXnTmeQ== -html-webpack-plugin@^5.5.0: - version "5.5.0" - resolved "https://registry.npmjs.org/html-webpack-plugin/-/html-webpack-plugin-5.5.0.tgz" - integrity sha512-sy88PC2cRTVxvETRgUHFrL4No3UxvcH8G1NepGhqaTT+GXN2kTamqasot0inS5hXeg1cMbFDt27zzo9p35lZVw== +html-void-elements@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/html-void-elements/-/html-void-elements-3.0.0.tgz#fc9dbd84af9e747249034d4d62602def6517f1d7" + integrity sha512-bEqo66MRXsUGxWHV5IP0PUiAWwoEjba4VCzg0LjFJBpchPaTfyfCKTG6bc5F8ucKec3q5y6qOdGyYTSBEvhCrg== + +html-webpack-plugin@^5.6.0: + version "5.6.3" + resolved "https://registry.yarnpkg.com/html-webpack-plugin/-/html-webpack-plugin-5.6.3.tgz#a31145f0fee4184d53a794f9513147df1e653685" + integrity sha512-QSf1yjtSAsmf7rYBV7XX86uua4W/vkhIt0xNXKbsi2foEeW7vjJQz4bhnpL3xH+l1ryl1680uNv968Z+X6jSYg== dependencies: "@types/html-minifier-terser" "^6.0.0" html-minifier-terser "^6.0.2" @@ -4526,9 +5354,9 @@ htmlparser2@^8.0.1: domutils "^3.0.1" entities "^4.3.0" -http-cache-semantics@^4.0.0: +http-cache-semantics@^4.1.1: version "4.1.1" - resolved "https://registry.npmjs.org/http-cache-semantics/-/http-cache-semantics-4.1.1.tgz" + resolved "https://registry.yarnpkg.com/http-cache-semantics/-/http-cache-semantics-4.1.1.tgz#abe02fcb2985460bf0323be664436ec3476a6d5a" integrity sha512-er295DKPVsV82j5kw1Gjt+ADA/XYHsajl82cGNQG2eyoPkvgUhX+nDIyelzhIWbbsXP39EHcI6l5tYs2FYqYXQ== http-deceiver@^1.2.7: @@ -4582,6 +5410,14 @@ http-proxy@^1.18.1: follow-redirects "^1.0.0" requires-port "^1.0.0" +http2-wrapper@^2.1.10: + version "2.2.1" + resolved "https://registry.yarnpkg.com/http2-wrapper/-/http2-wrapper-2.2.1.tgz#310968153dcdedb160d8b72114363ef5fce1f64a" + integrity sha512-V5nVw1PAOgfI3Lmeaj2Exmeg7fenjhRUgz1lPSezy1CuhPYbgQtbQj4jZfEAEMlaL+vupsvhjqCyjzob0yxsmQ== + dependencies: + quick-lru "^5.1.1" + resolve-alpn "^1.2.0" + human-signals@^2.1.0: version "2.1.0" resolved "https://registry.npmjs.org/human-signals/-/human-signals-2.1.0.tgz" @@ -4604,10 +5440,10 @@ ignore@^5.2.0: resolved "https://registry.npmjs.org/ignore/-/ignore-5.2.4.tgz" integrity sha512-MAb38BcSbH0eHNBxn7ql2NH/kX33OkB3lZ1BNdh7ENeRChHTYsTvWrMubiIAMNS2llXEEgZ1MUOBtXChP3kaFQ== -image-size@^1.0.1: - version "1.0.2" - resolved "https://registry.npmjs.org/image-size/-/image-size-1.0.2.tgz" - integrity sha512-xfOoWjceHntRb3qFCrh5ZFORYH8XCdYpASltMhZ/Q0KZiOwjdE/Yl2QCiWdwD+lygV5bMCvauzgu5PxBX/Yerg== +image-size@^1.0.2: + version "1.2.0" + resolved "https://registry.yarnpkg.com/image-size/-/image-size-1.2.0.tgz#312af27a2ff4ff58595ad00b9344dd684c910df6" + integrity sha512-4S8fwbO6w3GeCVN6OPtA9I5IGKkcDMPcKndtUlpJuCwu7JLjtj7JZpwqLuyY2nrmQT3AWsCJLSKPsc2mPBSl3w== dependencies: queue "6.0.2" @@ -4616,7 +5452,7 @@ immer@^9.0.7: resolved "https://registry.npmjs.org/immer/-/immer-9.0.19.tgz" integrity sha512-eY+Y0qcsB4TZKwgQzLaE/lqYMlKhv5J9dyd2RhhtGhNo2njPXDqU9XPfcNfa3MIDsdtZt5KlkIsirlo4dHsWdQ== -import-fresh@^3.1.0, import-fresh@^3.2.1, import-fresh@^3.3.0: +import-fresh@^3.1.0, import-fresh@^3.3.0: version "3.3.0" resolved "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz" integrity sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw== @@ -4624,10 +5460,10 @@ import-fresh@^3.1.0, import-fresh@^3.2.1, import-fresh@^3.3.0: parent-module "^1.0.0" resolve-from "^4.0.0" -import-lazy@^2.1.0: - version "2.1.0" - resolved "https://registry.npmjs.org/import-lazy/-/import-lazy-2.1.0.tgz" - integrity sha512-m7ZEHgtw69qOGw+jwxXkHlrlIPdTGkyh66zXZ1ajZbxkDBNjSY/LGbmjc7h0s2ELsUDTAhFr55TrPSSqJGPG0A== +import-lazy@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/import-lazy/-/import-lazy-4.0.0.tgz#e8eb627483a0a43da3c03f3e35548be5cb0cc153" + integrity sha512-rKtvo6a868b5Hu3heneU+L4yEQ4jYKLtjpnPeUdK7h0yzXGmyBTypknlkCvHFBqfX9YlorEiMM6Dnq/5atfHkw== imurmurhash@^0.1.4: version "0.1.4" @@ -4639,10 +5475,10 @@ indent-string@^4.0.0: resolved "https://registry.npmjs.org/indent-string/-/indent-string-4.0.0.tgz" integrity sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg== -infima@0.2.0-alpha.43: - version "0.2.0-alpha.43" - resolved "https://registry.npmjs.org/infima/-/infima-0.2.0-alpha.43.tgz" - integrity sha512-2uw57LvUqW0rK/SWYnd/2rRfxNA5DDNOh33jxF7fy46VWoNhGxiUQyVZHbBMjQ33mQem0cjdDVwgWVAmlRfgyQ== +infima@0.2.0-alpha.45: + version "0.2.0-alpha.45" + resolved "https://registry.yarnpkg.com/infima/-/infima-0.2.0-alpha.45.tgz#542aab5a249274d81679631b492973dd2c1e7466" + integrity sha512-uyH0zfr1erU1OohLk0fT4Rrb94AOhguWNOcD9uGrSpRvNB+6gZXUoJX5J0NtvzBO10YZ9PgvA4NFgt+fYg8ojw== inflight@^1.0.4: version "1.0.6" @@ -4652,7 +5488,7 @@ inflight@^1.0.4: once "^1.3.0" wrappy "1" -inherits@2, inherits@2.0.4, inherits@^2.0.0, inherits@^2.0.1, inherits@^2.0.3, inherits@~2.0.3: +inherits@2, inherits@2.0.4, inherits@^2.0.1, inherits@^2.0.3, inherits@~2.0.3: version "2.0.4" resolved "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz" integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ== @@ -4667,7 +5503,7 @@ ini@2.0.0: resolved "https://registry.npmjs.org/ini/-/ini-2.0.0.tgz" integrity sha512-7PnF4oN3CvZF23ADhA5wRaYEQpJ8qygSkbtTXWBeXWXmEVRXK+1ITciHWwHhsjv1TmW0MgacIv6hEi5pX5NQdA== -ini@^1.3.5, ini@~1.3.0: +ini@^1.3.4, ini@^1.3.5, ini@~1.3.0: version "1.3.8" resolved "https://registry.npmjs.org/ini/-/ini-1.3.8.tgz" integrity sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew== @@ -4677,6 +5513,11 @@ inline-style-parser@0.1.1: resolved "https://registry.npmjs.org/inline-style-parser/-/inline-style-parser-0.1.1.tgz" integrity sha512-7NXolsK4CAS5+xvdj5OMMbI962hU/wvwoxk+LWR9Ek9bVtyuuYScDN6eS0rUm6TxApFpw7CX1o4uJzcd4AyD3Q== +inline-style-parser@0.2.4: + version "0.2.4" + resolved "https://registry.yarnpkg.com/inline-style-parser/-/inline-style-parser-0.2.4.tgz#f4af5fe72e612839fcd453d989a586566d695f22" + integrity sha512-0aO8FkhNZlj/ZIbNi7Lxxr12obT7cL1moPfE4tg1LkX7LlLfC6DeX4l2ZEud1ukP9jNQyNnfzQVqwbwmAATY4Q== + interpret@^1.0.0: version "1.4.0" resolved "https://registry.npmjs.org/interpret/-/interpret-1.4.0.tgz" @@ -4699,18 +5540,18 @@ ipaddr.js@^2.0.1: resolved "https://registry.npmjs.org/ipaddr.js/-/ipaddr.js-2.0.1.tgz" integrity sha512-1qTgH9NG+IIJ4yfKs2e6Pp1bZg8wbDbKHT21HrLIeYBTRLgMYKnMTPAuI3Lcs61nfx5h1xlXnbJtH1kX5/d/ng== -is-alphabetical@1.0.4, is-alphabetical@^1.0.0: - version "1.0.4" - resolved "https://registry.npmjs.org/is-alphabetical/-/is-alphabetical-1.0.4.tgz" - integrity sha512-DwzsA04LQ10FHTZuL0/grVDk4rFoVH1pjAToYwBrHSxcrBIGQuXrQMtD5U1b0U2XVgKZCTLLP8u2Qxqhy3l2Vg== +is-alphabetical@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/is-alphabetical/-/is-alphabetical-2.0.1.tgz#01072053ea7c1036df3c7d19a6daaec7f19e789b" + integrity sha512-FWyyY60MeTNyeSRpkM2Iry0G9hpr7/9kD40mD/cGQEuilcZYS4okz8SN2Q6rLCJ8gbCt6fN+rC+6tMGS99LaxQ== -is-alphanumerical@^1.0.0: - version "1.0.4" - resolved "https://registry.npmjs.org/is-alphanumerical/-/is-alphanumerical-1.0.4.tgz" - integrity sha512-UzoZUr+XfVz3t3v4KyGEniVL9BDRoQtY7tOyrRybkVNjDFWyo1yhXNGrrBTQxp3ib9BLAWs7k2YKBQsFRkZG9A== +is-alphanumerical@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/is-alphanumerical/-/is-alphanumerical-2.0.1.tgz#7c03fbe96e3e931113e57f964b0a368cc2dfd875" + integrity sha512-hmbYhX/9MUMF5uh7tOXyK/n0ZvWpad5caBA17GsC6vyuCqaWliRG5K1qS9inmUhEMaOBIW7/whAnSwveW/LtZw== dependencies: - is-alphabetical "^1.0.0" - is-decimal "^1.0.0" + is-alphabetical "^2.0.0" + is-decimal "^2.0.0" is-arrayish@^0.2.1: version "0.2.1" @@ -4724,17 +5565,12 @@ is-binary-path@~2.1.0: dependencies: binary-extensions "^2.0.0" -is-buffer@^2.0.0: - version "2.0.5" - resolved "https://registry.npmjs.org/is-buffer/-/is-buffer-2.0.5.tgz" - integrity sha512-i2R6zNFDwgEHJyQUtJEk0XFi1i0dPFn/oqjK3/vPCcDeJvW5NQ83V8QbicfF1SupOaB0h8ntgBC2YiE7dfyctQ== - -is-ci@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/is-ci/-/is-ci-2.0.0.tgz" - integrity sha512-YfJT7rkpQB0updsdHLGWrvhBJfcfzNNawYDNIyQXJz0IViGf75O8EBPKSdvw2rF+LGCsX4FZ8tcr3b19LcZq4w== +is-ci@^3.0.1: + version "3.0.1" + resolved "https://registry.yarnpkg.com/is-ci/-/is-ci-3.0.1.tgz#db6ecbed1bd659c43dac0f45661e7674103d1867" + integrity sha512-ZYvCgrefwqoQ6yTyYUbQu64HsITZ3NfKX1lzaEYdkTDcfKzzCI/wthRRYKkdjHKFVgNiXKAKm65Zo1pk2as/QQ== dependencies: - ci-info "^2.0.0" + ci-info "^3.2.0" is-core-module@^2.9.0: version "2.11.0" @@ -4743,10 +5579,10 @@ is-core-module@^2.9.0: dependencies: has "^1.0.3" -is-decimal@^1.0.0: - version "1.0.4" - resolved "https://registry.npmjs.org/is-decimal/-/is-decimal-1.0.4.tgz" - integrity sha512-RGdriMmQQvZ2aqaQq3awNA6dCGtKpiDFcOzrTWrDAT2MiWrKQVPmxLGHl7Y2nNu6led0kEyoX0enY0qXYsv9zw== +is-decimal@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/is-decimal/-/is-decimal-2.0.1.tgz#9469d2dc190d0214fd87d78b78caecc0cc14eef7" + integrity sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A== is-docker@^2.0.0, is-docker@^2.1.1: version "2.2.1" @@ -4775,10 +5611,10 @@ is-glob@^4.0.0, is-glob@^4.0.1, is-glob@^4.0.3, is-glob@~4.0.1: dependencies: is-extglob "^2.1.1" -is-hexadecimal@^1.0.0: - version "1.0.4" - resolved "https://registry.npmjs.org/is-hexadecimal/-/is-hexadecimal-1.0.4.tgz" - integrity sha512-gyPJuv83bHMpocVYoqof5VDiZveEoGoFL8m3BXNb2VW8Xs+rz9kqO8LOQ5DH6EsuvilT1ApazU0pyl+ytbPtlw== +is-hexadecimal@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/is-hexadecimal/-/is-hexadecimal-2.0.1.tgz#86b5bf668fca307498d319dfc03289d781a90027" + integrity sha512-DgZQp241c8oO6cA1SbTEWiXeoxV42vlcJxgH+B3hi1AiqqKruZR3ZGF8In3fj4+/y/7rHvlOZLZtgJ/4ttYGZg== is-installed-globally@^0.4.0: version "0.4.0" @@ -4788,10 +5624,10 @@ is-installed-globally@^0.4.0: global-dirs "^3.0.0" is-path-inside "^3.0.2" -is-npm@^5.0.0: - version "5.0.0" - resolved "https://registry.npmjs.org/is-npm/-/is-npm-5.0.0.tgz" - integrity sha512-WW/rQLOazUq+ST/bCAVBp/2oMERWLsR7OrKyt052dNDk4DHcDE0/7QSXITlmi+VBcV13DfIbysG3tZJm5RfdBA== +is-npm@^6.0.0: + version "6.0.0" + resolved "https://registry.yarnpkg.com/is-npm/-/is-npm-6.0.0.tgz#b59e75e8915543ca5d881ecff864077cba095261" + integrity sha512-JEjxbSmtPSt1c8XTkVrlujcXdKV1/tvuQ7GwKcAlyiVLeYFQ2VHat8xfrDJsIkhCdF/tZ7CiIR3sy141c6+gPQ== is-number@^7.0.0: version "7.0.0" @@ -4818,16 +5654,16 @@ is-path-inside@^3.0.2: resolved "https://registry.npmjs.org/is-path-inside/-/is-path-inside-3.0.3.tgz" integrity sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ== -is-plain-obj@^2.0.0: - version "2.1.0" - resolved "https://registry.npmjs.org/is-plain-obj/-/is-plain-obj-2.1.0.tgz" - integrity sha512-YWnfyRwxL/+SsrWYfOpUtz5b3YD+nyfkHvjbcanzk8zgyO4ASD67uVMRt8k5bM4lLMDnXfriRhOpemw+NfT1eA== - is-plain-obj@^3.0.0: version "3.0.0" resolved "https://registry.npmjs.org/is-plain-obj/-/is-plain-obj-3.0.0.tgz" integrity sha512-gwsOE28k+23GP1B6vFl1oVh/WOzmawBrKwo5Ev6wMKzPkaXaCDIQKzLnvsA42DRlbVTWorkgTKIviAKCWkfUwA== +is-plain-obj@^4.0.0: + version "4.1.0" + resolved "https://registry.yarnpkg.com/is-plain-obj/-/is-plain-obj-4.1.0.tgz#d65025edec3657ce032fd7db63c97883eaed71f0" + integrity sha512-+Pgi+vMuUNkJyExiMBt5IlFoMyKnr5zhJ4Uspz58WOhBF5QoIZkFyNHIbBAtHwzVAgk5RtndVNsDRN61/mmDqg== + is-plain-object@^2.0.4: version "2.0.4" resolved "https://registry.npmjs.org/is-plain-object/-/is-plain-object-2.0.4.tgz" @@ -4855,21 +5691,11 @@ is-typedarray@^1.0.0: resolved "https://registry.npmjs.org/is-typedarray/-/is-typedarray-1.0.0.tgz" integrity sha512-cyA56iCMHAh5CdzjJIa4aohJyeO1YbwLi3Jc35MmRU6poroFjIGZzUzupGiRPOjgHg9TLu43xbpwXk523fMxKA== -is-whitespace-character@^1.0.0: - version "1.0.4" - resolved "https://registry.npmjs.org/is-whitespace-character/-/is-whitespace-character-1.0.4.tgz" - integrity sha512-SDweEzfIZM0SJV0EUga669UTKlmL0Pq8Lno0QDQsPnvECB3IM2aP0gdx5TrU0A01MAPfViaZiI2V1QMZLaKK5w== - is-windows@^1.0.1: version "1.0.2" resolved "https://registry.npmjs.org/is-windows/-/is-windows-1.0.2.tgz" integrity sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA== -is-word-character@^1.0.0: - version "1.0.4" - resolved "https://registry.npmjs.org/is-word-character/-/is-word-character-1.0.4.tgz" - integrity sha512-5SMO8RVennx3nZrqtKwCGyyetPE9VDba5ugvKLaD4KopPG5kR4mQ7tNt/r7feL5yt5h3lpuBbIUmCOG2eSzXHA== - is-wsl@^2.2.0: version "2.2.0" resolved "https://registry.npmjs.org/is-wsl/-/is-wsl-2.2.0.tgz" @@ -4877,10 +5703,10 @@ is-wsl@^2.2.0: dependencies: is-docker "^2.0.0" -is-yarn-global@^0.3.0: - version "0.3.0" - resolved "https://registry.npmjs.org/is-yarn-global/-/is-yarn-global-0.3.0.tgz" - integrity sha512-VjSeb/lHmkoyd8ryPVIKvOCn4D1koMqY+vqyjjUfc3xyKtP4dYOxM44sZrnqQSzSds3xyOrUTLTC9LVCVgLngw== +is-yarn-global@^0.4.0: + version "0.4.1" + resolved "https://registry.yarnpkg.com/is-yarn-global/-/is-yarn-global-0.4.1.tgz#b312d902b313f81e4eaf98b6361ba2b45cd694bb" + integrity sha512-/kppl+R+LO5VmhYSEWARUFjodS25D68gvj8W7z0I7OWhUla5xWu8KL6CtB2V0R6yqhnRgbcaREMr4EEM6htLPQ== isarray@0.0.1: version "0.0.1" @@ -4902,12 +5728,12 @@ isobject@^3.0.1: resolved "https://registry.npmjs.org/isobject/-/isobject-3.0.1.tgz" integrity sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg== -jest-util@^29.4.1: - version "29.4.1" - resolved "https://registry.npmjs.org/jest-util/-/jest-util-29.4.1.tgz" - integrity sha512-bQy9FPGxVutgpN4VRc0hk6w7Hx/m6L53QxpDreTZgJd9gfx/AV2MjyPde9tGyZRINAUrSv57p2inGBu2dRLmkQ== +jest-util@^29.7.0: + version "29.7.0" + resolved "https://registry.yarnpkg.com/jest-util/-/jest-util-29.7.0.tgz#23c2b62bfb22be82b44de98055802ff3710fc0bc" + integrity sha512-z6EbKajIpqGKU56y5KBUgy1dt1ihhQJgWzUlZHArA/+X2ad7Cb5iF+AK1EWVL/Bo7Rz9uurpqw6SiBCefUbCGA== dependencies: - "@jest/types" "^29.4.1" + "@jest/types" "^29.6.3" "@types/node" "*" chalk "^4.0.0" ci-info "^3.2.0" @@ -4923,25 +5749,30 @@ jest-worker@^27.4.5: merge-stream "^2.0.0" supports-color "^8.0.0" -jest-worker@^29.1.2: - version "29.4.1" - resolved "https://registry.npmjs.org/jest-worker/-/jest-worker-29.4.1.tgz" - integrity sha512-O9doU/S1EBe+yp/mstQ0VpPwpv0Clgn68TkNwGxL6/usX/KUW9Arnn4ag8C3jc6qHcXznhsT5Na1liYzAsuAbQ== +jest-worker@^29.4.3: + version "29.7.0" + resolved "https://registry.yarnpkg.com/jest-worker/-/jest-worker-29.7.0.tgz#acad073acbbaeb7262bd5389e1bcf43e10058d4a" + integrity sha512-eIz2msL/EzL9UFTFFx7jBTkeZfku0yUAyZZZmJ93H2TYEiroIx2PQjEXcwYtYl8zXCxb+PAmA2hLIt/6ZEkPHw== dependencies: "@types/node" "*" - jest-util "^29.4.1" + jest-util "^29.7.0" merge-stream "^2.0.0" supports-color "^8.0.0" -joi@^17.6.0: - version "17.7.0" - resolved "https://registry.npmjs.org/joi/-/joi-17.7.0.tgz" - integrity sha512-1/ugc8djfn93rTE3WRKdCzGGt/EtiYKxITMO4Wiv6q5JL1gl9ePt4kBsl1S499nbosspfctIQTpYIhSmHA3WAg== +jiti@^1.20.0: + version "1.21.7" + resolved "https://registry.yarnpkg.com/jiti/-/jiti-1.21.7.tgz#9dd81043424a3d28458b193d965f0d18a2300ba9" + integrity sha512-/imKNG4EbWNrVjoNC/1H5/9GFy+tqjGBHCaSsN+P2RnPqjsLmv6UD3Ej+Kj8nBWaRAwyk7kK5ZUc+OEatnTR3A== + +joi@^17.9.2: + version "17.13.3" + resolved "https://registry.yarnpkg.com/joi/-/joi-17.13.3.tgz#0f5cc1169c999b30d344366d384b12d92558bcec" + integrity sha512-otDA4ldcIx+ZXsKHWmp0YizCweVRZG96J10b0FevjfuncLO1oX59THoAmHkNubYJ+9gWsYsp5k8v4ib6oDv1fA== dependencies: - "@hapi/hoek" "^9.0.0" - "@hapi/topo" "^5.0.0" - "@sideway/address" "^4.1.3" - "@sideway/formula" "^3.0.0" + "@hapi/hoek" "^9.3.0" + "@hapi/topo" "^5.1.0" + "@sideway/address" "^4.1.5" + "@sideway/formula" "^3.0.1" "@sideway/pinpoint" "^2.0.0" "js-tokens@^3.0.0 || ^4.0.0", js-tokens@^4.0.0: @@ -4964,20 +5795,25 @@ js-yaml@^4.1.0: dependencies: argparse "^2.0.1" -jsesc@^2.5.1: - version "2.5.2" - resolved "https://registry.npmjs.org/jsesc/-/jsesc-2.5.2.tgz" - integrity sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA== +jsesc@^3.0.2: + version "3.1.0" + resolved "https://registry.yarnpkg.com/jsesc/-/jsesc-3.1.0.tgz#74d335a234f67ed19907fdadfac7ccf9d409825d" + integrity sha512-/sM3dO2FOzXjKQhJuo0Q173wf2KOo8t4I8vHy6lF9poUp7bKT0/NHE8fPX23PwfhnykfqnC2xRxOnVw5XuGIaA== jsesc@~0.5.0: version "0.5.0" resolved "https://registry.npmjs.org/jsesc/-/jsesc-0.5.0.tgz" integrity sha512-uZz5UnB7u4T9LvwmFqXii7pZSouaRPorGs5who1Ip7VO0wxanFvBL7GkM6dTHlgX+jhBApRetaWpnDabOeTcnA== -json-buffer@3.0.0: - version "3.0.0" - resolved "https://registry.npmjs.org/json-buffer/-/json-buffer-3.0.0.tgz" - integrity sha512-CuUqjv0FUZIdXkHPI8MezCnFCdaTAacej1TZYulLoAg1h/PhwkdXFN4V/gzY4g+fMBCOV2xF+rp7t2XD2ns/NQ== +jsesc@~3.0.2: + version "3.0.2" + resolved "https://registry.yarnpkg.com/jsesc/-/jsesc-3.0.2.tgz#bb8b09a6597ba426425f2e4a07245c3d00b9343e" + integrity sha512-xKqzzWXDttJuOcawBt4KnKHHIf5oQ/Cxax+0PWFG+DFDgHNAdi+TXECADI+RYiFUMmx8792xsMbbgXj4CwnP4g== + +json-buffer@3.0.1: + version "3.0.1" + resolved "https://registry.yarnpkg.com/json-buffer/-/json-buffer-3.0.1.tgz#9338802a30d3b6605fbe0613e094008ca8c05a13" + integrity sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ== json-parse-even-better-errors@^2.3.0, json-parse-even-better-errors@^2.3.1: version "2.3.1" @@ -4994,7 +5830,7 @@ json-schema-traverse@^1.0.0: resolved "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz" integrity sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug== -json5@^2.1.2, json5@^2.2.2: +json5@^2.1.2, json5@^2.2.3: version "2.2.3" resolved "https://registry.npmjs.org/json5/-/json5-2.2.3.tgz" integrity sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg== @@ -5008,12 +5844,12 @@ jsonfile@^6.0.1: optionalDependencies: graceful-fs "^4.1.6" -keyv@^3.0.0: - version "3.1.0" - resolved "https://registry.npmjs.org/keyv/-/keyv-3.1.0.tgz" - integrity sha512-9ykJ/46SN/9KPM/sichzQ7OvXyGDYKGTaDlKMGCAlg2UK8KRy4jb0d8sFc+0Tt0YYnThq8X2RZgCg74RPxgcVA== +keyv@^4.5.3: + version "4.5.4" + resolved "https://registry.yarnpkg.com/keyv/-/keyv-4.5.4.tgz#a879a99e29452f942439f2a405e3af8b31d4de93" + integrity sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw== dependencies: - json-buffer "3.0.0" + json-buffer "3.0.1" kind-of@^6.0.0, kind-of@^6.0.2: version "6.0.3" @@ -5025,27 +5861,30 @@ kleur@^3.0.3: resolved "https://registry.npmjs.org/kleur/-/kleur-3.0.3.tgz" integrity sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w== -klona@^2.0.5: - version "2.0.6" - resolved "https://registry.npmjs.org/klona/-/klona-2.0.6.tgz" - integrity sha512-dhG34DXATL5hSxJbIexCft8FChFXtmskoZYnoPWjXQuebWYCNkVeV3KkGegCK9CP1oswI/vQibS2GY7Em/sJJA== +latest-version@^7.0.0: + version "7.0.0" + resolved "https://registry.yarnpkg.com/latest-version/-/latest-version-7.0.0.tgz#843201591ea81a4d404932eeb61240fe04e9e5da" + integrity sha512-KvNT4XqAMzdcL6ka6Tl3i2lYeFDgXNCuIX+xNx6ZMVR1dFq+idXd9FLKNMOIx0t9mJ9/HudyX4oZWXZQ0UJHeg== + dependencies: + package-json "^8.1.0" -latest-version@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/latest-version/-/latest-version-5.1.0.tgz" - integrity sha512-weT+r0kTkRQdCdYCNtkMwWXQTMEswKrFBkm4ckQOMVhhqhIMI1UT2hMj+1iigIhgSZm5gTmrRXBNoGUgaTY1xA== +launch-editor@^2.6.0: + version "2.9.1" + resolved "https://registry.yarnpkg.com/launch-editor/-/launch-editor-2.9.1.tgz#253f173bd441e342d4344b4dae58291abb425047" + integrity sha512-Gcnl4Bd+hRO9P9icCP/RVVT2o8SFlPXofuCxvA2SaZuH45whSvf5p8x5oih5ftLiVhEI4sp5xDY+R+b3zJBh5w== dependencies: - package-json "^6.3.0" + picocolors "^1.0.0" + shell-quote "^1.8.1" leven@^3.1.0: version "3.1.0" resolved "https://registry.npmjs.org/leven/-/leven-3.1.0.tgz" integrity sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A== -lilconfig@^2.0.3: - version "2.0.6" - resolved "https://registry.npmjs.org/lilconfig/-/lilconfig-2.0.6.tgz" - integrity sha512-9JROoBW7pobfsx+Sq2JsASvCo6Pfo6WWoUW79HuB1BCoBXD4PLWJPqDF6fNj67pqBYTbAHkE57M1kS/+L1neOg== +lilconfig@^3.1.1: + version "3.1.3" + resolved "https://registry.yarnpkg.com/lilconfig/-/lilconfig-3.1.3.tgz#a1bcfd6257f9585bf5ae14ceeebb7b559025e4c4" + integrity sha512-/vlFKAoH5Cgt3Ie+JLhRbwOsCQePABiU3tJ1egGvyQ+33R/vcwM2Zl2QR/LzjsBeItPt3oSVXapn+m4nQDvpzw== lines-and-columns@^1.1.6: version "1.2.4" @@ -5110,36 +5949,31 @@ lodash-es@^4.17.21: resolved "https://registry.npmjs.org/lodash-es/-/lodash-es-4.17.21.tgz" integrity sha512-mKnC+QJ9pWVzv+C4/U3rRsHapFfHvQFoFB92e52xeyGMcX6/OlIl78je1u8vePzYZSkkogMPJ2yjxxsb89cxyw== -lodash.curry@^4.0.1: - version "4.1.1" - resolved "https://registry.npmjs.org/lodash.curry/-/lodash.curry-4.1.1.tgz" - integrity sha512-/u14pXGviLaweY5JI0IUzgzF2J6Ne8INyzAZjImcryjgkZ+ebruBxy2/JaOOkTqScddcYtakjhSaeemV8lR0tA== - lodash.debounce@^4.0.8: version "4.0.8" resolved "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-4.0.8.tgz" integrity sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow== -lodash.flow@^3.3.0: - version "3.5.0" - resolved "https://registry.npmjs.org/lodash.flow/-/lodash.flow-3.5.0.tgz" - integrity sha512-ff3BX/tSioo+XojX4MOsOMhJw0nZoUEF011LX8g8d3gvjVbxd89cCio4BCXronjxcTUIJUoqKEUA+n4CqvvRPw== - lodash.memoize@^4.1.2: version "4.1.2" resolved "https://registry.npmjs.org/lodash.memoize/-/lodash.memoize-4.1.2.tgz" integrity sha512-t7j+NzmgnQzTAYXcsHYLgimltOV1MXHtlOWf6GjL9Kj8GK5FInw5JotxvbOs+IvV1/Dzo04/fCGfLVs7aXb4Ag== -lodash.uniq@4.5.0, lodash.uniq@^4.5.0: +lodash.uniq@^4.5.0: version "4.5.0" resolved "https://registry.npmjs.org/lodash.uniq/-/lodash.uniq-4.5.0.tgz" integrity sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ== -lodash@4.17.21, lodash@^4.17.19, lodash@^4.17.20, lodash@^4.17.21: +lodash@4.17.21, lodash@^4.17.20, lodash@^4.17.21: version "4.17.21" resolved "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz" integrity sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg== +longest-streak@^3.0.0: + version "3.1.0" + resolved "https://registry.yarnpkg.com/longest-streak/-/longest-streak-3.1.0.tgz#62fa67cd958742a1574af9f39866364102d90cd4" + integrity sha512-9Ri+o0JYgehTaVBBDoMqIl8GXtbWg711O3srftcHhZ0dqnETqLaoIK0x17fUw9rFSlK/0NlsKe0Ahhyl5pXE2g== + loose-envify@^1.0.0, loose-envify@^1.1.0, loose-envify@^1.2.0, loose-envify@^1.3.1, loose-envify@^1.4.0: version "1.4.0" resolved "https://registry.npmjs.org/loose-envify/-/loose-envify-1.4.0.tgz" @@ -5154,15 +5988,10 @@ lower-case@^2.0.2: dependencies: tslib "^2.0.3" -lowercase-keys@^1.0.0, lowercase-keys@^1.0.1: - version "1.0.1" - resolved "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-1.0.1.tgz" - integrity sha512-G2Lj61tXDnVFFOi8VZds+SoQjtQC3dgokKdDG2mTm1tx4m50NUHBOZSBwQQHyy0V12A0JTG4icfZQH+xPyh8VA== - -lowercase-keys@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/lowercase-keys/-/lowercase-keys-2.0.0.tgz" - integrity sha512-tqNXrS78oMOE73NMxK4EMLQsQowWf8jKooH9g7xPavRT706R6bkQJ6DY2Te7QukaZsulxa30wQ7bk0pm4XiHmA== +lowercase-keys@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-3.0.0.tgz#c5e7d442e37ead247ae9db117a9d0a467c89d4f2" + integrity sha512-ozCC6gdQ+glXOQsveKD0YsDy8DSQFjDTz4zyzEHNV5+JP5D62LmfDZ6o1cycFx9ouG940M5dE8C8CTewdj2YWQ== lru-cache@^4.0.1: version "4.1.5" @@ -5186,97 +6015,711 @@ lru-cache@^6.0.0: dependencies: yallist "^4.0.0" -make-dir@^3.0.0, make-dir@^3.0.2, make-dir@^3.1.0: +make-dir@^3.0.2: version "3.1.0" resolved "https://registry.npmjs.org/make-dir/-/make-dir-3.1.0.tgz" integrity sha512-g3FeP20LNwhALb/6Cz6Dd4F2ngze0jz7tbzrD2wAV+o9FeNHe4rL+yK2md0J/fiSf1sa1ADhXqi5+oVwOM/eGw== dependencies: semver "^6.0.0" -markdown-escapes@^1.0.0: - version "1.0.4" - resolved "https://registry.npmjs.org/markdown-escapes/-/markdown-escapes-1.0.4.tgz" - integrity sha512-8z4efJYk43E0upd0NbVXwgSTQs6cT3T06etieCMEg7dRbzCbxUCK/GHlX8mhHRDcp+OLlHkPKsvqQTCvsRl2cg== +markdown-extensions@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/markdown-extensions/-/markdown-extensions-2.0.0.tgz#34bebc83e9938cae16e0e017e4a9814a8330d3c4" + integrity sha512-o5vL7aDWatOTX8LzaS1WMoaoxIiLRQJuIKKe2wAw6IeULDHaqbiqiggmx+pKvZDb1Sj+pE46Sn1T7lCqfFtg1Q== + +markdown-table@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/markdown-table/-/markdown-table-2.0.0.tgz#194a90ced26d31fe753d8b9434430214c011865b" + integrity sha512-Ezda85ToJUBhM6WGaG6veasyym+Tbs3cMAw/ZhOPqXiYsr0jgocBV3j3nx+4lk47plLlIqjwuTm/ywVI+zjJ/A== + dependencies: + repeat-string "^1.0.0" + +markdown-table@^3.0.0: + version "3.0.4" + resolved "https://registry.yarnpkg.com/markdown-table/-/markdown-table-3.0.4.tgz#fe44d6d410ff9d6f2ea1797a3f60aa4d2b631c2a" + integrity sha512-wiYz4+JrLyb/DqW2hkFJxP7Vd7JuTDm77fvbM8VfEQdmSMqcImWeeRbHwZjBjIFki/VaMK2BhFi7oUUZeM5bqw== + +mdast-util-directive@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/mdast-util-directive/-/mdast-util-directive-3.0.0.tgz#3fb1764e705bbdf0afb0d3f889e4404c3e82561f" + integrity sha512-JUpYOqKI4mM3sZcNxmF/ox04XYFFkNwr0CFlrQIkCwbvH0xzMCqkMqAde9wRd80VAhaUrwFwKm2nxretdT1h7Q== + dependencies: + "@types/mdast" "^4.0.0" + "@types/unist" "^3.0.0" + devlop "^1.0.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + parse-entities "^4.0.0" + stringify-entities "^4.0.0" + unist-util-visit-parents "^6.0.0" + +mdast-util-find-and-replace@^3.0.0, mdast-util-find-and-replace@^3.0.1: + version "3.0.1" + resolved "https://registry.yarnpkg.com/mdast-util-find-and-replace/-/mdast-util-find-and-replace-3.0.1.tgz#a6fc7b62f0994e973490e45262e4bc07607b04e0" + integrity sha512-SG21kZHGC3XRTSUhtofZkBzZTJNM5ecCi0SK2IMKmSXR8vO3peL+kb1O0z7Zl83jKtutG4k5Wv/W7V3/YHvzPA== + dependencies: + "@types/mdast" "^4.0.0" + escape-string-regexp "^5.0.0" + unist-util-is "^6.0.0" + unist-util-visit-parents "^6.0.0" + +mdast-util-from-markdown@^2.0.0: + version "2.0.2" + resolved "https://registry.yarnpkg.com/mdast-util-from-markdown/-/mdast-util-from-markdown-2.0.2.tgz#4850390ca7cf17413a9b9a0fbefcd1bc0eb4160a" + integrity sha512-uZhTV/8NBuw0WHkPTrCqDOl0zVe1BIng5ZtHoDk49ME1qqcjYmmLmOf0gELgcRMxN4w2iuIeVso5/6QymSrgmA== + dependencies: + "@types/mdast" "^4.0.0" + "@types/unist" "^3.0.0" + decode-named-character-reference "^1.0.0" + devlop "^1.0.0" + mdast-util-to-string "^4.0.0" + micromark "^4.0.0" + micromark-util-decode-numeric-character-reference "^2.0.0" + micromark-util-decode-string "^2.0.0" + micromark-util-normalize-identifier "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + unist-util-stringify-position "^4.0.0" + +mdast-util-frontmatter@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/mdast-util-frontmatter/-/mdast-util-frontmatter-2.0.1.tgz#f5f929eb1eb36c8a7737475c7eb438261f964ee8" + integrity sha512-LRqI9+wdgC25P0URIJY9vwocIzCcksduHQ9OF2joxQoyTNVduwLAFUzjoopuRJbJAReaKrNQKAZKL3uCMugWJA== + dependencies: + "@types/mdast" "^4.0.0" + devlop "^1.0.0" + escape-string-regexp "^5.0.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + micromark-extension-frontmatter "^2.0.0" + +mdast-util-gfm-autolink-literal@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/mdast-util-gfm-autolink-literal/-/mdast-util-gfm-autolink-literal-2.0.1.tgz#abd557630337bd30a6d5a4bd8252e1c2dc0875d5" + integrity sha512-5HVP2MKaP6L+G6YaxPNjuL0BPrq9orG3TsrZ9YXbA3vDw/ACI4MEsnoDpn6ZNm7GnZgtAcONJyPhOP8tNJQavQ== + dependencies: + "@types/mdast" "^4.0.0" + ccount "^2.0.0" + devlop "^1.0.0" + mdast-util-find-and-replace "^3.0.0" + micromark-util-character "^2.0.0" + +mdast-util-gfm-footnote@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/mdast-util-gfm-footnote/-/mdast-util-gfm-footnote-2.0.0.tgz#25a1753c7d16db8bfd53cd84fe50562bd1e6d6a9" + integrity sha512-5jOT2boTSVkMnQ7LTrd6n/18kqwjmuYqo7JUPe+tRCY6O7dAuTFMtTPauYYrMPpox9hlN0uOx/FL8XvEfG9/mQ== + dependencies: + "@types/mdast" "^4.0.0" + devlop "^1.1.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + micromark-util-normalize-identifier "^2.0.0" + +mdast-util-gfm-strikethrough@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/mdast-util-gfm-strikethrough/-/mdast-util-gfm-strikethrough-2.0.0.tgz#d44ef9e8ed283ac8c1165ab0d0dfd058c2764c16" + integrity sha512-mKKb915TF+OC5ptj5bJ7WFRPdYtuHv0yTRxK2tJvi+BDqbkiG7h7u/9SI89nRAYcmap2xHQL9D+QG/6wSrTtXg== + dependencies: + "@types/mdast" "^4.0.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + +mdast-util-gfm-table@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/mdast-util-gfm-table/-/mdast-util-gfm-table-2.0.0.tgz#7a435fb6223a72b0862b33afbd712b6dae878d38" + integrity sha512-78UEvebzz/rJIxLvE7ZtDd/vIQ0RHv+3Mh5DR96p7cS7HsBhYIICDBCu8csTNWNO6tBWfqXPWekRuj2FNOGOZg== + dependencies: + "@types/mdast" "^4.0.0" + devlop "^1.0.0" + markdown-table "^3.0.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + +mdast-util-gfm-task-list-item@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/mdast-util-gfm-task-list-item/-/mdast-util-gfm-task-list-item-2.0.0.tgz#e68095d2f8a4303ef24094ab642e1047b991a936" + integrity sha512-IrtvNvjxC1o06taBAVJznEnkiHxLFTzgonUdy8hzFVeDun0uTjxxrRGVaNFqkU1wJR3RBPEfsxmU6jDWPofrTQ== + dependencies: + "@types/mdast" "^4.0.0" + devlop "^1.0.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + +mdast-util-gfm@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/mdast-util-gfm/-/mdast-util-gfm-3.0.0.tgz#3f2aecc879785c3cb6a81ff3a243dc11eca61095" + integrity sha512-dgQEX5Amaq+DuUqf26jJqSK9qgixgd6rYDHAv4aTBuA92cTknZlKpPfa86Z/s8Dj8xsAQpFfBmPUHWJBWqS4Bw== + dependencies: + mdast-util-from-markdown "^2.0.0" + mdast-util-gfm-autolink-literal "^2.0.0" + mdast-util-gfm-footnote "^2.0.0" + mdast-util-gfm-strikethrough "^2.0.0" + mdast-util-gfm-table "^2.0.0" + mdast-util-gfm-task-list-item "^2.0.0" + mdast-util-to-markdown "^2.0.0" + +mdast-util-mdx-expression@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/mdast-util-mdx-expression/-/mdast-util-mdx-expression-2.0.1.tgz#43f0abac9adc756e2086f63822a38c8d3c3a5096" + integrity sha512-J6f+9hUp+ldTZqKRSg7Vw5V6MqjATc+3E4gf3CFNcuZNWD8XdyI6zQ8GqH7f8169MM6P7hMBRDVGnn7oHB9kXQ== + dependencies: + "@types/estree-jsx" "^1.0.0" + "@types/hast" "^3.0.0" + "@types/mdast" "^4.0.0" + devlop "^1.0.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + +mdast-util-mdx-jsx@^3.0.0: + version "3.1.3" + resolved "https://registry.yarnpkg.com/mdast-util-mdx-jsx/-/mdast-util-mdx-jsx-3.1.3.tgz#76b957b3da18ebcfd0de3a9b4451dcd6fdec2320" + integrity sha512-bfOjvNt+1AcbPLTFMFWY149nJz0OjmewJs3LQQ5pIyVGxP4CdOqNVJL6kTaM5c68p8q82Xv3nCyFfUnuEcH3UQ== + dependencies: + "@types/estree-jsx" "^1.0.0" + "@types/hast" "^3.0.0" + "@types/mdast" "^4.0.0" + "@types/unist" "^3.0.0" + ccount "^2.0.0" + devlop "^1.1.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + parse-entities "^4.0.0" + stringify-entities "^4.0.0" + unist-util-stringify-position "^4.0.0" + vfile-message "^4.0.0" + +mdast-util-mdx@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/mdast-util-mdx/-/mdast-util-mdx-3.0.0.tgz#792f9cf0361b46bee1fdf1ef36beac424a099c41" + integrity sha512-JfbYLAW7XnYTTbUsmpu0kdBUVe+yKVJZBItEjwyYJiDJuZ9w4eeaqks4HQO+R7objWgS2ymV60GYpI14Ug554w== + dependencies: + mdast-util-from-markdown "^2.0.0" + mdast-util-mdx-expression "^2.0.0" + mdast-util-mdx-jsx "^3.0.0" + mdast-util-mdxjs-esm "^2.0.0" + mdast-util-to-markdown "^2.0.0" + +mdast-util-mdxjs-esm@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/mdast-util-mdxjs-esm/-/mdast-util-mdxjs-esm-2.0.1.tgz#019cfbe757ad62dd557db35a695e7314bcc9fa97" + integrity sha512-EcmOpxsZ96CvlP03NghtH1EsLtr0n9Tm4lPUJUBccV9RwUOneqSycg19n5HGzCf+10LozMRSObtVr3ee1WoHtg== + dependencies: + "@types/estree-jsx" "^1.0.0" + "@types/hast" "^3.0.0" + "@types/mdast" "^4.0.0" + devlop "^1.0.0" + mdast-util-from-markdown "^2.0.0" + mdast-util-to-markdown "^2.0.0" + +mdast-util-phrasing@^4.0.0: + version "4.1.0" + resolved "https://registry.yarnpkg.com/mdast-util-phrasing/-/mdast-util-phrasing-4.1.0.tgz#7cc0a8dec30eaf04b7b1a9661a92adb3382aa6e3" + integrity sha512-TqICwyvJJpBwvGAMZjj4J2n0X8QWp21b9l0o7eXyVJ25YNWYbJDVIyD1bZXE6WtV6RmKJVYmQAKWa0zWOABz2w== + dependencies: + "@types/mdast" "^4.0.0" + unist-util-is "^6.0.0" + +mdast-util-to-hast@^13.0.0: + version "13.2.0" + resolved "https://registry.yarnpkg.com/mdast-util-to-hast/-/mdast-util-to-hast-13.2.0.tgz#5ca58e5b921cc0a3ded1bc02eed79a4fe4fe41f4" + integrity sha512-QGYKEuUsYT9ykKBCMOEDLsU5JRObWQusAolFMeko/tYPufNkRffBAQjIE+99jbA87xv6FgmjLtwjh9wBWajwAA== + dependencies: + "@types/hast" "^3.0.0" + "@types/mdast" "^4.0.0" + "@ungap/structured-clone" "^1.0.0" + devlop "^1.0.0" + micromark-util-sanitize-uri "^2.0.0" + trim-lines "^3.0.0" + unist-util-position "^5.0.0" + unist-util-visit "^5.0.0" + vfile "^6.0.0" + +mdast-util-to-markdown@^2.0.0: + version "2.1.2" + resolved "https://registry.yarnpkg.com/mdast-util-to-markdown/-/mdast-util-to-markdown-2.1.2.tgz#f910ffe60897f04bb4b7e7ee434486f76288361b" + integrity sha512-xj68wMTvGXVOKonmog6LwyJKrYXZPvlwabaryTjLh9LuvovB/KAH+kvi8Gjj+7rJjsFi23nkUxRQv1KqSroMqA== + dependencies: + "@types/mdast" "^4.0.0" + "@types/unist" "^3.0.0" + longest-streak "^3.0.0" + mdast-util-phrasing "^4.0.0" + mdast-util-to-string "^4.0.0" + micromark-util-classify-character "^2.0.0" + micromark-util-decode-string "^2.0.0" + unist-util-visit "^5.0.0" + zwitch "^2.0.0" + +mdast-util-to-string@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/mdast-util-to-string/-/mdast-util-to-string-4.0.0.tgz#7a5121475556a04e7eddeb67b264aae79d312814" + integrity sha512-0H44vDimn51F0YwvxSJSm0eCDOJTRlmN0R1yBh4HLj9wiV1Dn0QoXGbvFAWj2hSItVTlCmBF1hqKlIyUBVFLPg== + dependencies: + "@types/mdast" "^4.0.0" + +mdn-data@2.0.28: + version "2.0.28" + resolved "https://registry.yarnpkg.com/mdn-data/-/mdn-data-2.0.28.tgz#5ec48e7bef120654539069e1ae4ddc81ca490eba" + integrity sha512-aylIc7Z9y4yzHYAJNuESG3hfhC+0Ibp/MAMiaOZgNv4pmEdFyfZhhhny4MNiAfWdBQ1RQ2mfDWmM1x8SvGyp8g== + +mdn-data@2.0.30: + version "2.0.30" + resolved "https://registry.yarnpkg.com/mdn-data/-/mdn-data-2.0.30.tgz#ce4df6f80af6cfbe218ecd5c552ba13c4dfa08cc" + integrity sha512-GaqWWShW4kv/G9IEucWScBx9G1/vsFZZJUO+tD26M8J8z3Kw5RDQjaoZe03YAClgeS/SWPOcb4nkFBTEi5DUEA== + +media-typer@0.3.0: + version "0.3.0" + resolved "https://registry.npmjs.org/media-typer/-/media-typer-0.3.0.tgz" + integrity sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ== + +memfs@^3.1.2, memfs@^3.4.3: + version "3.4.13" + resolved "https://registry.npmjs.org/memfs/-/memfs-3.4.13.tgz" + integrity sha512-omTM41g3Skpvx5dSYeZIbXKcXoAVc/AoMNwn9TKx++L/gaen/+4TTttmu8ZSch5vfVJ8uJvGbroTsIlslRg6lg== + dependencies: + fs-monkey "^1.0.3" + +memoize-one@^5.1.1: + version "5.2.1" + resolved "https://registry.npmjs.org/memoize-one/-/memoize-one-5.2.1.tgz" + integrity sha512-zYiwtZUcYyXKo/np96AGZAckk+FWWsUdJ3cHGGmld7+AhvcWmQyGCYUh1hc4Q/pkOhb65dQR/pqCyK0cOaHz4Q== + +merge-descriptors@1.0.3: + version "1.0.3" + resolved "https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-1.0.3.tgz" + integrity sha512-gaNvAS7TZ897/rVaZ0nMtAyxNyi/pdbjbAwUpFQpN70GqnVfOiXpeUUMKRBmzXaSQ8DdTX4/0ms62r2K+hE6mQ== + +merge-stream@^2.0.0: + version "2.0.0" + resolved "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz" + integrity sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w== + +merge2@^1.3.0, merge2@^1.4.1: + version "1.4.1" + resolved "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz" + integrity sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg== + +methods@~1.1.2: + version "1.1.2" + resolved "https://registry.npmjs.org/methods/-/methods-1.1.2.tgz" + integrity sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w== + +micromark-core-commonmark@^2.0.0: + version "2.0.2" + resolved "https://registry.yarnpkg.com/micromark-core-commonmark/-/micromark-core-commonmark-2.0.2.tgz#6a45bbb139e126b3f8b361a10711ccc7c6e15e93" + integrity sha512-FKjQKbxd1cibWMM1P9N+H8TwlgGgSkWZMmfuVucLCHaYqeSvJ0hFeHsIa65pA2nYbes0f8LDHPMrd9X7Ujxg9w== + dependencies: + decode-named-character-reference "^1.0.0" + devlop "^1.0.0" + micromark-factory-destination "^2.0.0" + micromark-factory-label "^2.0.0" + micromark-factory-space "^2.0.0" + micromark-factory-title "^2.0.0" + micromark-factory-whitespace "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-chunked "^2.0.0" + micromark-util-classify-character "^2.0.0" + micromark-util-html-tag-name "^2.0.0" + micromark-util-normalize-identifier "^2.0.0" + micromark-util-resolve-all "^2.0.0" + micromark-util-subtokenize "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-directive@^3.0.0: + version "3.0.2" + resolved "https://registry.yarnpkg.com/micromark-extension-directive/-/micromark-extension-directive-3.0.2.tgz#2eb61985d1995a7c1ff7621676a4f32af29409e8" + integrity sha512-wjcXHgk+PPdmvR58Le9d7zQYWy+vKEU9Se44p2CrCDPiLr2FMyiT4Fyb5UFKFC66wGB3kPlgD7q3TnoqPS7SZA== + dependencies: + devlop "^1.0.0" + micromark-factory-space "^2.0.0" + micromark-factory-whitespace "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + parse-entities "^4.0.0" + +micromark-extension-frontmatter@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/micromark-extension-frontmatter/-/micromark-extension-frontmatter-2.0.0.tgz#651c52ffa5d7a8eeed687c513cd869885882d67a" + integrity sha512-C4AkuM3dA58cgZha7zVnuVxBhDsbttIMiytjgsM2XbHAB2faRVaHRle40558FBN+DJcrLNCoqG5mlrpdU4cRtg== + dependencies: + fault "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-gfm-autolink-literal@^2.0.0: + version "2.1.0" + resolved "https://registry.yarnpkg.com/micromark-extension-gfm-autolink-literal/-/micromark-extension-gfm-autolink-literal-2.1.0.tgz#6286aee9686c4462c1e3552a9d505feddceeb935" + integrity sha512-oOg7knzhicgQ3t4QCjCWgTmfNhvQbDDnJeVu9v81r7NltNCVmhPy1fJRX27pISafdjL+SVc4d3l48Gb6pbRypw== + dependencies: + micromark-util-character "^2.0.0" + micromark-util-sanitize-uri "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-gfm-footnote@^2.0.0: + version "2.1.0" + resolved "https://registry.yarnpkg.com/micromark-extension-gfm-footnote/-/micromark-extension-gfm-footnote-2.1.0.tgz#4dab56d4e398b9853f6fe4efac4fc9361f3e0750" + integrity sha512-/yPhxI1ntnDNsiHtzLKYnE3vf9JZ6cAisqVDauhp4CEHxlb4uoOTxOCJ+9s51bIB8U1N1FJ1RXOKTIlD5B/gqw== + dependencies: + devlop "^1.0.0" + micromark-core-commonmark "^2.0.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-normalize-identifier "^2.0.0" + micromark-util-sanitize-uri "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-gfm-strikethrough@^2.0.0: + version "2.1.0" + resolved "https://registry.yarnpkg.com/micromark-extension-gfm-strikethrough/-/micromark-extension-gfm-strikethrough-2.1.0.tgz#86106df8b3a692b5f6a92280d3879be6be46d923" + integrity sha512-ADVjpOOkjz1hhkZLlBiYA9cR2Anf8F4HqZUO6e5eDcPQd0Txw5fxLzzxnEkSkfnD0wziSGiv7sYhk/ktvbf1uw== + dependencies: + devlop "^1.0.0" + micromark-util-chunked "^2.0.0" + micromark-util-classify-character "^2.0.0" + micromark-util-resolve-all "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-gfm-table@^2.0.0: + version "2.1.0" + resolved "https://registry.yarnpkg.com/micromark-extension-gfm-table/-/micromark-extension-gfm-table-2.1.0.tgz#5cadedfbb29fca7abf752447967003dc3b6583c9" + integrity sha512-Ub2ncQv+fwD70/l4ou27b4YzfNaCJOvyX4HxXU15m7mpYY+rjuWzsLIPZHJL253Z643RpbcP1oeIJlQ/SKW67g== + dependencies: + devlop "^1.0.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-gfm-tagfilter@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/micromark-extension-gfm-tagfilter/-/micromark-extension-gfm-tagfilter-2.0.0.tgz#f26d8a7807b5985fba13cf61465b58ca5ff7dc57" + integrity sha512-xHlTOmuCSotIA8TW1mDIM6X2O1SiX5P9IuDtqGonFhEK0qgRI4yeC6vMxEV2dgyr2TiD+2PQ10o+cOhdVAcwfg== + dependencies: + micromark-util-types "^2.0.0" + +micromark-extension-gfm-task-list-item@^2.0.0: + version "2.1.0" + resolved "https://registry.yarnpkg.com/micromark-extension-gfm-task-list-item/-/micromark-extension-gfm-task-list-item-2.1.0.tgz#bcc34d805639829990ec175c3eea12bb5b781f2c" + integrity sha512-qIBZhqxqI6fjLDYFTBIa4eivDMnP+OZqsNwmQ3xNLE4Cxwc+zfQEfbs6tzAo2Hjq+bh6q5F+Z8/cksrLFYWQQw== + dependencies: + devlop "^1.0.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-gfm@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/micromark-extension-gfm/-/micromark-extension-gfm-3.0.0.tgz#3e13376ab95dd7a5cfd0e29560dfe999657b3c5b" + integrity sha512-vsKArQsicm7t0z2GugkCKtZehqUm31oeGBV/KVSorWSy8ZlNAv7ytjFhvaryUiCUJYqs+NoE6AFhpQvBTM6Q4w== + dependencies: + micromark-extension-gfm-autolink-literal "^2.0.0" + micromark-extension-gfm-footnote "^2.0.0" + micromark-extension-gfm-strikethrough "^2.0.0" + micromark-extension-gfm-table "^2.0.0" + micromark-extension-gfm-tagfilter "^2.0.0" + micromark-extension-gfm-task-list-item "^2.0.0" + micromark-util-combine-extensions "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-mdx-expression@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/micromark-extension-mdx-expression/-/micromark-extension-mdx-expression-3.0.0.tgz#1407b9ce69916cf5e03a196ad9586889df25302a" + integrity sha512-sI0nwhUDz97xyzqJAbHQhp5TfaxEvZZZ2JDqUo+7NvyIYG6BZ5CPPqj2ogUoPJlmXHBnyZUzISg9+oUmU6tUjQ== + dependencies: + "@types/estree" "^1.0.0" + devlop "^1.0.0" + micromark-factory-mdx-expression "^2.0.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-events-to-acorn "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-extension-mdx-jsx@^3.0.0: + version "3.0.1" + resolved "https://registry.yarnpkg.com/micromark-extension-mdx-jsx/-/micromark-extension-mdx-jsx-3.0.1.tgz#5abb83da5ddc8e473a374453e6ea56fbd66b59ad" + integrity sha512-vNuFb9czP8QCtAQcEJn0UJQJZA8Dk6DXKBqx+bg/w0WGuSxDxNr7hErW89tHUY31dUW4NqEOWwmEUNhjTFmHkg== + dependencies: + "@types/acorn" "^4.0.0" + "@types/estree" "^1.0.0" + devlop "^1.0.0" + estree-util-is-identifier-name "^3.0.0" + micromark-factory-mdx-expression "^2.0.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-events-to-acorn "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + vfile-message "^4.0.0" + +micromark-extension-mdx-md@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/micromark-extension-mdx-md/-/micromark-extension-mdx-md-2.0.0.tgz#1d252881ea35d74698423ab44917e1f5b197b92d" + integrity sha512-EpAiszsB3blw4Rpba7xTOUptcFeBFi+6PY8VnJ2hhimH+vCQDirWgsMpz7w1XcZE7LVrSAUGb9VJpG9ghlYvYQ== + dependencies: + micromark-util-types "^2.0.0" + +micromark-extension-mdxjs-esm@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/micromark-extension-mdxjs-esm/-/micromark-extension-mdxjs-esm-3.0.0.tgz#de21b2b045fd2059bd00d36746081de38390d54a" + integrity sha512-DJFl4ZqkErRpq/dAPyeWp15tGrcrrJho1hKK5uBS70BCtfrIFg81sqcTVu3Ta+KD1Tk5vAtBNElWxtAa+m8K9A== + dependencies: + "@types/estree" "^1.0.0" + devlop "^1.0.0" + micromark-core-commonmark "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-events-to-acorn "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + unist-util-position-from-estree "^2.0.0" + vfile-message "^4.0.0" + +micromark-extension-mdxjs@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/micromark-extension-mdxjs/-/micromark-extension-mdxjs-3.0.0.tgz#b5a2e0ed449288f3f6f6c544358159557549de18" + integrity sha512-A873fJfhnJ2siZyUrJ31l34Uqwy4xIFmvPY1oj+Ean5PHcPBYzEsvqvWGaWcfEIr11O5Dlw3p2y0tZWpKHDejQ== + dependencies: + acorn "^8.0.0" + acorn-jsx "^5.0.0" + micromark-extension-mdx-expression "^3.0.0" + micromark-extension-mdx-jsx "^3.0.0" + micromark-extension-mdx-md "^2.0.0" + micromark-extension-mdxjs-esm "^3.0.0" + micromark-util-combine-extensions "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-factory-destination@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-factory-destination/-/micromark-factory-destination-2.0.1.tgz#8fef8e0f7081f0474fbdd92deb50c990a0264639" + integrity sha512-Xe6rDdJlkmbFRExpTOmRj9N3MaWmbAgdpSrBQvCFqhezUn4AHqJHbaEnfbVYYiexVSs//tqOdY/DxhjdCiJnIA== + dependencies: + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-factory-label@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-factory-label/-/micromark-factory-label-2.0.1.tgz#5267efa97f1e5254efc7f20b459a38cb21058ba1" + integrity sha512-VFMekyQExqIW7xIChcXn4ok29YE3rnuyveW3wZQWWqF4Nv9Wk5rgJ99KzPvHjkmPXF93FXIbBp6YdW3t71/7Vg== + dependencies: + devlop "^1.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-factory-mdx-expression@^2.0.0: + version "2.0.2" + resolved "https://registry.yarnpkg.com/micromark-factory-mdx-expression/-/micromark-factory-mdx-expression-2.0.2.tgz#2afaa8ba6d5f63e0cead3e4dee643cad184ca260" + integrity sha512-5E5I2pFzJyg2CtemqAbcyCktpHXuJbABnsb32wX2U8IQKhhVFBqkcZR5LRm1WVoFqa4kTueZK4abep7wdo9nrw== + dependencies: + "@types/estree" "^1.0.0" + devlop "^1.0.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-events-to-acorn "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + unist-util-position-from-estree "^2.0.0" + vfile-message "^4.0.0" + +micromark-factory-space@^1.0.0: + version "1.1.0" + resolved "https://registry.yarnpkg.com/micromark-factory-space/-/micromark-factory-space-1.1.0.tgz#c8f40b0640a0150751d3345ed885a080b0d15faf" + integrity sha512-cRzEj7c0OL4Mw2v6nwzttyOZe8XY/Z8G0rzmWQZTBi/jjwyw/U4uqKtUORXQrR5bAZZnbTI/feRV/R7hc4jQYQ== + dependencies: + micromark-util-character "^1.0.0" + micromark-util-types "^1.0.0" + +micromark-factory-space@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-factory-space/-/micromark-factory-space-2.0.1.tgz#36d0212e962b2b3121f8525fc7a3c7c029f334fc" + integrity sha512-zRkxjtBxxLd2Sc0d+fbnEunsTj46SWXgXciZmHq0kDYGnck/ZSGj9/wULTV95uoeYiK5hRXP2mJ98Uo4cq/LQg== + dependencies: + micromark-util-character "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-factory-title@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-factory-title/-/micromark-factory-title-2.0.1.tgz#237e4aa5d58a95863f01032d9ee9b090f1de6e94" + integrity sha512-5bZ+3CjhAd9eChYTHsjy6TGxpOFSKgKKJPJxr293jTbfry2KDoWkhBb6TcPVB4NmzaPhMs1Frm9AZH7OD4Cjzw== + dependencies: + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-factory-whitespace@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-factory-whitespace/-/micromark-factory-whitespace-2.0.1.tgz#06b26b2983c4d27bfcc657b33e25134d4868b0b1" + integrity sha512-Ob0nuZ3PKt/n0hORHyvoD9uZhr+Za8sFoP+OnMcnWK5lngSzALgQYKMr9RJVOWLqQYuyn6ulqGWSXdwf6F80lQ== + dependencies: + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-util-character@^1.0.0, micromark-util-character@^1.1.0: + version "1.2.0" + resolved "https://registry.yarnpkg.com/micromark-util-character/-/micromark-util-character-1.2.0.tgz#4fedaa3646db249bc58caeb000eb3549a8ca5dcc" + integrity sha512-lXraTwcX3yH/vMDaFWCQJP1uIszLVebzUa3ZHdrgxr7KEU/9mL4mVgCpGbyhvNLNlauROiNUq7WN5u7ndbY6xg== + dependencies: + micromark-util-symbol "^1.0.0" + micromark-util-types "^1.0.0" + +micromark-util-character@^2.0.0: + version "2.1.1" + resolved "https://registry.yarnpkg.com/micromark-util-character/-/micromark-util-character-2.1.1.tgz#2f987831a40d4c510ac261e89852c4e9703ccda6" + integrity sha512-wv8tdUTJ3thSFFFJKtpYKOYiGP2+v96Hvk4Tu8KpCAsTMs6yi+nVmGh1syvSCsaxz45J6Jbw+9DD6g97+NV67Q== + dependencies: + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-util-chunked@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-chunked/-/micromark-util-chunked-2.0.1.tgz#47fbcd93471a3fccab86cff03847fc3552db1051" + integrity sha512-QUNFEOPELfmvv+4xiNg2sRYeS/P84pTW0TCgP5zc9FpXetHY0ab7SxKyAQCNCc1eK0459uoLI1y5oO5Vc1dbhA== + dependencies: + micromark-util-symbol "^2.0.0" + +micromark-util-classify-character@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-classify-character/-/micromark-util-classify-character-2.0.1.tgz#d399faf9c45ca14c8b4be98b1ea481bced87b629" + integrity sha512-K0kHzM6afW/MbeWYWLjoHQv1sgg2Q9EccHEDzSkxiP/EaagNzCm7T/WMKZ3rjMbvIpvBiZgwR3dKMygtA4mG1Q== + dependencies: + micromark-util-character "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-util-combine-extensions@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-combine-extensions/-/micromark-util-combine-extensions-2.0.1.tgz#2a0f490ab08bff5cc2fd5eec6dd0ca04f89b30a9" + integrity sha512-OnAnH8Ujmy59JcyZw8JSbK9cGpdVY44NKgSM7E9Eh7DiLS2E9RNQf0dONaGDzEG9yjEl5hcqeIsj4hfRkLH/Bg== + dependencies: + micromark-util-chunked "^2.0.0" + micromark-util-types "^2.0.0" + +micromark-util-decode-numeric-character-reference@^2.0.0: + version "2.0.2" + resolved "https://registry.yarnpkg.com/micromark-util-decode-numeric-character-reference/-/micromark-util-decode-numeric-character-reference-2.0.2.tgz#fcf15b660979388e6f118cdb6bf7d79d73d26fe5" + integrity sha512-ccUbYk6CwVdkmCQMyr64dXz42EfHGkPQlBj5p7YVGzq8I7CtjXZJrubAYezf7Rp+bjPseiROqe7G6foFd+lEuw== + dependencies: + micromark-util-symbol "^2.0.0" + +micromark-util-decode-string@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-decode-string/-/micromark-util-decode-string-2.0.1.tgz#6cb99582e5d271e84efca8e61a807994d7161eb2" + integrity sha512-nDV/77Fj6eH1ynwscYTOsbK7rR//Uj0bZXBwJZRfaLEJ1iGBR6kIfNmlNqaqJf649EP0F3NWNdeJi03elllNUQ== + dependencies: + decode-named-character-reference "^1.0.0" + micromark-util-character "^2.0.0" + micromark-util-decode-numeric-character-reference "^2.0.0" + micromark-util-symbol "^2.0.0" + +micromark-util-encode@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-encode/-/micromark-util-encode-2.0.1.tgz#0d51d1c095551cfaac368326963cf55f15f540b8" + integrity sha512-c3cVx2y4KqUnwopcO9b/SCdo2O67LwJJ/UyqGfbigahfegL9myoEFoDYZgkT7f36T0bLrM9hZTAaAyH+PCAXjw== + +micromark-util-events-to-acorn@^2.0.0: + version "2.0.2" + resolved "https://registry.yarnpkg.com/micromark-util-events-to-acorn/-/micromark-util-events-to-acorn-2.0.2.tgz#4275834f5453c088bd29cd72dfbf80e3327cec07" + integrity sha512-Fk+xmBrOv9QZnEDguL9OI9/NQQp6Hz4FuQ4YmCb/5V7+9eAh1s6AYSvL20kHkD67YIg7EpE54TiSlcsf3vyZgA== + dependencies: + "@types/acorn" "^4.0.0" + "@types/estree" "^1.0.0" + "@types/unist" "^3.0.0" + devlop "^1.0.0" + estree-util-visit "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" + vfile-message "^4.0.0" + +micromark-util-html-tag-name@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-html-tag-name/-/micromark-util-html-tag-name-2.0.1.tgz#e40403096481986b41c106627f98f72d4d10b825" + integrity sha512-2cNEiYDhCWKI+Gs9T0Tiysk136SnR13hhO8yW6BGNyhOC4qYFnwF1nKfD3HFAIXA5c45RrIG1ub11GiXeYd1xA== -mdast-squeeze-paragraphs@^4.0.0: - version "4.0.0" - resolved "https://registry.npmjs.org/mdast-squeeze-paragraphs/-/mdast-squeeze-paragraphs-4.0.0.tgz" - integrity sha512-zxdPn69hkQ1rm4J+2Cs2j6wDEv7O17TfXTJ33tl/+JPIoEmtV9t2ZzBM5LPHE8QlHsmVD8t3vPKCyY3oH+H8MQ== +micromark-util-normalize-identifier@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-normalize-identifier/-/micromark-util-normalize-identifier-2.0.1.tgz#c30d77b2e832acf6526f8bf1aa47bc9c9438c16d" + integrity sha512-sxPqmo70LyARJs0w2UclACPUUEqltCkJ6PhKdMIDuJ3gSf/Q+/GIe3WKl0Ijb/GyH9lOpUkRAO2wp0GVkLvS9Q== dependencies: - unist-util-remove "^2.0.0" + micromark-util-symbol "^2.0.0" -mdast-util-definitions@^4.0.0: - version "4.0.0" - resolved "https://registry.npmjs.org/mdast-util-definitions/-/mdast-util-definitions-4.0.0.tgz" - integrity sha512-k8AJ6aNnUkB7IE+5azR9h81O5EQ/cTDXtWdMq9Kk5KcEW/8ritU5CeLg/9HhOC++nALHBlaogJ5jz0Ybk3kPMQ== +micromark-util-resolve-all@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-resolve-all/-/micromark-util-resolve-all-2.0.1.tgz#e1a2d62cdd237230a2ae11839027b19381e31e8b" + integrity sha512-VdQyxFWFT2/FGJgwQnJYbe1jjQoNTS4RjglmSjTUlpUMa95Htx9NHeYW4rGDJzbjvCsl9eLjMQwGeElsqmzcHg== dependencies: - unist-util-visit "^2.0.0" + micromark-util-types "^2.0.0" -mdast-util-to-hast@10.0.1: - version "10.0.1" - resolved "https://registry.npmjs.org/mdast-util-to-hast/-/mdast-util-to-hast-10.0.1.tgz" - integrity sha512-BW3LM9SEMnjf4HXXVApZMt8gLQWVNXc3jryK0nJu/rOXPOnlkUjmdkDlmxMirpbU9ILncGFIwLH/ubnWBbcdgA== +micromark-util-sanitize-uri@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-sanitize-uri/-/micromark-util-sanitize-uri-2.0.1.tgz#ab89789b818a58752b73d6b55238621b7faa8fd7" + integrity sha512-9N9IomZ/YuGGZZmQec1MbgxtlgougxTodVwDzzEouPKo3qFWvymFHWcnDi2vzV1ff6kas9ucW+o3yzJK9YB1AQ== dependencies: - "@types/mdast" "^3.0.0" - "@types/unist" "^2.0.0" - mdast-util-definitions "^4.0.0" - mdurl "^1.0.0" - unist-builder "^2.0.0" - unist-util-generated "^1.0.0" - unist-util-position "^3.0.0" - unist-util-visit "^2.0.0" - -mdast-util-to-string@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/mdast-util-to-string/-/mdast-util-to-string-2.0.0.tgz" - integrity sha512-AW4DRS3QbBayY/jJmD8437V1Gombjf8RSOUCMFBuo5iHi58AGEgVCKQ+ezHkZZDpAQS75hcBMpLqjpJTjtUL7w== - -mdn-data@2.0.14: - version "2.0.14" - resolved "https://registry.npmjs.org/mdn-data/-/mdn-data-2.0.14.tgz" - integrity sha512-dn6wd0uw5GsdswPFfsgMp5NSB0/aDe6fK94YJV/AJDYXL6HVLWBsxeq7js7Ad+mU2K9LAlwpk6kN2D5mwCPVow== - -mdurl@^1.0.0: - version "1.0.1" - resolved "https://registry.npmjs.org/mdurl/-/mdurl-1.0.1.tgz" - integrity sha512-/sKlQJCBYVY9Ers9hqzKou4H6V5UWc/M59TH2dvkt+84itfnq7uFOMLpOiOS4ujvHP4etln18fmIxA5R5fll0g== - -media-typer@0.3.0: - version "0.3.0" - resolved "https://registry.npmjs.org/media-typer/-/media-typer-0.3.0.tgz" - integrity sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ== + micromark-util-character "^2.0.0" + micromark-util-encode "^2.0.0" + micromark-util-symbol "^2.0.0" -memfs@^3.1.2, memfs@^3.4.3: - version "3.4.13" - resolved "https://registry.npmjs.org/memfs/-/memfs-3.4.13.tgz" - integrity sha512-omTM41g3Skpvx5dSYeZIbXKcXoAVc/AoMNwn9TKx++L/gaen/+4TTttmu8ZSch5vfVJ8uJvGbroTsIlslRg6lg== +micromark-util-subtokenize@^2.0.0: + version "2.0.3" + resolved "https://registry.yarnpkg.com/micromark-util-subtokenize/-/micromark-util-subtokenize-2.0.3.tgz#70ffb99a454bd8c913c8b709c3dc97baefb65f96" + integrity sha512-VXJJuNxYWSoYL6AJ6OQECCFGhIU2GGHMw8tahogePBrjkG8aCCas3ibkp7RnVOSTClg2is05/R7maAhF1XyQMg== dependencies: - fs-monkey "^1.0.3" + devlop "^1.0.0" + micromark-util-chunked "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" -memoize-one@^5.1.1: - version "5.2.1" - resolved "https://registry.npmjs.org/memoize-one/-/memoize-one-5.2.1.tgz" - integrity sha512-zYiwtZUcYyXKo/np96AGZAckk+FWWsUdJ3cHGGmld7+AhvcWmQyGCYUh1hc4Q/pkOhb65dQR/pqCyK0cOaHz4Q== +micromark-util-symbol@^1.0.0, micromark-util-symbol@^1.0.1: + version "1.1.0" + resolved "https://registry.yarnpkg.com/micromark-util-symbol/-/micromark-util-symbol-1.1.0.tgz#813cd17837bdb912d069a12ebe3a44b6f7063142" + integrity sha512-uEjpEYY6KMs1g7QfJ2eX1SQEV+ZT4rUD3UcF6l57acZvLNK7PBZL+ty82Z1qhK1/yXIY4bdx04FKMgR0g4IAag== -merge-descriptors@1.0.3: - version "1.0.3" - resolved "https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-1.0.3.tgz" - integrity sha512-gaNvAS7TZ897/rVaZ0nMtAyxNyi/pdbjbAwUpFQpN70GqnVfOiXpeUUMKRBmzXaSQ8DdTX4/0ms62r2K+hE6mQ== +micromark-util-symbol@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-symbol/-/micromark-util-symbol-2.0.1.tgz#e5da494e8eb2b071a0d08fb34f6cefec6c0a19b8" + integrity sha512-vs5t8Apaud9N28kgCrRUdEed4UJ+wWNvicHLPxCa9ENlYuAY31M0ETy5y1vA33YoNPDFTghEbnh6efaE8h4x0Q== -merge-stream@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz" - integrity sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w== +micromark-util-types@^1.0.0: + version "1.1.0" + resolved "https://registry.yarnpkg.com/micromark-util-types/-/micromark-util-types-1.1.0.tgz#e6676a8cae0bb86a2171c498167971886cb7e283" + integrity sha512-ukRBgie8TIAcacscVHSiddHjO4k/q3pnedmzMQ4iwDcK0FtFCohKOlFbaOL/mPgfnPsL3C1ZyxJa4sbWrBl3jg== -merge2@^1.3.0, merge2@^1.4.1: - version "1.4.1" - resolved "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz" - integrity sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg== +micromark-util-types@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/micromark-util-types/-/micromark-util-types-2.0.1.tgz#a3edfda3022c6c6b55bfb049ef5b75d70af50709" + integrity sha512-534m2WhVTddrcKVepwmVEVnUAmtrx9bfIjNoQHRqfnvdaHQiFytEhJoTgpWJvDEXCO5gLTQh3wYC1PgOJA4NSQ== -methods@~1.1.2: - version "1.1.2" - resolved "https://registry.npmjs.org/methods/-/methods-1.1.2.tgz" - integrity sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w== +micromark@^4.0.0: + version "4.0.1" + resolved "https://registry.yarnpkg.com/micromark/-/micromark-4.0.1.tgz#294c2f12364759e5f9e925a767ae3dfde72223ff" + integrity sha512-eBPdkcoCNvYcxQOAKAlceo5SNdzZWfF+FcSupREAzdAh9rRmE239CEQAiTwIgblwnoM8zzj35sZ5ZwvSEOF6Kw== + dependencies: + "@types/debug" "^4.0.0" + debug "^4.0.0" + decode-named-character-reference "^1.0.0" + devlop "^1.0.0" + micromark-core-commonmark "^2.0.0" + micromark-factory-space "^2.0.0" + micromark-util-character "^2.0.0" + micromark-util-chunked "^2.0.0" + micromark-util-combine-extensions "^2.0.0" + micromark-util-decode-numeric-character-reference "^2.0.0" + micromark-util-encode "^2.0.0" + micromark-util-normalize-identifier "^2.0.0" + micromark-util-resolve-all "^2.0.0" + micromark-util-sanitize-uri "^2.0.0" + micromark-util-subtokenize "^2.0.0" + micromark-util-symbol "^2.0.0" + micromark-util-types "^2.0.0" micromatch@^4.0.2, micromatch@^4.0.4, micromatch@^4.0.5: version "4.0.8" @@ -5320,17 +6763,23 @@ mimic-fn@^2.1.0: resolved "https://registry.npmjs.org/mimic-fn/-/mimic-fn-2.1.0.tgz" integrity sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg== -mimic-response@^1.0.0, mimic-response@^1.0.1: - version "1.0.1" - resolved "https://registry.npmjs.org/mimic-response/-/mimic-response-1.0.1.tgz" - integrity sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ== +mimic-response@^3.1.0: + version "3.1.0" + resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-3.1.0.tgz#2d1d59af9c1b129815accc2c46a022a5ce1fa3c9" + integrity sha512-z0yWI+4FDrrweS8Zmt4Ej5HdJmky15+L2e6Wgn3+iK5fWzb6T3fhNFq2+MeTRb064c6Wr4N/wv0DzQTjNzHNGQ== -mini-css-extract-plugin@^2.6.1: - version "2.7.2" - resolved "https://registry.npmjs.org/mini-css-extract-plugin/-/mini-css-extract-plugin-2.7.2.tgz" - integrity sha512-EdlUizq13o0Pd+uCp+WO/JpkLvHRVGt97RqfeGhXqAcorYo1ypJSpkV+WDT0vY/kmh/p7wRdJNJtuyK540PXDw== +mimic-response@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-4.0.0.tgz#35468b19e7c75d10f5165ea25e75a5ceea7cf70f" + integrity sha512-e5ISH9xMYU0DzrT+jl8q2ze9D6eWBto+I8CNpe+VI+K2J/F/k3PdkdTdz4wvGVH4NTpo+NRYTVIuMQEMMcsLqg== + +mini-css-extract-plugin@^2.9.1: + version "2.9.2" + resolved "https://registry.yarnpkg.com/mini-css-extract-plugin/-/mini-css-extract-plugin-2.9.2.tgz#966031b468917a5446f4c24a80854b2947503c5b" + integrity sha512-GJuACcS//jtq4kCtd5ii/M0SZf7OZRH+BxdqXZHaJfb8TJiVl+NgQRPwiYt2EuqeSkNydn/7vP+bcE27C5mb9w== dependencies: schema-utils "^4.0.0" + tapable "^2.2.1" minimalistic-assert@^1.0.0: version "1.0.1" @@ -5344,15 +6793,15 @@ minimatch@3.1.2, minimatch@^3.0.4, minimatch@^3.0.5, minimatch@^3.1.1: dependencies: brace-expansion "^1.1.7" -minimist@^1.2.0, minimist@^1.2.5: +minimist@^1.2.0: version "1.2.7" resolved "https://registry.npmjs.org/minimist/-/minimist-1.2.7.tgz" integrity sha512-bzfL1YUZsP41gmu/qjrEk0Q6i2ix/cVeAhbCbqH9u3zYutS1cLg00qhrD0M2MVdCcx4Sc0UpP2eBWo9rotpq6g== -mrmime@^1.0.0: - version "1.0.1" - resolved "https://registry.npmjs.org/mrmime/-/mrmime-1.0.1.tgz" - integrity sha512-hzzEagAgDyoU1Q6yg5uI+AorQgdvMCur3FcKf7NhMKWsaYg+RnbTyHRa/9IlLF9rf455MOCtcqqrQQ83pPP7Uw== +mrmime@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/mrmime/-/mrmime-2.0.0.tgz#151082a6e06e59a9a39b46b3e14d5cfe92b3abb4" + integrity sha512-eu38+hdgojoyq63s+yTpN4XMBdt5l8HhMhc4VKLO9KM5caLIBvUm4thi7fFaxyTmCKeNnXZ5pAlBwCUnhA09uw== ms@2.0.0: version "2.0.0" @@ -5364,7 +6813,7 @@ ms@2.1.2: resolved "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz" integrity sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w== -ms@2.1.3: +ms@2.1.3, ms@^2.1.3: version "2.1.3" resolved "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz" integrity sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA== @@ -5377,9 +6826,9 @@ multicast-dns@^7.2.5: dns-packet "^5.2.2" thunky "^1.0.2" -nanoid@^3.3.6: +nanoid@^3.3.7: version "3.3.8" - resolved "https://registry.npmjs.org/nanoid/-/nanoid-3.3.8.tgz" + resolved "https://registry.yarnpkg.com/nanoid/-/nanoid-3.3.8.tgz#b1be3030bee36aaff18bacb375e5cce521684baf" integrity sha512-WNLf5Sd8oZxOm+TzppcYk8gVOgP+l58xNy58D0nbUnOxOWRWvlcCV4kUF7ltmI6PsrLl/BgKEyS4mqsGChFN0w== negotiator@0.6.3: @@ -5407,19 +6856,15 @@ no-case@^3.0.4: lower-case "^2.0.2" tslib "^2.0.3" -node-emoji@^1.10.0: - version "1.11.0" - resolved "https://registry.npmjs.org/node-emoji/-/node-emoji-1.11.0.tgz" - integrity sha512-wo2DpQkQp7Sjm2A0cq+sN7EHKO6Sl0ctXeBdFZrL9T9+UywORbufTcTZxom8YqpLQt/FqNMUkOpkZrJVYSKD3A== - dependencies: - lodash "^4.17.21" - -node-fetch@2.6.7: - version "2.6.7" - resolved "https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.7.tgz" - integrity sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ== +node-emoji@^2.1.0: + version "2.2.0" + resolved "https://registry.yarnpkg.com/node-emoji/-/node-emoji-2.2.0.tgz#1d000e3c76e462577895be1b436f4aa2d6760eb0" + integrity sha512-Z3lTE9pLaJF47NyMhd4ww1yFTAP8YhYI8SleJiHzM46Fgpm5cnNzSl9XfzFNqbaz+VlJrIj3fXQ4DeN1Rjm6cw== dependencies: - whatwg-url "^5.0.0" + "@sindresorhus/is" "^4.6.0" + char-regex "^1.0.2" + emojilib "^2.4.0" + skin-tone "^2.0.0" node-forge@^1: version "1.3.1" @@ -5431,6 +6876,11 @@ node-releases@^2.0.18: resolved "https://registry.npmjs.org/node-releases/-/node-releases-2.0.18.tgz" integrity sha512-d9VeXT4SJ7ZeOqGX6R5EM022wpL+eWPooLI+5UpWn2jCT1aosUQEhQP214x33Wkwx3JQMvIm+tIoVOdodFS40g== +node-releases@^2.0.19: + version "2.0.19" + resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-2.0.19.tgz#9e445a52950951ec4d177d843af370b411caf314" + integrity sha512-xxOWJsBKtzAq7DY0J+DTzuz58K8e7sJbdgwkbMWQe8UYB6ekmsQ45q0M/tJDsGaZmbC+l7n57UV8Hl5tHxO9uw== + normalize-path@^3.0.0, normalize-path@~3.0.0: version "3.0.0" resolved "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz" @@ -5441,15 +6891,10 @@ normalize-range@^0.1.2: resolved "https://registry.npmjs.org/normalize-range/-/normalize-range-0.1.2.tgz" integrity sha512-bdok/XvKII3nUpklnV6P2hxtMNrCboOjAcyBuQnWEhO665FwrSNRxU+AqpsyvO6LgGYPspN+lu5CLtw4jPRKNA== -normalize-url@^4.1.0: - version "4.5.1" - resolved "https://registry.npmjs.org/normalize-url/-/normalize-url-4.5.1.tgz" - integrity sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA== - -normalize-url@^6.0.1: - version "6.1.0" - resolved "https://registry.npmjs.org/normalize-url/-/normalize-url-6.1.0.tgz" - integrity sha512-DlL+XwOy3NxAQ8xuC0okPgK46iuVNAK01YN7RueYBqqFeGsBjV9XmCAzAdgt+667bCl5kPh9EqKKDwnaPG1I7A== +normalize-url@^8.0.0: + version "8.0.1" + resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-8.0.1.tgz#9b7d96af9836577c58f5883e939365fa15623a4a" + integrity sha512-IO9QvjUMWxPQQhs60oOu10CRkWCiZzSUkzbXGGV9pviYl1fXYcvkzQ5jV9z8Y6un8ARoVRl4EtC6v6jNqbaJ/w== npm-run-path@^4.0.1: version "4.0.1" @@ -5470,7 +6915,15 @@ nth-check@^2.0.1: dependencies: boolbase "^1.0.0" -object-assign@^4.1.0, object-assign@^4.1.1: +null-loader@^4.0.1: + version "4.0.1" + resolved "https://registry.yarnpkg.com/null-loader/-/null-loader-4.0.1.tgz#8e63bd3a2dd3c64236a4679428632edd0a6dbc6a" + integrity sha512-pxqVbi4U6N26lq+LmgIbB5XATP0VdZKOG25DhHi8btMmJJefGArFyDg1yc4U3hWCJbMqSrw0qyrz1UQX+qYXqg== + dependencies: + loader-utils "^2.0.0" + schema-utils "^3.0.0" + +object-assign@^4.1.1: version "4.1.1" resolved "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz" integrity sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg== @@ -5512,7 +6965,7 @@ on-headers@~1.0.2: resolved "https://registry.npmjs.org/on-headers/-/on-headers-1.0.2.tgz" integrity sha512-pZAE+FJLoyITytdqK0U5s+FIpjN0JP3OzFi/u8Rx+EV5/W+JTWGXG8xFzevE7AjBfDqHv/8vL8qQsIhHnqRkrA== -once@^1.3.0, once@^1.3.1, once@^1.4.0: +once@^1.3.0: version "1.4.0" resolved "https://registry.npmjs.org/once/-/once-1.4.0.tgz" integrity sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w== @@ -5540,10 +6993,10 @@ opener@^1.5.2: resolved "https://registry.npmjs.org/opener/-/opener-1.5.2.tgz" integrity sha512-ur5UIdyw5Y7yEj9wLzhqXiy6GZ3Mwx0yGI+5sMn2r0N0v3cKJvUmFH5yPP+WXh9e0xfyzyJX95D8l088DNFj7A== -p-cancelable@^1.0.0: - version "1.1.0" - resolved "https://registry.npmjs.org/p-cancelable/-/p-cancelable-1.1.0.tgz" - integrity sha512-s73XxOZ4zpt1edZYZzvhqFa6uvQc1vwUa0K0BdtIZgQMAJj9IbebH+JkgKZc9h+B05PKHLOTl4ajG1BmNrVZlw== +p-cancelable@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/p-cancelable/-/p-cancelable-3.0.0.tgz#63826694b54d61ca1c20ebcb6d3ecf5e14cd8050" + integrity sha512-mlVgR3PGuzlo0MmTdk4cXqXWlwQDLnONTAg6sm62XkMJEiRxN3GL3SffkYvqwonbkJBcrI7Uvv5Zh9yjvn2iUw== p-limit@^2.0.0, p-limit@^2.2.0: version "2.3.0" @@ -5614,15 +7067,15 @@ p-try@^2.0.0: resolved "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz" integrity sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ== -package-json@^6.3.0: - version "6.5.0" - resolved "https://registry.npmjs.org/package-json/-/package-json-6.5.0.tgz" - integrity sha512-k3bdm2n25tkyxcjSKzB5x8kfVxlMdgsbPr0GkZcwHsLpba6cBjqCt1KlcChKEvxHIcTB1FVMuwoijZ26xex5MQ== +package-json@^8.1.0: + version "8.1.1" + resolved "https://registry.yarnpkg.com/package-json/-/package-json-8.1.1.tgz#3e9948e43df40d1e8e78a85485f1070bf8f03dc8" + integrity sha512-cbH9IAIJHNj9uXi196JVsRlt7cHKak6u/e6AkL/bkRelZ7rlL3X1YKxsZwa36xipOEKAsdtmaG6aAJoM1fx2zA== dependencies: - got "^9.6.0" - registry-auth-token "^4.0.0" - registry-url "^5.0.0" - semver "^6.2.0" + got "^12.1.0" + registry-auth-token "^5.0.1" + registry-url "^6.0.0" + semver "^7.3.7" param-case@^3.0.4: version "3.0.4" @@ -5639,19 +7092,20 @@ parent-module@^1.0.0: dependencies: callsites "^3.0.0" -parse-entities@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/parse-entities/-/parse-entities-2.0.0.tgz" - integrity sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ== +parse-entities@^4.0.0: + version "4.0.2" + resolved "https://registry.yarnpkg.com/parse-entities/-/parse-entities-4.0.2.tgz#61d46f5ed28e4ee62e9ddc43d6b010188443f159" + integrity sha512-GG2AQYWoLgL877gQIKeRPGO1xF9+eG1ujIb5soS5gPvLQ1y2o8FL90w2QWNdf9I361Mpp7726c+lj3U0qK1uGw== dependencies: - character-entities "^1.0.0" - character-entities-legacy "^1.0.0" - character-reference-invalid "^1.0.0" - is-alphanumerical "^1.0.0" - is-decimal "^1.0.0" - is-hexadecimal "^1.0.0" - -parse-json@^5.0.0: + "@types/unist" "^2.0.0" + character-entities-legacy "^3.0.0" + character-reference-invalid "^2.0.0" + decode-named-character-reference "^1.0.0" + is-alphanumerical "^2.0.0" + is-decimal "^2.0.0" + is-hexadecimal "^2.0.0" + +parse-json@^5.0.0, parse-json@^5.2.0: version "5.2.0" resolved "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz" integrity sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg== @@ -5674,11 +7128,6 @@ parse5-htmlparser2-tree-adapter@^7.0.0: domhandler "^5.0.2" parse5 "^7.0.0" -parse5@^6.0.0: - version "6.0.1" - resolved "https://registry.npmjs.org/parse5/-/parse5-6.0.1.tgz" - integrity sha512-Ofn/CTFzRGTTxwpNEs9PP93gXShHcTq255nzRYSKe8AkVpZY7e1fpmTfOyoIvjP5HG7Z2ZM7VS9PPhQGW2pOpw== - parse5@^7.0.0: version "7.1.2" resolved "https://registry.npmjs.org/parse5/-/parse5-7.1.2.tgz" @@ -5739,10 +7188,10 @@ path-to-regexp@0.1.10: resolved "https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-0.1.10.tgz" integrity sha512-7lf7qcQidTku0Gu3YDPc8DJ1q7OOucfa/BSsIwjuh56VU7katFvuM8hULfkwB3Fns/rsVF7PwPKVw1sl5KQS9w== -path-to-regexp@2.2.1: - version "2.2.1" - resolved "https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-2.2.1.tgz" - integrity sha512-gu9bD6Ta5bwGrrU8muHzVOBFFREpp2iRkVfhBJahwJ6p6Xw20SjT0MxLnwkjOibQmGSYhiUnf2FLe7k+jcFmGQ== +path-to-regexp@3.3.0: + version "3.3.0" + resolved "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-3.3.0.tgz#f7f31d32e8518c2660862b644414b6d5c63a611b" + integrity sha512-qyCH421YQPS2WFDxDjftfc1ZR5WKQzVzqsp4n9M2kQhVOo/ByahFoUNJfl58kOcEGfQ//7weFTDhm+ss8Ecxgw== path-to-regexp@^1.7.0: version "1.9.0" @@ -5756,7 +7205,7 @@ path-type@^4.0.0: resolved "https://registry.npmjs.org/path-type/-/path-type-4.0.0.tgz" integrity sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw== -picocolors@^1.0.0, picocolors@^1.1.0: +picocolors@^1.0.0, picocolors@^1.0.1, picocolors@^1.1.0, picocolors@^1.1.1: version "1.1.1" resolved "https://registry.npmjs.org/picocolors/-/picocolors-1.1.1.tgz" integrity sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA== @@ -5780,6 +7229,13 @@ pkg-dir@^6.0.1: dependencies: find-up "^6.1.0" +pkg-dir@^7.0.0: + version "7.0.0" + resolved "https://registry.yarnpkg.com/pkg-dir/-/pkg-dir-7.0.0.tgz#8f0c08d6df4476756c5ff29b3282d0bab7517d11" + integrity sha512-Ie9z/WINcxxLp27BKOCHGde4ITq9UklYKDzVo1nhk5sqGEXU3FpkwP5GM2voTGJkGd9B3Otl+Q4uwSOeSUtOBA== + dependencies: + find-up "^6.3.0" + pkg-up@^3.1.0: version "3.1.0" resolved "https://registry.npmjs.org/pkg-up/-/pkg-up-3.1.0.tgz" @@ -5787,146 +7243,284 @@ pkg-up@^3.1.0: dependencies: find-up "^3.0.0" -postcss-calc@^8.2.3: - version "8.2.4" - resolved "https://registry.npmjs.org/postcss-calc/-/postcss-calc-8.2.4.tgz" - integrity sha512-SmWMSJmB8MRnnULldx0lQIyhSNvuDl9HfrZkaqqE/WHAhToYsAvDq+yAsA/kIyINDszOp3Rh0GFoNuH5Ypsm3Q== +postcss-attribute-case-insensitive@^7.0.1: + version "7.0.1" + resolved "https://registry.yarnpkg.com/postcss-attribute-case-insensitive/-/postcss-attribute-case-insensitive-7.0.1.tgz#0c4500e3bcb2141848e89382c05b5a31c23033a3" + integrity sha512-Uai+SupNSqzlschRyNx3kbCTWgY/2hcwtHEI/ej2LJWc9JJ77qKgGptd8DHwY1mXtZ7Aoh4z4yxfwMBue9eNgw== + dependencies: + postcss-selector-parser "^7.0.0" + +postcss-calc@^9.0.1: + version "9.0.1" + resolved "https://registry.yarnpkg.com/postcss-calc/-/postcss-calc-9.0.1.tgz#a744fd592438a93d6de0f1434c572670361eb6c6" + integrity sha512-TipgjGyzP5QzEhsOZUaIkeO5mKeMFpebWzRogWG/ysonUlnHcq5aJe0jOjpfzUU8PeSaBQnrE8ehR0QA5vs8PQ== dependencies: - postcss-selector-parser "^6.0.9" + postcss-selector-parser "^6.0.11" postcss-value-parser "^4.2.0" -postcss-colormin@^5.3.0: - version "5.3.0" - resolved "https://registry.npmjs.org/postcss-colormin/-/postcss-colormin-5.3.0.tgz" - integrity sha512-WdDO4gOFG2Z8n4P8TWBpshnL3JpmNmJwdnfP2gbk2qBA8PWwOYcmjmI/t3CmMeL72a7Hkd+x/Mg9O2/0rD54Pg== +postcss-clamp@^4.1.0: + version "4.1.0" + resolved "https://registry.yarnpkg.com/postcss-clamp/-/postcss-clamp-4.1.0.tgz#7263e95abadd8c2ba1bd911b0b5a5c9c93e02363" + integrity sha512-ry4b1Llo/9zz+PKC+030KUnPITTJAHeOwjfAyyB60eT0AorGLdzp52s31OsPRHRf8NchkgFoG2y6fCfn1IV1Ow== + dependencies: + postcss-value-parser "^4.2.0" + +postcss-color-functional-notation@^7.0.6: + version "7.0.6" + resolved "https://registry.yarnpkg.com/postcss-color-functional-notation/-/postcss-color-functional-notation-7.0.6.tgz#d74c1e2294b72287eb9af079c04b7ddeff7ec5b3" + integrity sha512-wLXvm8RmLs14Z2nVpB4CWlnvaWPRcOZFltJSlcbYwSJ1EDZKsKDhPKIMecCnuU054KSmlmubkqczmm6qBPCBhA== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +postcss-color-hex-alpha@^10.0.0: + version "10.0.0" + resolved "https://registry.yarnpkg.com/postcss-color-hex-alpha/-/postcss-color-hex-alpha-10.0.0.tgz#5dd3eba1f8facb4ea306cba6e3f7712e876b0c76" + integrity sha512-1kervM2cnlgPs2a8Vt/Qbe5cQ++N7rkYo/2rz2BkqJZIHQwaVuJgQH38REHrAi4uM0b1fqxMkWYmese94iMp3w== + dependencies: + "@csstools/utilities" "^2.0.0" + postcss-value-parser "^4.2.0" + +postcss-color-rebeccapurple@^10.0.0: + version "10.0.0" + resolved "https://registry.yarnpkg.com/postcss-color-rebeccapurple/-/postcss-color-rebeccapurple-10.0.0.tgz#5ada28406ac47e0796dff4056b0a9d5a6ecead98" + integrity sha512-JFta737jSP+hdAIEhk1Vs0q0YF5P8fFcj+09pweS8ktuGuZ8pPlykHsk6mPxZ8awDl4TrcxUqJo9l1IhVr/OjQ== + dependencies: + "@csstools/utilities" "^2.0.0" + postcss-value-parser "^4.2.0" + +postcss-colormin@^6.1.0: + version "6.1.0" + resolved "https://registry.yarnpkg.com/postcss-colormin/-/postcss-colormin-6.1.0.tgz#076e8d3fb291fbff7b10e6b063be9da42ff6488d" + integrity sha512-x9yX7DOxeMAR+BgGVnNSAxmAj98NX/YxEMNFP+SDCEeNLb2r3i6Hh1ksMsnW8Ub5SLCpbescQqn9YEbE9554Sw== dependencies: - browserslist "^4.16.6" + browserslist "^4.23.0" caniuse-api "^3.0.0" - colord "^2.9.1" + colord "^2.9.3" postcss-value-parser "^4.2.0" -postcss-convert-values@^5.1.3: - version "5.1.3" - resolved "https://registry.npmjs.org/postcss-convert-values/-/postcss-convert-values-5.1.3.tgz" - integrity sha512-82pC1xkJZtcJEfiLw6UXnXVXScgtBrjlO5CBmuDQc+dlb88ZYheFsjTn40+zBVi3DkfF7iezO0nJUPLcJK3pvA== +postcss-convert-values@^6.1.0: + version "6.1.0" + resolved "https://registry.yarnpkg.com/postcss-convert-values/-/postcss-convert-values-6.1.0.tgz#3498387f8efedb817cbc63901d45bd1ceaa40f48" + integrity sha512-zx8IwP/ts9WvUM6NkVSkiU902QZL1bwPhaVaLynPtCsOTqp+ZKbNi+s6XJg3rfqpKGA/oc7Oxk5t8pOQJcwl/w== dependencies: - browserslist "^4.21.4" + browserslist "^4.23.0" postcss-value-parser "^4.2.0" -postcss-discard-comments@^5.1.2: - version "5.1.2" - resolved "https://registry.npmjs.org/postcss-discard-comments/-/postcss-discard-comments-5.1.2.tgz" - integrity sha512-+L8208OVbHVF2UQf1iDmRcbdjJkuBF6IS29yBDSiWUIzpYaAhtNl6JYnYm12FnkeCwQqF5LeklOu6rAqgfBZqQ== +postcss-custom-media@^11.0.5: + version "11.0.5" + resolved "https://registry.yarnpkg.com/postcss-custom-media/-/postcss-custom-media-11.0.5.tgz#2fcd88a9b1d4da41c67dac6f2def903063a3377d" + integrity sha512-SQHhayVNgDvSAdX9NQ/ygcDQGEY+aSF4b/96z7QUX6mqL5yl/JgG/DywcF6fW9XbnCRE+aVYk+9/nqGuzOPWeQ== + dependencies: + "@csstools/cascade-layer-name-parser" "^2.0.4" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/media-query-list-parser" "^4.0.2" + +postcss-custom-properties@^14.0.4: + version "14.0.4" + resolved "https://registry.yarnpkg.com/postcss-custom-properties/-/postcss-custom-properties-14.0.4.tgz#de9c663285a98833a946d7003a34369d3ce373a9" + integrity sha512-QnW8FCCK6q+4ierwjnmXF9Y9KF8q0JkbgVfvQEMa93x1GT8FvOiUevWCN2YLaOWyByeDX8S6VFbZEeWoAoXs2A== + dependencies: + "@csstools/cascade-layer-name-parser" "^2.0.4" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/utilities" "^2.0.0" + postcss-value-parser "^4.2.0" -postcss-discard-duplicates@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-discard-duplicates/-/postcss-discard-duplicates-5.1.0.tgz" - integrity sha512-zmX3IoSI2aoenxHV6C7plngHWWhUOV3sP1T8y2ifzxzbtnuhk1EdPwm0S1bIUNaJ2eNbWeGLEwzw8huPD67aQw== +postcss-custom-selectors@^8.0.4: + version "8.0.4" + resolved "https://registry.yarnpkg.com/postcss-custom-selectors/-/postcss-custom-selectors-8.0.4.tgz#95ef8268fdbbbd84f34cf84a4517c9d99d419c5a" + integrity sha512-ASOXqNvDCE0dAJ/5qixxPeL1aOVGHGW2JwSy7HyjWNbnWTQCl+fDc968HY1jCmZI0+BaYT5CxsOiUhavpG/7eg== + dependencies: + "@csstools/cascade-layer-name-parser" "^2.0.4" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + postcss-selector-parser "^7.0.0" -postcss-discard-empty@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-discard-empty/-/postcss-discard-empty-5.1.1.tgz" - integrity sha512-zPz4WljiSuLWsI0ir4Mcnr4qQQ5e1Ukc3i7UfE2XcrwKK2LIPIqE5jxMRxO6GbI3cv//ztXDsXwEWT3BHOGh3A== +postcss-dir-pseudo-class@^9.0.1: + version "9.0.1" + resolved "https://registry.yarnpkg.com/postcss-dir-pseudo-class/-/postcss-dir-pseudo-class-9.0.1.tgz#80d9e842c9ae9d29f6bf5fd3cf9972891d6cc0ca" + integrity sha512-tRBEK0MHYvcMUrAuYMEOa0zg9APqirBcgzi6P21OhxtJyJADo/SWBwY1CAwEohQ/6HDaa9jCjLRG7K3PVQYHEA== + dependencies: + postcss-selector-parser "^7.0.0" -postcss-discard-overridden@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-discard-overridden/-/postcss-discard-overridden-5.1.0.tgz" - integrity sha512-21nOL7RqWR1kasIVdKs8HNqQJhFxLsyRfAnUDm4Fe4t4mCWL9OJiHvlHPjcd8zc5Myu89b/7wZDnOSjFgeWRtw== +postcss-discard-comments@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-discard-comments/-/postcss-discard-comments-6.0.2.tgz#e768dcfdc33e0216380623652b0a4f69f4678b6c" + integrity sha512-65w/uIqhSBBfQmYnG92FO1mWZjJ4GL5b8atm5Yw2UgrwD7HiNiSSNwJor1eCFGzUgYnN/iIknhNRVqjrrpuglw== -postcss-discard-unused@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-discard-unused/-/postcss-discard-unused-5.1.0.tgz" - integrity sha512-KwLWymI9hbwXmJa0dkrzpRbSJEh0vVUd7r8t0yOGPcfKzyJJxFM8kLyC5Ev9avji6nY95pOp1W6HqIrfT+0VGw== +postcss-discard-duplicates@^6.0.3: + version "6.0.3" + resolved "https://registry.yarnpkg.com/postcss-discard-duplicates/-/postcss-discard-duplicates-6.0.3.tgz#d121e893c38dc58a67277f75bb58ba43fce4c3eb" + integrity sha512-+JA0DCvc5XvFAxwx6f/e68gQu/7Z9ud584VLmcgto28eB8FqSFZwtrLwB5Kcp70eIoWP/HXqz4wpo8rD8gpsTw== + +postcss-discard-empty@^6.0.3: + version "6.0.3" + resolved "https://registry.yarnpkg.com/postcss-discard-empty/-/postcss-discard-empty-6.0.3.tgz#ee39c327219bb70473a066f772621f81435a79d9" + integrity sha512-znyno9cHKQsK6PtxL5D19Fj9uwSzC2mB74cpT66fhgOadEUPyXFkbgwm5tvc3bt3NAy8ltE5MrghxovZRVnOjQ== + +postcss-discard-overridden@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-discard-overridden/-/postcss-discard-overridden-6.0.2.tgz#4e9f9c62ecd2df46e8fdb44dc17e189776572e2d" + integrity sha512-j87xzI4LUggC5zND7KdjsI25APtyMuynXZSujByMaav2roV6OZX+8AaCUcZSWqckZpjAjRyFDdpqybgjFO0HJQ== + +postcss-discard-unused@^6.0.5: + version "6.0.5" + resolved "https://registry.yarnpkg.com/postcss-discard-unused/-/postcss-discard-unused-6.0.5.tgz#c1b0e8c032c6054c3fbd22aaddba5b248136f338" + integrity sha512-wHalBlRHkaNnNwfC8z+ppX57VhvS+HWgjW508esjdaEYr3Mx7Gnn2xA4R/CKf5+Z9S5qsqC+Uzh4ueENWwCVUA== dependencies: - postcss-selector-parser "^6.0.5" + postcss-selector-parser "^6.0.16" -postcss-loader@^7.0.0: - version "7.0.2" - resolved "https://registry.npmjs.org/postcss-loader/-/postcss-loader-7.0.2.tgz" - integrity sha512-fUJzV/QH7NXUAqV8dWJ9Lg4aTkDCezpTS5HgJ2DvqznexTbSTxgi/dTECvTZ15BwKTtk8G/bqI/QTu2HPd3ZCg== +postcss-double-position-gradients@^6.0.0: + version "6.0.0" + resolved "https://registry.yarnpkg.com/postcss-double-position-gradients/-/postcss-double-position-gradients-6.0.0.tgz#eddd424ec754bb543d057d4d2180b1848095d4d2" + integrity sha512-JkIGah3RVbdSEIrcobqj4Gzq0h53GG4uqDPsho88SgY84WnpkTpI0k50MFK/sX7XqVisZ6OqUfFnoUO6m1WWdg== dependencies: - cosmiconfig "^7.0.0" - klona "^2.0.5" - semver "^7.3.8" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + postcss-value-parser "^4.2.0" -postcss-merge-idents@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-merge-idents/-/postcss-merge-idents-5.1.1.tgz" - integrity sha512-pCijL1TREiCoog5nQp7wUe+TUonA2tC2sQ54UGeMmryK3UFGIYKqDyjnqd6RcuI4znFn9hWSLNN8xKE/vWcUQw== +postcss-focus-visible@^10.0.1: + version "10.0.1" + resolved "https://registry.yarnpkg.com/postcss-focus-visible/-/postcss-focus-visible-10.0.1.tgz#1f7904904368a2d1180b220595d77b6f8a957868" + integrity sha512-U58wyjS/I1GZgjRok33aE8juW9qQgQUNwTSdxQGuShHzwuYdcklnvK/+qOWX1Q9kr7ysbraQ6ht6r+udansalA== dependencies: - cssnano-utils "^3.1.0" + postcss-selector-parser "^7.0.0" + +postcss-focus-within@^9.0.1: + version "9.0.1" + resolved "https://registry.yarnpkg.com/postcss-focus-within/-/postcss-focus-within-9.0.1.tgz#ac01ce80d3f2e8b2b3eac4ff84f8e15cd0057bc7" + integrity sha512-fzNUyS1yOYa7mOjpci/bR+u+ESvdar6hk8XNK/TRR0fiGTp2QT5N+ducP0n3rfH/m9I7H/EQU6lsa2BrgxkEjw== + dependencies: + postcss-selector-parser "^7.0.0" + +postcss-font-variant@^5.0.0: + version "5.0.0" + resolved "https://registry.yarnpkg.com/postcss-font-variant/-/postcss-font-variant-5.0.0.tgz#efd59b4b7ea8bb06127f2d031bfbb7f24d32fa66" + integrity sha512-1fmkBaCALD72CK2a9i468mA/+tr9/1cBxRRMXOUaZqO43oWPR5imcyPjXwuv7PXbCid4ndlP5zWhidQVVa3hmA== + +postcss-gap-properties@^6.0.0: + version "6.0.0" + resolved "https://registry.yarnpkg.com/postcss-gap-properties/-/postcss-gap-properties-6.0.0.tgz#d5ff0bdf923c06686499ed2b12e125fe64054fed" + integrity sha512-Om0WPjEwiM9Ru+VhfEDPZJAKWUd0mV1HmNXqp2C29z80aQ2uP9UVhLc7e3aYMIor/S5cVhoPgYQ7RtfeZpYTRw== + +postcss-image-set-function@^7.0.0: + version "7.0.0" + resolved "https://registry.yarnpkg.com/postcss-image-set-function/-/postcss-image-set-function-7.0.0.tgz#538e94e16716be47f9df0573b56bbaca86e1da53" + integrity sha512-QL7W7QNlZuzOwBTeXEmbVckNt1FSmhQtbMRvGGqqU4Nf4xk6KUEQhAoWuMzwbSv5jxiRiSZ5Tv7eiDB9U87znA== + dependencies: + "@csstools/utilities" "^2.0.0" + postcss-value-parser "^4.2.0" + +postcss-lab-function@^7.0.6: + version "7.0.6" + resolved "https://registry.yarnpkg.com/postcss-lab-function/-/postcss-lab-function-7.0.6.tgz#3121800fc7939ed1d9a1e87abeb33c407151252c" + integrity sha512-HPwvsoK7C949vBZ+eMyvH2cQeMr3UREoHvbtra76/UhDuiViZH6pir+z71UaJQohd7VDSVUdR6TkWYKExEc9aQ== + dependencies: + "@csstools/css-color-parser" "^3.0.6" + "@csstools/css-parser-algorithms" "^3.0.4" + "@csstools/css-tokenizer" "^3.0.3" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/utilities" "^2.0.0" + +postcss-loader@^7.3.3: + version "7.3.4" + resolved "https://registry.yarnpkg.com/postcss-loader/-/postcss-loader-7.3.4.tgz#aed9b79ce4ed7e9e89e56199d25ad1ec8f606209" + integrity sha512-iW5WTTBSC5BfsBJ9daFMPVrLT36MrNiC6fqOZTTaHjBNX6Pfd5p+hSBqe/fEeNd7pc13QiAyGt7VdGMw4eRC4A== + dependencies: + cosmiconfig "^8.3.5" + jiti "^1.20.0" + semver "^7.5.4" + +postcss-logical@^8.0.0: + version "8.0.0" + resolved "https://registry.yarnpkg.com/postcss-logical/-/postcss-logical-8.0.0.tgz#0db0b90c2dc53b485a8074a4b7a906297544f58d" + integrity sha512-HpIdsdieClTjXLOyYdUPAX/XQASNIwdKt5hoZW08ZOAiI+tbV0ta1oclkpVkW5ANU+xJvk3KkA0FejkjGLXUkg== + dependencies: + postcss-value-parser "^4.2.0" + +postcss-merge-idents@^6.0.3: + version "6.0.3" + resolved "https://registry.yarnpkg.com/postcss-merge-idents/-/postcss-merge-idents-6.0.3.tgz#7b9c31c7bc823c94bec50f297f04e3c2b838ea65" + integrity sha512-1oIoAsODUs6IHQZkLQGO15uGEbK3EAl5wi9SS8hs45VgsxQfMnxvt+L+zIr7ifZFIH14cfAeVe2uCTa+SPRa3g== + dependencies: + cssnano-utils "^4.0.2" postcss-value-parser "^4.2.0" -postcss-merge-longhand@^5.1.7: - version "5.1.7" - resolved "https://registry.npmjs.org/postcss-merge-longhand/-/postcss-merge-longhand-5.1.7.tgz" - integrity sha512-YCI9gZB+PLNskrK0BB3/2OzPnGhPkBEwmwhfYk1ilBHYVAZB7/tkTHFBAnCrvBBOmeYyMYw3DMjT55SyxMBzjQ== +postcss-merge-longhand@^6.0.5: + version "6.0.5" + resolved "https://registry.yarnpkg.com/postcss-merge-longhand/-/postcss-merge-longhand-6.0.5.tgz#ba8a8d473617c34a36abbea8dda2b215750a065a" + integrity sha512-5LOiordeTfi64QhICp07nzzuTDjNSO8g5Ksdibt44d+uvIIAE1oZdRn8y/W5ZtYgRH/lnLDlvi9F8btZcVzu3w== dependencies: postcss-value-parser "^4.2.0" - stylehacks "^5.1.1" + stylehacks "^6.1.1" -postcss-merge-rules@^5.1.3: - version "5.1.3" - resolved "https://registry.npmjs.org/postcss-merge-rules/-/postcss-merge-rules-5.1.3.tgz" - integrity sha512-LbLd7uFC00vpOuMvyZop8+vvhnfRGpp2S+IMQKeuOZZapPRY4SMq5ErjQeHbHsjCUgJkRNrlU+LmxsKIqPKQlA== +postcss-merge-rules@^6.1.1: + version "6.1.1" + resolved "https://registry.yarnpkg.com/postcss-merge-rules/-/postcss-merge-rules-6.1.1.tgz#7aa539dceddab56019469c0edd7d22b64c3dea9d" + integrity sha512-KOdWF0gju31AQPZiD+2Ar9Qjowz1LTChSjFFbS+e2sFgc4uHOp3ZvVX4sNeTlk0w2O31ecFGgrFzhO0RSWbWwQ== dependencies: - browserslist "^4.21.4" + browserslist "^4.23.0" caniuse-api "^3.0.0" - cssnano-utils "^3.1.0" - postcss-selector-parser "^6.0.5" + cssnano-utils "^4.0.2" + postcss-selector-parser "^6.0.16" -postcss-minify-font-values@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-minify-font-values/-/postcss-minify-font-values-5.1.0.tgz" - integrity sha512-el3mYTgx13ZAPPirSVsHqFzl+BBBDrXvbySvPGFnQcTI4iNslrPaFq4muTkLZmKlGk4gyFAYUBMH30+HurREyA== +postcss-minify-font-values@^6.1.0: + version "6.1.0" + resolved "https://registry.yarnpkg.com/postcss-minify-font-values/-/postcss-minify-font-values-6.1.0.tgz#a0e574c02ee3f299be2846369211f3b957ea4c59" + integrity sha512-gklfI/n+9rTh8nYaSJXlCo3nOKqMNkxuGpTn/Qm0gstL3ywTr9/WRKznE+oy6fvfolH6dF+QM4nCo8yPLdvGJg== dependencies: postcss-value-parser "^4.2.0" -postcss-minify-gradients@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-minify-gradients/-/postcss-minify-gradients-5.1.1.tgz" - integrity sha512-VGvXMTpCEo4qHTNSa9A0a3D+dxGFZCYwR6Jokk+/3oB6flu2/PnPXAh2x7x52EkY5xlIHLm+Le8tJxe/7TNhzw== +postcss-minify-gradients@^6.0.3: + version "6.0.3" + resolved "https://registry.yarnpkg.com/postcss-minify-gradients/-/postcss-minify-gradients-6.0.3.tgz#ca3eb55a7bdb48a1e187a55c6377be918743dbd6" + integrity sha512-4KXAHrYlzF0Rr7uc4VrfwDJ2ajrtNEpNEuLxFgwkhFZ56/7gaE4Nr49nLsQDZyUe+ds+kEhf+YAUolJiYXF8+Q== dependencies: - colord "^2.9.1" - cssnano-utils "^3.1.0" + colord "^2.9.3" + cssnano-utils "^4.0.2" postcss-value-parser "^4.2.0" -postcss-minify-params@^5.1.4: - version "5.1.4" - resolved "https://registry.npmjs.org/postcss-minify-params/-/postcss-minify-params-5.1.4.tgz" - integrity sha512-+mePA3MgdmVmv6g+30rn57USjOGSAyuxUmkfiWpzalZ8aiBkdPYjXWtHuwJGm1v5Ojy0Z0LaSYhHaLJQB0P8Jw== +postcss-minify-params@^6.1.0: + version "6.1.0" + resolved "https://registry.yarnpkg.com/postcss-minify-params/-/postcss-minify-params-6.1.0.tgz#54551dec77b9a45a29c3cb5953bf7325a399ba08" + integrity sha512-bmSKnDtyyE8ujHQK0RQJDIKhQ20Jq1LYiez54WiaOoBtcSuflfK3Nm596LvbtlFcpipMjgClQGyGr7GAs+H1uA== dependencies: - browserslist "^4.21.4" - cssnano-utils "^3.1.0" + browserslist "^4.23.0" + cssnano-utils "^4.0.2" postcss-value-parser "^4.2.0" -postcss-minify-selectors@^5.2.1: - version "5.2.1" - resolved "https://registry.npmjs.org/postcss-minify-selectors/-/postcss-minify-selectors-5.2.1.tgz" - integrity sha512-nPJu7OjZJTsVUmPdm2TcaiohIwxP+v8ha9NehQ2ye9szv4orirRU3SDdtUmKH+10nzn0bAyOXZ0UEr7OpvLehg== +postcss-minify-selectors@^6.0.4: + version "6.0.4" + resolved "https://registry.yarnpkg.com/postcss-minify-selectors/-/postcss-minify-selectors-6.0.4.tgz#197f7d72e6dd19eed47916d575d69dc38b396aff" + integrity sha512-L8dZSwNLgK7pjTto9PzWRoMbnLq5vsZSTu8+j1P/2GB8qdtGQfn+K1uSvFgYvgh83cbyxT5m43ZZhUMTJDSClQ== dependencies: - postcss-selector-parser "^6.0.5" + postcss-selector-parser "^6.0.16" -postcss-modules-extract-imports@^3.0.0: - version "3.0.0" - resolved "https://registry.npmjs.org/postcss-modules-extract-imports/-/postcss-modules-extract-imports-3.0.0.tgz" - integrity sha512-bdHleFnP3kZ4NYDhuGlVK+CMrQ/pqUm8bx/oGL93K6gVwiclvX5x0n76fYMKuIGKzlABOy13zsvqjb0f92TEXw== +postcss-modules-extract-imports@^3.1.0: + version "3.1.0" + resolved "https://registry.yarnpkg.com/postcss-modules-extract-imports/-/postcss-modules-extract-imports-3.1.0.tgz#b4497cb85a9c0c4b5aabeb759bb25e8d89f15002" + integrity sha512-k3kNe0aNFQDAZGbin48pL2VNidTF0w4/eASDsxlyspobzU3wZQLOGj7L9gfRe0Jo9/4uud09DsjFNH7winGv8Q== -postcss-modules-local-by-default@^4.0.0: - version "4.0.0" - resolved "https://registry.npmjs.org/postcss-modules-local-by-default/-/postcss-modules-local-by-default-4.0.0.tgz" - integrity sha512-sT7ihtmGSF9yhm6ggikHdV0hlziDTX7oFoXtuVWeDd3hHObNkcHRo9V3yg7vCAY7cONyxJC/XXCmmiHHcvX7bQ== +postcss-modules-local-by-default@^4.0.5: + version "4.2.0" + resolved "https://registry.yarnpkg.com/postcss-modules-local-by-default/-/postcss-modules-local-by-default-4.2.0.tgz#d150f43837831dae25e4085596e84f6f5d6ec368" + integrity sha512-5kcJm/zk+GJDSfw+V/42fJ5fhjL5YbFDl8nVdXkJPLLW+Vf9mTD5Xe0wqIaDnLuL2U6cDNpTr+UQ+v2HWIBhzw== dependencies: icss-utils "^5.0.0" - postcss-selector-parser "^6.0.2" + postcss-selector-parser "^7.0.0" postcss-value-parser "^4.1.0" -postcss-modules-scope@^3.0.0: - version "3.0.0" - resolved "https://registry.npmjs.org/postcss-modules-scope/-/postcss-modules-scope-3.0.0.tgz" - integrity sha512-hncihwFA2yPath8oZ15PZqvWGkWf+XUfQgUGamS4LqoP1anQLOsOJw0vr7J7IwLpoY9fatA2qiGUGmuZL0Iqlg== +postcss-modules-scope@^3.2.0: + version "3.2.1" + resolved "https://registry.yarnpkg.com/postcss-modules-scope/-/postcss-modules-scope-3.2.1.tgz#1bbccddcb398f1d7a511e0a2d1d047718af4078c" + integrity sha512-m9jZstCVaqGjTAuny8MdgE88scJnCiQSlSrOWcTQgM2t32UBe+MUmFSO5t7VMSfAf/FJKImAxBav8ooCHJXCJA== dependencies: - postcss-selector-parser "^6.0.4" + postcss-selector-parser "^7.0.0" postcss-modules-values@^4.0.0: version "4.0.0" @@ -5935,152 +7529,275 @@ postcss-modules-values@^4.0.0: dependencies: icss-utils "^5.0.0" -postcss-normalize-charset@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-normalize-charset/-/postcss-normalize-charset-5.1.0.tgz" - integrity sha512-mSgUJ+pd/ldRGVx26p2wz9dNZ7ji6Pn8VWBajMXFf8jk7vUoSrZ2lt/wZR7DtlZYKesmZI680qjr2CeFF2fbUg== +postcss-nesting@^13.0.1: + version "13.0.1" + resolved "https://registry.yarnpkg.com/postcss-nesting/-/postcss-nesting-13.0.1.tgz#c405796d7245a3e4c267a9956cacfe9670b5d43e" + integrity sha512-VbqqHkOBOt4Uu3G8Dm8n6lU5+9cJFxiuty9+4rcoyRPO9zZS1JIs6td49VIoix3qYqELHlJIn46Oih9SAKo+yQ== + dependencies: + "@csstools/selector-resolve-nested" "^3.0.0" + "@csstools/selector-specificity" "^5.0.0" + postcss-selector-parser "^7.0.0" -postcss-normalize-display-values@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-normalize-display-values/-/postcss-normalize-display-values-5.1.0.tgz" - integrity sha512-WP4KIM4o2dazQXWmFaqMmcvsKmhdINFblgSeRgn8BJ6vxaMyaJkwAzpPpuvSIoG/rmX3M+IrRZEz2H0glrQNEA== +postcss-normalize-charset@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-normalize-charset/-/postcss-normalize-charset-6.0.2.tgz#1ec25c435057a8001dac942942a95ffe66f721e1" + integrity sha512-a8N9czmdnrjPHa3DeFlwqst5eaL5W8jYu3EBbTTkI5FHkfMhFZh1EGbku6jhHhIzTA6tquI2P42NtZ59M/H/kQ== + +postcss-normalize-display-values@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-normalize-display-values/-/postcss-normalize-display-values-6.0.2.tgz#54f02764fed0b288d5363cbb140d6950dbbdd535" + integrity sha512-8H04Mxsb82ON/aAkPeq8kcBbAtI5Q2a64X/mnRRfPXBq7XeogoQvReqxEfc0B4WPq1KimjezNC8flUtC3Qz6jg== dependencies: postcss-value-parser "^4.2.0" -postcss-normalize-positions@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-normalize-positions/-/postcss-normalize-positions-5.1.1.tgz" - integrity sha512-6UpCb0G4eofTCQLFVuI3EVNZzBNPiIKcA1AKVka+31fTVySphr3VUgAIULBhxZkKgwLImhzMR2Bw1ORK+37INg== +postcss-normalize-positions@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-normalize-positions/-/postcss-normalize-positions-6.0.2.tgz#e982d284ec878b9b819796266f640852dbbb723a" + integrity sha512-/JFzI441OAB9O7VnLA+RtSNZvQ0NCFZDOtp6QPFo1iIyawyXg0YI3CYM9HBy1WvwCRHnPep/BvI1+dGPKoXx/Q== dependencies: postcss-value-parser "^4.2.0" -postcss-normalize-repeat-style@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-normalize-repeat-style/-/postcss-normalize-repeat-style-5.1.1.tgz" - integrity sha512-mFpLspGWkQtBcWIRFLmewo8aC3ImN2i/J3v8YCFUwDnPu3Xz4rLohDO26lGjwNsQxB3YF0KKRwspGzE2JEuS0g== +postcss-normalize-repeat-style@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-normalize-repeat-style/-/postcss-normalize-repeat-style-6.0.2.tgz#f8006942fd0617c73f049dd8b6201c3a3040ecf3" + integrity sha512-YdCgsfHkJ2jEXwR4RR3Tm/iOxSfdRt7jplS6XRh9Js9PyCR/aka/FCb6TuHT2U8gQubbm/mPmF6L7FY9d79VwQ== dependencies: postcss-value-parser "^4.2.0" -postcss-normalize-string@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-normalize-string/-/postcss-normalize-string-5.1.0.tgz" - integrity sha512-oYiIJOf4T9T1N4i+abeIc7Vgm/xPCGih4bZz5Nm0/ARVJ7K6xrDlLwvwqOydvyL3RHNf8qZk6vo3aatiw/go3w== +postcss-normalize-string@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-normalize-string/-/postcss-normalize-string-6.0.2.tgz#e3cc6ad5c95581acd1fc8774b309dd7c06e5e363" + integrity sha512-vQZIivlxlfqqMp4L9PZsFE4YUkWniziKjQWUtsxUiVsSSPelQydwS8Wwcuw0+83ZjPWNTl02oxlIvXsmmG+CiQ== dependencies: postcss-value-parser "^4.2.0" -postcss-normalize-timing-functions@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-normalize-timing-functions/-/postcss-normalize-timing-functions-5.1.0.tgz" - integrity sha512-DOEkzJ4SAXv5xkHl0Wa9cZLF3WCBhF3o1SKVxKQAa+0pYKlueTpCgvkFAHfk+Y64ezX9+nITGrDZeVGgITJXjg== +postcss-normalize-timing-functions@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-normalize-timing-functions/-/postcss-normalize-timing-functions-6.0.2.tgz#40cb8726cef999de984527cbd9d1db1f3e9062c0" + integrity sha512-a+YrtMox4TBtId/AEwbA03VcJgtyW4dGBizPl7e88cTFULYsprgHWTbfyjSLyHeBcK/Q9JhXkt2ZXiwaVHoMzA== dependencies: postcss-value-parser "^4.2.0" -postcss-normalize-unicode@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-normalize-unicode/-/postcss-normalize-unicode-5.1.1.tgz" - integrity sha512-qnCL5jzkNUmKVhZoENp1mJiGNPcsJCs1aaRmURmeJGES23Z/ajaln+EPTD+rBeNkSryI+2WTdW+lwcVdOikrpA== +postcss-normalize-unicode@^6.1.0: + version "6.1.0" + resolved "https://registry.yarnpkg.com/postcss-normalize-unicode/-/postcss-normalize-unicode-6.1.0.tgz#aaf8bbd34c306e230777e80f7f12a4b7d27ce06e" + integrity sha512-QVC5TQHsVj33otj8/JD869Ndr5Xcc/+fwRh4HAsFsAeygQQXm+0PySrKbr/8tkDKzW+EVT3QkqZMfFrGiossDg== dependencies: - browserslist "^4.21.4" + browserslist "^4.23.0" postcss-value-parser "^4.2.0" -postcss-normalize-url@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-normalize-url/-/postcss-normalize-url-5.1.0.tgz" - integrity sha512-5upGeDO+PVthOxSmds43ZeMeZfKH+/DKgGRD7TElkkyS46JXAUhMzIKiCa7BabPeIy3AQcTkXwVVN7DbqsiCew== +postcss-normalize-url@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-normalize-url/-/postcss-normalize-url-6.0.2.tgz#292792386be51a8de9a454cb7b5c58ae22db0f79" + integrity sha512-kVNcWhCeKAzZ8B4pv/DnrU1wNh458zBNp8dh4y5hhxih5RZQ12QWMuQrDgPRw3LRl8mN9vOVfHl7uhvHYMoXsQ== dependencies: - normalize-url "^6.0.1" postcss-value-parser "^4.2.0" -postcss-normalize-whitespace@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-normalize-whitespace/-/postcss-normalize-whitespace-5.1.1.tgz" - integrity sha512-83ZJ4t3NUDETIHTa3uEg6asWjSBYL5EdkVB0sDncx9ERzOKBVJIUeDO9RyA9Zwtig8El1d79HBp0JEi8wvGQnA== +postcss-normalize-whitespace@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-normalize-whitespace/-/postcss-normalize-whitespace-6.0.2.tgz#fbb009e6ebd312f8b2efb225c2fcc7cf32b400cd" + integrity sha512-sXZ2Nj1icbJOKmdjXVT9pnyHQKiSAyuNQHSgRCUgThn2388Y9cGVDR+E9J9iAYbSbLHI+UUwLVl1Wzco/zgv0Q== dependencies: postcss-value-parser "^4.2.0" -postcss-ordered-values@^5.1.3: - version "5.1.3" - resolved "https://registry.npmjs.org/postcss-ordered-values/-/postcss-ordered-values-5.1.3.tgz" - integrity sha512-9UO79VUhPwEkzbb3RNpqqghc6lcYej1aveQteWY+4POIwlqkYE21HKWaLDF6lWNuqCobEAyTovVhtI32Rbv2RQ== +postcss-opacity-percentage@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/postcss-opacity-percentage/-/postcss-opacity-percentage-3.0.0.tgz#0b0db5ed5db5670e067044b8030b89c216e1eb0a" + integrity sha512-K6HGVzyxUxd/VgZdX04DCtdwWJ4NGLG212US4/LA1TLAbHgmAsTWVR86o+gGIbFtnTkfOpb9sCRBx8K7HO66qQ== + +postcss-ordered-values@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-ordered-values/-/postcss-ordered-values-6.0.2.tgz#366bb663919707093451ab70c3f99c05672aaae5" + integrity sha512-VRZSOB+JU32RsEAQrO94QPkClGPKJEL/Z9PCBImXMhIeK5KAYo6slP/hBYlLgrCjFxyqvn5VC81tycFEDBLG1Q== dependencies: - cssnano-utils "^3.1.0" + cssnano-utils "^4.0.2" postcss-value-parser "^4.2.0" -postcss-reduce-idents@^5.2.0: - version "5.2.0" - resolved "https://registry.npmjs.org/postcss-reduce-idents/-/postcss-reduce-idents-5.2.0.tgz" - integrity sha512-BTrLjICoSB6gxbc58D5mdBK8OhXRDqud/zodYfdSi52qvDHdMwk+9kB9xsM8yJThH/sZU5A6QVSmMmaN001gIg== +postcss-overflow-shorthand@^6.0.0: + version "6.0.0" + resolved "https://registry.yarnpkg.com/postcss-overflow-shorthand/-/postcss-overflow-shorthand-6.0.0.tgz#f5252b4a2ee16c68cd8a9029edb5370c4a9808af" + integrity sha512-BdDl/AbVkDjoTofzDQnwDdm/Ym6oS9KgmO7Gr+LHYjNWJ6ExORe4+3pcLQsLA9gIROMkiGVjjwZNoL/mpXHd5Q== dependencies: postcss-value-parser "^4.2.0" -postcss-reduce-initial@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-reduce-initial/-/postcss-reduce-initial-5.1.1.tgz" - integrity sha512-//jeDqWcHPuXGZLoolFrUXBDyuEGbr9S2rMo19bkTIjBQ4PqkaO+oI8wua5BOUxpfi97i3PCoInsiFIEBfkm9w== +postcss-page-break@^3.0.4: + version "3.0.4" + resolved "https://registry.yarnpkg.com/postcss-page-break/-/postcss-page-break-3.0.4.tgz#7fbf741c233621622b68d435babfb70dd8c1ee5f" + integrity sha512-1JGu8oCjVXLa9q9rFTo4MbeeA5FMe00/9C7lN4va606Rdb+HkxXtXsmEDrIraQ11fGz/WvKWa8gMuCKkrXpTsQ== + +postcss-place@^10.0.0: + version "10.0.0" + resolved "https://registry.yarnpkg.com/postcss-place/-/postcss-place-10.0.0.tgz#ba36ee4786ca401377ced17a39d9050ed772e5a9" + integrity sha512-5EBrMzat2pPAxQNWYavwAfoKfYcTADJ8AXGVPcUZ2UkNloUTWzJQExgrzrDkh3EKzmAx1evfTAzF9I8NGcc+qw== dependencies: - browserslist "^4.21.4" + postcss-value-parser "^4.2.0" + +postcss-preset-env@^10.1.0: + version "10.1.2" + resolved "https://registry.yarnpkg.com/postcss-preset-env/-/postcss-preset-env-10.1.2.tgz#ea9c25d92045ef06edd78f9945d2586107aab3e3" + integrity sha512-OqUBZ9ByVfngWhMNuBEMy52Izj07oIFA6K/EOGBlaSv+P12MiE1+S2cqXtS1VuW82demQ/Tzc7typYk3uHunkA== + dependencies: + "@csstools/postcss-cascade-layers" "^5.0.1" + "@csstools/postcss-color-function" "^4.0.6" + "@csstools/postcss-color-mix-function" "^3.0.6" + "@csstools/postcss-content-alt-text" "^2.0.4" + "@csstools/postcss-exponential-functions" "^2.0.5" + "@csstools/postcss-font-format-keywords" "^4.0.0" + "@csstools/postcss-gamut-mapping" "^2.0.6" + "@csstools/postcss-gradients-interpolation-method" "^5.0.6" + "@csstools/postcss-hwb-function" "^4.0.6" + "@csstools/postcss-ic-unit" "^4.0.0" + "@csstools/postcss-initial" "^2.0.0" + "@csstools/postcss-is-pseudo-class" "^5.0.1" + "@csstools/postcss-light-dark-function" "^2.0.7" + "@csstools/postcss-logical-float-and-clear" "^3.0.0" + "@csstools/postcss-logical-overflow" "^2.0.0" + "@csstools/postcss-logical-overscroll-behavior" "^2.0.0" + "@csstools/postcss-logical-resize" "^3.0.0" + "@csstools/postcss-logical-viewport-units" "^3.0.3" + "@csstools/postcss-media-minmax" "^2.0.5" + "@csstools/postcss-media-queries-aspect-ratio-number-values" "^3.0.4" + "@csstools/postcss-nested-calc" "^4.0.0" + "@csstools/postcss-normalize-display-values" "^4.0.0" + "@csstools/postcss-oklab-function" "^4.0.6" + "@csstools/postcss-progressive-custom-properties" "^4.0.0" + "@csstools/postcss-random-function" "^1.0.1" + "@csstools/postcss-relative-color-syntax" "^3.0.6" + "@csstools/postcss-scope-pseudo-class" "^4.0.1" + "@csstools/postcss-sign-functions" "^1.1.0" + "@csstools/postcss-stepped-value-functions" "^4.0.5" + "@csstools/postcss-text-decoration-shorthand" "^4.0.1" + "@csstools/postcss-trigonometric-functions" "^4.0.5" + "@csstools/postcss-unset-value" "^4.0.0" + autoprefixer "^10.4.19" + browserslist "^4.23.1" + css-blank-pseudo "^7.0.1" + css-has-pseudo "^7.0.2" + css-prefers-color-scheme "^10.0.0" + cssdb "^8.2.3" + postcss-attribute-case-insensitive "^7.0.1" + postcss-clamp "^4.1.0" + postcss-color-functional-notation "^7.0.6" + postcss-color-hex-alpha "^10.0.0" + postcss-color-rebeccapurple "^10.0.0" + postcss-custom-media "^11.0.5" + postcss-custom-properties "^14.0.4" + postcss-custom-selectors "^8.0.4" + postcss-dir-pseudo-class "^9.0.1" + postcss-double-position-gradients "^6.0.0" + postcss-focus-visible "^10.0.1" + postcss-focus-within "^9.0.1" + postcss-font-variant "^5.0.0" + postcss-gap-properties "^6.0.0" + postcss-image-set-function "^7.0.0" + postcss-lab-function "^7.0.6" + postcss-logical "^8.0.0" + postcss-nesting "^13.0.1" + postcss-opacity-percentage "^3.0.0" + postcss-overflow-shorthand "^6.0.0" + postcss-page-break "^3.0.4" + postcss-place "^10.0.0" + postcss-pseudo-class-any-link "^10.0.1" + postcss-replace-overflow-wrap "^4.0.0" + postcss-selector-not "^8.0.1" + +postcss-pseudo-class-any-link@^10.0.1: + version "10.0.1" + resolved "https://registry.yarnpkg.com/postcss-pseudo-class-any-link/-/postcss-pseudo-class-any-link-10.0.1.tgz#06455431171bf44b84d79ebaeee9fd1c05946544" + integrity sha512-3el9rXlBOqTFaMFkWDOkHUTQekFIYnaQY55Rsp8As8QQkpiSgIYEcF/6Ond93oHiDsGb4kad8zjt+NPlOC1H0Q== + dependencies: + postcss-selector-parser "^7.0.0" + +postcss-reduce-idents@^6.0.3: + version "6.0.3" + resolved "https://registry.yarnpkg.com/postcss-reduce-idents/-/postcss-reduce-idents-6.0.3.tgz#b0d9c84316d2a547714ebab523ec7d13704cd486" + integrity sha512-G3yCqZDpsNPoQgbDUy3T0E6hqOQ5xigUtBQyrmq3tn2GxlyiL0yyl7H+T8ulQR6kOcHJ9t7/9H4/R2tv8tJbMA== + dependencies: + postcss-value-parser "^4.2.0" + +postcss-reduce-initial@^6.1.0: + version "6.1.0" + resolved "https://registry.yarnpkg.com/postcss-reduce-initial/-/postcss-reduce-initial-6.1.0.tgz#4401297d8e35cb6e92c8e9586963e267105586ba" + integrity sha512-RarLgBK/CrL1qZags04oKbVbrrVK2wcxhvta3GCxrZO4zveibqbRPmm2VI8sSgCXwoUHEliRSbOfpR0b/VIoiw== + dependencies: + browserslist "^4.23.0" caniuse-api "^3.0.0" -postcss-reduce-transforms@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-reduce-transforms/-/postcss-reduce-transforms-5.1.0.tgz" - integrity sha512-2fbdbmgir5AvpW9RLtdONx1QoYG2/EtqpNQbFASDlixBbAYuTcJ0dECwlqNqH7VbaUnEnh8SrxOe2sRIn24XyQ== +postcss-reduce-transforms@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-reduce-transforms/-/postcss-reduce-transforms-6.0.2.tgz#6fa2c586bdc091a7373caeee4be75a0f3e12965d" + integrity sha512-sB+Ya++3Xj1WaT9+5LOOdirAxP7dJZms3GRcYheSPi1PiTMigsxHAdkrbItHxwYHr4kt1zL7mmcHstgMYT+aiA== dependencies: postcss-value-parser "^4.2.0" -postcss-selector-parser@^6.0.2, postcss-selector-parser@^6.0.4, postcss-selector-parser@^6.0.5, postcss-selector-parser@^6.0.9: - version "6.0.11" - resolved "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.0.11.tgz" - integrity sha512-zbARubNdogI9j7WY4nQJBiNqQf3sLS3wCP4WfOidu+p28LofJqDH1tcXypGrcmMHhDk2t9wGhCsYe/+szLTy1g== +postcss-replace-overflow-wrap@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/postcss-replace-overflow-wrap/-/postcss-replace-overflow-wrap-4.0.0.tgz#d2df6bed10b477bf9c52fab28c568b4b29ca4319" + integrity sha512-KmF7SBPphT4gPPcKZc7aDkweHiKEEO8cla/GjcBK+ckKxiZslIu3C4GCRW3DNfL0o7yW7kMQu9xlZ1kXRXLXtw== + +postcss-selector-not@^8.0.1: + version "8.0.1" + resolved "https://registry.yarnpkg.com/postcss-selector-not/-/postcss-selector-not-8.0.1.tgz#f2df9c6ac9f95e9fe4416ca41a957eda16130172" + integrity sha512-kmVy/5PYVb2UOhy0+LqUYAhKj7DUGDpSWa5LZqlkWJaaAV+dxxsOG3+St0yNLu6vsKD7Dmqx+nWQt0iil89+WA== + dependencies: + postcss-selector-parser "^7.0.0" + +postcss-selector-parser@^6.0.11, postcss-selector-parser@^6.0.16: + version "6.1.2" + resolved "https://registry.yarnpkg.com/postcss-selector-parser/-/postcss-selector-parser-6.1.2.tgz#27ecb41fb0e3b6ba7a1ec84fff347f734c7929de" + integrity sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg== dependencies: cssesc "^3.0.0" util-deprecate "^1.0.2" -postcss-sort-media-queries@^4.2.1: - version "4.3.0" - resolved "https://registry.npmjs.org/postcss-sort-media-queries/-/postcss-sort-media-queries-4.3.0.tgz" - integrity sha512-jAl8gJM2DvuIJiI9sL1CuiHtKM4s5aEIomkU8G3LFvbP+p8i7Sz8VV63uieTgoewGqKbi+hxBTiOKJlB35upCg== +postcss-selector-parser@^7.0.0: + version "7.0.0" + resolved "https://registry.yarnpkg.com/postcss-selector-parser/-/postcss-selector-parser-7.0.0.tgz#41bd8b56f177c093ca49435f65731befe25d6b9c" + integrity sha512-9RbEr1Y7FFfptd/1eEdntyjMwLeghW1bHX9GWjXo19vx4ytPQhANltvVxDggzJl7mnWM+dX28kb6cyS/4iQjlQ== dependencies: - sort-css-media-queries "2.1.0" + cssesc "^3.0.0" + util-deprecate "^1.0.2" -postcss-svgo@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-svgo/-/postcss-svgo-5.1.0.tgz" - integrity sha512-D75KsH1zm5ZrHyxPakAxJWtkyXew5qwS70v56exwvw542d9CRtTo78K0WeFxZB4G7JXKKMbEZtZayTGdIky/eA== +postcss-sort-media-queries@^5.2.0: + version "5.2.0" + resolved "https://registry.yarnpkg.com/postcss-sort-media-queries/-/postcss-sort-media-queries-5.2.0.tgz#4556b3f982ef27d3bac526b99b6c0d3359a6cf97" + integrity sha512-AZ5fDMLD8SldlAYlvi8NIqo0+Z8xnXU2ia0jxmuhxAU+Lqt9K+AlmLNJ/zWEnE9x+Zx3qL3+1K20ATgNOr3fAA== + dependencies: + sort-css-media-queries "2.2.0" + +postcss-svgo@^6.0.3: + version "6.0.3" + resolved "https://registry.yarnpkg.com/postcss-svgo/-/postcss-svgo-6.0.3.tgz#1d6e180d6df1fa8a3b30b729aaa9161e94f04eaa" + integrity sha512-dlrahRmxP22bX6iKEjOM+c8/1p+81asjKT+V5lrgOH944ryx/OHpclnIbGsKVd3uWOXFLYJwCVf0eEkJGvO96g== dependencies: postcss-value-parser "^4.2.0" - svgo "^2.7.0" + svgo "^3.2.0" -postcss-unique-selectors@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/postcss-unique-selectors/-/postcss-unique-selectors-5.1.1.tgz" - integrity sha512-5JiODlELrz8L2HwxfPnhOWZYWDxVHWL83ufOv84NrcgipI7TaeRsatAhK4Tr2/ZiYldpK/wBvw5BD3qfaK96GA== +postcss-unique-selectors@^6.0.4: + version "6.0.4" + resolved "https://registry.yarnpkg.com/postcss-unique-selectors/-/postcss-unique-selectors-6.0.4.tgz#983ab308896b4bf3f2baaf2336e14e52c11a2088" + integrity sha512-K38OCaIrO8+PzpArzkLKB42dSARtC2tmG6PvD4b1o1Q2E9Os8jzfWFfSy/rixsHwohtsDdFtAWGjFVFUdwYaMg== dependencies: - postcss-selector-parser "^6.0.5" + postcss-selector-parser "^6.0.16" postcss-value-parser@^4.1.0, postcss-value-parser@^4.2.0: version "4.2.0" resolved "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz" integrity sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ== -postcss-zindex@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/postcss-zindex/-/postcss-zindex-5.1.0.tgz" - integrity sha512-fgFMf0OtVSBR1va1JNHYgMxYk73yhn/qb4uQDq1DLGYolz8gHCyr/sesEuGUaYs58E3ZJRcpoGuPVoB7Meiq9A== +postcss-zindex@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/postcss-zindex/-/postcss-zindex-6.0.2.tgz#e498304b83a8b165755f53db40e2ea65a99b56e1" + integrity sha512-5BxW9l1evPB/4ZIc+2GobEBoKC+h8gPGCMi+jxsYvd2x0mjq7wazk6DrP71pStqxE9Foxh5TVnonbWpFZzXaYg== -postcss@^8.3.11, postcss@^8.4.14, postcss@^8.4.17, postcss@^8.4.19: - version "8.4.31" - resolved "https://registry.npmjs.org/postcss/-/postcss-8.4.31.tgz" - integrity sha512-PS08Iboia9mts/2ygV3eLpY5ghnUcfLV/EXTOW1E2qYxJKGGBUtNjN76FYHnMs36RmARn41bC0AZmn+rR0OVpQ== +postcss@^8.4.21, postcss@^8.4.24, postcss@^8.4.26, postcss@^8.4.33, postcss@^8.4.38: + version "8.4.49" + resolved "https://registry.yarnpkg.com/postcss/-/postcss-8.4.49.tgz#4ea479048ab059ab3ae61d082190fabfd994fe19" + integrity sha512-OCVPnIObs4N29kxTjzLfUryOkvZEq+pf8jTF0lg8E7uETuWHA+v7j3c/xJmiqpX450191LlmZfUKkXxkTry7nA== dependencies: - nanoid "^3.3.6" - picocolors "^1.0.0" - source-map-js "^1.0.2" - -prepend-http@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/prepend-http/-/prepend-http-2.0.0.tgz" - integrity sha512-ravE6m9Atw9Z/jjttRUZ+clIXogdghyZAuWJ3qEzjT+jI/dL1ifAqhZeC5VHzQp1MSt1+jxKkFNemj/iO7tVUA== + nanoid "^3.3.7" + picocolors "^1.1.1" + source-map-js "^1.2.1" pretty-error@^4.0.0: version "4.0.0" @@ -6095,14 +7812,17 @@ pretty-time@^1.1.0: resolved "https://registry.npmjs.org/pretty-time/-/pretty-time-1.1.0.tgz" integrity sha512-28iF6xPQrP8Oa6uxE6a1biz+lWeTOAPKggvjB8HAs6nVMKZwf5bG++632Dx614hIWgUPkgivRfG+a8uAXGTIbA== -prism-react-renderer@^1.3.5: - version "1.3.5" - resolved "https://registry.npmjs.org/prism-react-renderer/-/prism-react-renderer-1.3.5.tgz" - integrity sha512-IJ+MSwBWKG+SM3b2SUfdrhC+gu01QkV2KmRQgREThBfSQRoufqRfxfHUxpG1WcaFjP+kojcFyO9Qqtpgt3qLCg== +prism-react-renderer@^2.3.0: + version "2.4.1" + resolved "https://registry.yarnpkg.com/prism-react-renderer/-/prism-react-renderer-2.4.1.tgz#ac63b7f78e56c8f2b5e76e823a976d5ede77e35f" + integrity sha512-ey8Ls/+Di31eqzUxC46h8MksNuGx/n0AAC8uKpwFau4RPDYLuE3EXTp8N8G2vX2N7UC/+IXeNUnlWBGGcAG+Ig== + dependencies: + "@types/prismjs" "^1.26.0" + clsx "^2.0.0" -prismjs@^1.28.0: +prismjs@^1.29.0: version "1.29.0" - resolved "https://registry.npmjs.org/prismjs/-/prismjs-1.29.0.tgz" + resolved "https://registry.yarnpkg.com/prismjs/-/prismjs-1.29.0.tgz#f113555a8fa9b57c35e637bba27509dcf802dd12" integrity sha512-Kx/1w86q/epKcmte75LNrEoT+lX8pBpavuAbvJWRXar7Hz8jrtF+e3vY751p0R8H9HdArwaCTNDDzHg/ScJK1Q== process-nextick-args@~2.0.0: @@ -6110,13 +7830,6 @@ process-nextick-args@~2.0.0: resolved "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-2.0.1.tgz" integrity sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag== -promise@^7.1.1: - version "7.3.1" - resolved "https://registry.npmjs.org/promise/-/promise-7.3.1.tgz" - integrity sha512-nolQXZ/4L+bP/UGlkfaIujX9BKxGwmQ9OT4mOt5yvy8iK1h3wqTEJCijzGANTCCl9nWjY41juyAn2K3Q1hLLTg== - dependencies: - asap "~2.0.3" - prompts@^2.4.2: version "2.4.2" resolved "https://registry.npmjs.org/prompts/-/prompts-2.4.2.tgz" @@ -6134,12 +7847,15 @@ prop-types@^15.6.2, prop-types@^15.7.2, prop-types@^15.8.1: object-assign "^4.1.1" react-is "^16.13.1" -property-information@^5.0.0, property-information@^5.3.0: - version "5.6.0" - resolved "https://registry.npmjs.org/property-information/-/property-information-5.6.0.tgz" - integrity sha512-YUHSPk+A30YPv+0Qf8i9Mbfe/C0hdPXk1s1jPVToV8pk8BQtpw10ct89Eo7OWkutrwqvT0eicAxlOg3dOAu8JA== - dependencies: - xtend "^4.0.0" +property-information@^6.0.0: + version "6.5.0" + resolved "https://registry.yarnpkg.com/property-information/-/property-information-6.5.0.tgz#6212fbb52ba757e92ef4fb9d657563b933b7ffec" + integrity sha512-PgTgs/BlvHxOu8QuEN7wi5A0OmXaBcHpmCSTehcs6Uuu9IkDIEo13Hy7n898RHfrQ49vKCoGeWZSaAK01nwVig== + +proto-list@~1.2.1: + version "1.2.4" + resolved "https://registry.yarnpkg.com/proto-list/-/proto-list-1.2.4.tgz#212d5bfe1318306a420f6402b8e26ff39647a849" + integrity sha512-vtK/94akxsTMhe0/cbfpR+syPuszcuwhqVjJq26CuNDgFGj682oRBXOP5MJpv2r7JtE8MsiepGIqvvOTBwn2vA== proxy-addr@~2.0.7: version "2.0.7" @@ -6154,35 +7870,17 @@ pseudomap@^1.0.2: resolved "https://registry.npmjs.org/pseudomap/-/pseudomap-1.0.2.tgz" integrity "sha1-8FKijacOYYkX7wqKw0wa5aaChrM=sha512-b/YwNhb8lk1Zz2+bXXpS/LK9OisiZZ1SNsSLxN1x2OXVEhW2Ckr/7mWE5vrC1ZTiJlD9g19jWszTmJsB+oEpFQ== sha512-b/YwNhb8lk1Zz2+bXXpS/LK9OisiZZ1SNsSLxN1x2OXVEhW2Ckr/7mWE5vrC1ZTiJlD9g19jWszTmJsB+oEpFQ==" -pump@^3.0.0: - version "3.0.0" - resolved "https://registry.npmjs.org/pump/-/pump-3.0.0.tgz" - integrity sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww== - dependencies: - end-of-stream "^1.1.0" - once "^1.3.1" - -punycode@^1.3.2: - version "1.4.1" - resolved "https://registry.npmjs.org/punycode/-/punycode-1.4.1.tgz" - integrity sha512-jmYNElW7yvO7TV33CjSmvSiE2yco3bV2czu/OzDKdMNVZQWfxCblURLhf+47syQRBntjfLdd/H0egrzIG+oaFQ== - punycode@^2.1.0: version "2.3.0" resolved "https://registry.npmjs.org/punycode/-/punycode-2.3.0.tgz" integrity sha512-rRV+zQD8tVFys26lAGR9WUuS4iUAngJScM+ZRSKtvl5tKeZ2t5bvdNFdNHBW9FWR4guGHlgmsZ1G7BSm2wTbuA== -pupa@^2.1.1: - version "2.1.1" - resolved "https://registry.npmjs.org/pupa/-/pupa-2.1.1.tgz" - integrity sha512-l1jNAspIBSFqbT+y+5FosojNpVpF94nlI+wDUpqP9enwOTfHx9f0gh5nB96vl+6yTpsJsypeNrwfzPrKuHB41A== +pupa@^3.1.0: + version "3.1.0" + resolved "https://registry.yarnpkg.com/pupa/-/pupa-3.1.0.tgz#f15610274376bbcc70c9a3aa8b505ea23f41c579" + integrity sha512-FLpr4flz5xZTSJxSeaheeMKN/EDzMdK7b8PTOC6a5PYFKTucWbdqjgqaEyH0shFiSJrVB1+Qqi4Tk19ccU6Aug== dependencies: - escape-goat "^2.0.0" - -pure-color@^1.2.0: - version "1.3.0" - resolved "https://registry.npmjs.org/pure-color/-/pure-color-1.3.0.tgz" - integrity sha512-QFADYnsVoBMw1srW7OVKEYjG+MbIa49s54w1MA1EDY6r2r/sTcKKYqRX1f4GYvnXP7eN/Pe9HFcX+hwzmrXRHA== + escape-goat "^4.0.0" qs@6.13.0: version "6.13.0" @@ -6203,6 +7901,11 @@ queue@6.0.2: dependencies: inherits "~2.0.3" +quick-lru@^5.1.1: + version "5.1.1" + resolved "https://registry.yarnpkg.com/quick-lru/-/quick-lru-5.1.1.tgz#366493e6b3e42a3a6885e2e99d18f80fb7a8c932" + integrity sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA== + randombytes@^2.1.0: version "2.1.0" resolved "https://registry.npmjs.org/randombytes/-/randombytes-2.1.0.tgz" @@ -6238,7 +7941,7 @@ raw-loader@^4.0.2: loader-utils "^2.0.0" schema-utils "^3.0.0" -rc@1.2.8, rc@^1.2.8: +rc@1.2.8: version "1.2.8" resolved "https://registry.npmjs.org/rc/-/rc-1.2.8.tgz" integrity sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw== @@ -6248,16 +7951,6 @@ rc@1.2.8, rc@^1.2.8: minimist "^1.2.0" strip-json-comments "~2.0.1" -react-base16-styling@^0.6.0: - version "0.6.0" - resolved "https://registry.npmjs.org/react-base16-styling/-/react-base16-styling-0.6.0.tgz" - integrity sha512-yvh/7CArceR/jNATXOKDlvTnPKPmGZz7zsenQ3jUwLzHkNUR0CvY3yGYJbWJ/nnxsL8Sgmt5cO3/SILVuPO6TQ== - dependencies: - base16 "^1.0.0" - lodash.curry "^4.0.1" - lodash.flow "^3.3.0" - pure-color "^1.2.0" - react-dev-utils@^12.0.1: version "12.0.1" resolved "https://registry.npmjs.org/react-dev-utils/-/react-dev-utils-12.0.1.tgz" @@ -6288,14 +7981,13 @@ react-dev-utils@^12.0.1: strip-ansi "^6.0.1" text-table "^0.2.0" -react-dom@^17.0.1: - version "17.0.2" - resolved "https://registry.npmjs.org/react-dom/-/react-dom-17.0.2.tgz" - integrity sha512-s4h96KtLDUQlsENhMn1ar8t2bEa+q/YAtj8pPPdIjPDGBDIVNsrD9aXNWqspUe6AzKCIG0C1HZZLqLV7qpOBGA== +react-dom@^18.0.0: + version "18.3.1" + resolved "https://registry.yarnpkg.com/react-dom/-/react-dom-18.3.1.tgz#c2265d79511b57d479b3dd3fdfa51536494c5cb4" + integrity sha512-5m4nQKp+rZRb09LNH59GM4BxTh9251/ylbKIbpe7TpGxfJ+9kv6BLkLBXIjjspbgbnIBNqlI23tRnTWT0snUIw== dependencies: loose-envify "^1.1.0" - object-assign "^4.1.1" - scheduler "^0.20.2" + scheduler "^0.23.2" react-error-overlay@^6.0.11: version "6.0.11" @@ -6323,20 +8015,10 @@ react-is@^16.13.1, react-is@^16.6.0, react-is@^16.7.0: resolved "https://registry.npmjs.org/react-is/-/react-is-16.13.1.tgz" integrity sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ== -react-json-view@^1.21.3: - version "1.21.3" - resolved "https://registry.npmjs.org/react-json-view/-/react-json-view-1.21.3.tgz" - integrity sha512-13p8IREj9/x/Ye4WI/JpjhoIwuzEgUAtgJZNBJckfzJt1qyh24BdTm6UQNGnyTq9dapQdrqvquZTo3dz1X6Cjw== - dependencies: - flux "^4.0.1" - react-base16-styling "^0.6.0" - react-lifecycles-compat "^3.0.4" - react-textarea-autosize "^8.3.2" - -react-lifecycles-compat@^3.0.4: - version "3.0.4" - resolved "https://registry.npmjs.org/react-lifecycles-compat/-/react-lifecycles-compat-3.0.4.tgz" - integrity sha512-fBASbA6LnOU9dOU2eW7aQ8xmYBSXUIWr+UmF9b1efZBazGNO+rcXT/icdKnYm2pTwcRylVUYwW7H1PHfLekVzA== +react-json-view-lite@^1.2.0: + version "1.5.0" + resolved "https://registry.yarnpkg.com/react-json-view-lite/-/react-json-view-lite-1.5.0.tgz#377cc302821717ac79a1b6d099e1891df54c8662" + integrity sha512-nWqA1E4jKPklL2jvHWs6s+7Na0qNgw9HCP6xehdQJeg6nPBTFZgGwyko9Q0oj+jQWKTTVRS30u0toM5wiuL3iw== react-loadable-ssr-addon-v5-slorber@^1.0.1: version "1.0.1" @@ -6345,13 +8027,12 @@ react-loadable-ssr-addon-v5-slorber@^1.0.1: dependencies: "@babel/runtime" "^7.10.3" -"react-loadable@npm:@docusaurus/react-loadable@5.5.2": - version "5.5.2" - resolved "https://registry.npmjs.org/@docusaurus/react-loadable/-/react-loadable-5.5.2.tgz" - integrity sha512-A3dYjdBGuy0IGT+wyLIGIKLRE+sAk1iNk0f1HjNDysO7u8lhL4N3VEm+FAubmJbAztn94F7MxBTPmnixbiyFdQ== +"react-loadable@npm:@docusaurus/react-loadable@6.0.0": + version "6.0.0" + resolved "https://registry.yarnpkg.com/@docusaurus/react-loadable/-/react-loadable-6.0.0.tgz#de6c7f73c96542bd70786b8e522d535d69069dc4" + integrity sha512-YMMxTUQV/QFSnbgrP3tjDzLHRg7vsbMn8e9HAa8o/1iXoiomo48b7sk/kkmWEuWNDPJVlKSJRB6Y2fHqdJk+SQ== dependencies: "@types/react" "*" - prop-types "^15.6.2" react-player@^2.11.0: version "2.11.0" @@ -6371,9 +8052,9 @@ react-router-config@^5.1.1: dependencies: "@babel/runtime" "^7.1.2" -react-router-dom@^5.3.3: +react-router-dom@^5.3.4: version "5.3.4" - resolved "https://registry.npmjs.org/react-router-dom/-/react-router-dom-5.3.4.tgz" + resolved "https://registry.yarnpkg.com/react-router-dom/-/react-router-dom-5.3.4.tgz#2ed62ffd88cae6db134445f4a0c0ae8b91d2e5e6" integrity sha512-m4EqFMHv/Ih4kpcBCONHbkT68KoAeHN4p3lAGoNryfHi0dMy0kCzEZakiKRsvg5wHZ/JLrLW8o8KomWiz/qbYQ== dependencies: "@babel/runtime" "^7.12.13" @@ -6384,7 +8065,7 @@ react-router-dom@^5.3.3: tiny-invariant "^1.0.2" tiny-warning "^1.0.0" -react-router@5.3.4, react-router@^5.3.3: +react-router@5.3.4, react-router@^5.3.4: version "5.3.4" resolved "https://registry.npmjs.org/react-router/-/react-router-5.3.4.tgz" integrity sha512-Ys9K+ppnJah3QuaRiLxk+jDWOR1MekYQrlytiXxC1RyfbdsZkS5pvKAzCCr031xHixZwpnsYNT5xysdFHQaYsA== @@ -6399,22 +8080,12 @@ react-router@5.3.4, react-router@^5.3.3: tiny-invariant "^1.0.2" tiny-warning "^1.0.0" -react-textarea-autosize@^8.3.2: - version "8.4.0" - resolved "https://registry.npmjs.org/react-textarea-autosize/-/react-textarea-autosize-8.4.0.tgz" - integrity sha512-YrTFaEHLgJsi8sJVYHBzYn+mkP3prGkmP2DKb/tm0t7CLJY5t1Rxix8070LAKb0wby7bl/lf2EeHkuMihMZMwQ== - dependencies: - "@babel/runtime" "^7.10.2" - use-composed-ref "^1.3.0" - use-latest "^1.2.1" - -react@^17.0.1: - version "17.0.2" - resolved "https://registry.npmjs.org/react/-/react-17.0.2.tgz" - integrity sha512-gnhPt75i/dq/z3/6q/0asP78D0u592D5L1pd7M8P+dck6Fu/jJeL6iVVK23fptSUZj8Vjf++7wXA8UNclGQcbA== +react@^18.0.0: + version "18.3.1" + resolved "https://registry.yarnpkg.com/react/-/react-18.3.1.tgz#49ab892009c53933625bd16b2533fc754cab2891" + integrity sha512-wS+hAgJShR0KhEvPJArfuPVN1+Hz1t0Y6n5jLrGQbkb4urgPE/0Rve+1kMB1v/oWgHgm4WIcV+i7F2pTVj+2iQ== dependencies: loose-envify "^1.1.0" - object-assign "^4.1.1" readable-stream@^2.0.1: version "2.3.7" @@ -6457,6 +8128,46 @@ rechoir@^0.6.2: dependencies: resolve "^1.1.6" +recma-build-jsx@^1.0.0: + version "1.0.0" + resolved "https://registry.yarnpkg.com/recma-build-jsx/-/recma-build-jsx-1.0.0.tgz#c02f29e047e103d2fab2054954e1761b8ea253c4" + integrity sha512-8GtdyqaBcDfva+GUKDr3nev3VpKAhup1+RvkMvUxURHpW7QyIvk9F5wz7Vzo06CEMSilw6uArgRqhpiUcWp8ew== + dependencies: + "@types/estree" "^1.0.0" + estree-util-build-jsx "^3.0.0" + vfile "^6.0.0" + +recma-jsx@^1.0.0: + version "1.0.0" + resolved "https://registry.yarnpkg.com/recma-jsx/-/recma-jsx-1.0.0.tgz#f7bef02e571a49d6ba3efdfda8e2efab48dbe3aa" + integrity sha512-5vwkv65qWwYxg+Atz95acp8DMu1JDSqdGkA2Of1j6rCreyFUE/gp15fC8MnGEuG1W68UKjM6x6+YTWIh7hZM/Q== + dependencies: + acorn-jsx "^5.0.0" + estree-util-to-js "^2.0.0" + recma-parse "^1.0.0" + recma-stringify "^1.0.0" + unified "^11.0.0" + +recma-parse@^1.0.0: + version "1.0.0" + resolved "https://registry.yarnpkg.com/recma-parse/-/recma-parse-1.0.0.tgz#c351e161bb0ab47d86b92a98a9d891f9b6814b52" + integrity sha512-OYLsIGBB5Y5wjnSnQW6t3Xg7q3fQ7FWbw/vcXtORTnyaSFscOtABg+7Pnz6YZ6c27fG1/aN8CjfwoUEUIdwqWQ== + dependencies: + "@types/estree" "^1.0.0" + esast-util-from-js "^2.0.0" + unified "^11.0.0" + vfile "^6.0.0" + +recma-stringify@^1.0.0: + version "1.0.0" + resolved "https://registry.yarnpkg.com/recma-stringify/-/recma-stringify-1.0.0.tgz#54632030631e0c7546136ff9ef8fde8e7b44f130" + integrity sha512-cjwII1MdIIVloKvC9ErQ+OgAtwHBmcZ0Bg4ciz78FtbT8In39aAYbaA7zvxQ61xVMSPE8WxhLwLbhif4Js2C+g== + dependencies: + "@types/estree" "^1.0.0" + estree-util-to-js "^2.0.0" + unified "^11.0.0" + vfile "^6.0.0" + recursive-readdir@^2.2.2: version "2.2.3" resolved "https://registry.npmjs.org/recursive-readdir/-/recursive-readdir-2.2.3.tgz" @@ -6471,6 +8182,13 @@ regenerate-unicode-properties@^10.1.0: dependencies: regenerate "^1.4.2" +regenerate-unicode-properties@^10.2.0: + version "10.2.0" + resolved "https://registry.yarnpkg.com/regenerate-unicode-properties/-/regenerate-unicode-properties-10.2.0.tgz#626e39df8c372338ea9b8028d1f99dc3fd9c3db0" + integrity sha512-DqHn3DwbmmPVzeKj9woBadqmXxLvQoQIwu7nopMc72ztvxVmVk2SBhSnx67zuye5TP+lJsb/TBQsjLKhnDf3MA== + dependencies: + regenerate "^1.4.2" + regenerate@^1.4.2: version "1.4.2" resolved "https://registry.npmjs.org/regenerate/-/regenerate-1.4.2.tgz" @@ -6481,10 +8199,15 @@ regenerator-runtime@^0.13.11: resolved "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.13.11.tgz" integrity sha512-kY1AZVr2Ra+t+piVaJ4gxaFaReZVH40AKNo7UCX6W+dEwBo/2oZJzqfuN1qLq1oL45o56cPaTXELwrTh8Fpggg== -regenerator-transform@^0.15.1: - version "0.15.1" - resolved "https://registry.npmjs.org/regenerator-transform/-/regenerator-transform-0.15.1.tgz" - integrity sha512-knzmNAcuyxV+gQCufkYcvOqX/qIIfHLv0u5x79kRxuGojfYVky1f15TzZEu2Avte8QGepvUNTnLskf8E6X6Vyg== +regenerator-runtime@^0.14.0: + version "0.14.1" + resolved "https://registry.yarnpkg.com/regenerator-runtime/-/regenerator-runtime-0.14.1.tgz#356ade10263f685dda125100cd862c1db895327f" + integrity sha512-dYnhHh0nJoMfnkZs6GmmhFknAGRrLznOu5nc9ML+EJxGvrx6H7teuevqVqCuPcPK//3eDrrjQhehXVx9cnkGdw== + +regenerator-transform@^0.15.2: + version "0.15.2" + resolved "https://registry.yarnpkg.com/regenerator-transform/-/regenerator-transform-0.15.2.tgz#5bbae58b522098ebdf09bca2f83838929001c7a4" + integrity sha512-hfMp2BoF0qOk3uc5V20ALGDS2ddjQaLrdl7xrGXvAIow7qeWRM2VA2HuCHkUKk9slq3VwEwLNK3DFBqDfPGYtg== dependencies: "@babel/runtime" "^7.8.4" @@ -6500,25 +8223,49 @@ regexpu-core@^5.2.1: unicode-match-property-ecmascript "^2.0.0" unicode-match-property-value-ecmascript "^2.1.0" -registry-auth-token@^4.0.0: - version "4.2.2" - resolved "https://registry.npmjs.org/registry-auth-token/-/registry-auth-token-4.2.2.tgz" - integrity sha512-PC5ZysNb42zpFME6D/XlIgtNGdTl8bBOCw90xQLVMpzuuubJKYDWFAEuUNc+Cn8Z8724tg2SDhDRrkVEsqfDMg== +regexpu-core@^6.2.0: + version "6.2.0" + resolved "https://registry.yarnpkg.com/regexpu-core/-/regexpu-core-6.2.0.tgz#0e5190d79e542bf294955dccabae04d3c7d53826" + integrity sha512-H66BPQMrv+V16t8xtmq+UC0CBpiTBA60V8ibS1QVReIp8T1z8hwFxqcGzm9K6lgsN7sB5edVH8a+ze6Fqm4weA== dependencies: - rc "1.2.8" + regenerate "^1.4.2" + regenerate-unicode-properties "^10.2.0" + regjsgen "^0.8.0" + regjsparser "^0.12.0" + unicode-match-property-ecmascript "^2.0.0" + unicode-match-property-value-ecmascript "^2.1.0" -registry-url@^5.0.0: - version "5.1.0" - resolved "https://registry.npmjs.org/registry-url/-/registry-url-5.1.0.tgz" - integrity sha512-8acYXXTI0AkQv6RAOjE3vOaIXZkT9wo4LOFbBKYQEEnnMNBpKqdUrI6S4NT0KPIo/WVvJ5tE/X5LF/TQUf0ekw== +registry-auth-token@^5.0.1: + version "5.0.3" + resolved "https://registry.yarnpkg.com/registry-auth-token/-/registry-auth-token-5.0.3.tgz#417d758c8164569de8cf5cabff16cc937902dcc6" + integrity sha512-1bpc9IyC+e+CNFRaWyn77tk4xGG4PPUyfakSmA6F6cvUDjrm58dfyJ3II+9yb10EDkHoy1LaPSmHaWLOH3m6HA== + dependencies: + "@pnpm/npm-conf" "^2.1.0" + +registry-url@^6.0.0: + version "6.0.1" + resolved "https://registry.yarnpkg.com/registry-url/-/registry-url-6.0.1.tgz#056d9343680f2f64400032b1e199faa692286c58" + integrity sha512-+crtS5QjFRqFCoQmvGduwYWEBng99ZvmFvF+cUJkGYF1L1BfU8C6Zp9T7f5vPAwyLkUExpvK+ANVZmGU49qi4Q== dependencies: - rc "^1.2.8" + rc "1.2.8" regjsgen@^0.7.1: version "0.7.1" resolved "https://registry.npmjs.org/regjsgen/-/regjsgen-0.7.1.tgz" integrity sha512-RAt+8H2ZEzHeYWxZ3H2z6tF18zyyOnlcdaafLrm21Bguj7uZy6ULibiAFdXEtKQY4Sy7wDTwDiOazasMLc4KPA== +regjsgen@^0.8.0: + version "0.8.0" + resolved "https://registry.yarnpkg.com/regjsgen/-/regjsgen-0.8.0.tgz#df23ff26e0c5b300a6470cad160a9d090c3a37ab" + integrity sha512-RvwtGe3d7LvWiDQXeQw8p5asZUmfU1G/l6WbUXeHta7Y2PEIvBTwH6E2EfmYUK8pxcxEdEmaomqyp0vZZ7C+3Q== + +regjsparser@^0.12.0: + version "0.12.0" + resolved "https://registry.yarnpkg.com/regjsparser/-/regjsparser-0.12.0.tgz#0e846df6c6530586429377de56e0475583b088dc" + integrity sha512-cnE+y8bz4NhMjISKbgeVJtqNbtf5QpjZP+Bslo+UqkIt9QPnX9q095eiRRASJG1/tz6dlNr6Z5NsBiWYokp6EQ== + dependencies: + jsesc "~3.0.2" + regjsparser@^0.9.1: version "0.9.1" resolved "https://registry.npmjs.org/regjsparser/-/regjsparser-0.9.1.tgz" @@ -6526,67 +8273,109 @@ regjsparser@^0.9.1: dependencies: jsesc "~0.5.0" +rehype-raw@^7.0.0: + version "7.0.0" + resolved "https://registry.yarnpkg.com/rehype-raw/-/rehype-raw-7.0.0.tgz#59d7348fd5dbef3807bbaa1d443efd2dd85ecee4" + integrity sha512-/aE8hCfKlQeA8LmyeyQvQF3eBiLRGNlfBJEvWH7ivp9sBqs7TNqBL5X3v157rM4IFETqDnIOO+z5M/biZbo9Ww== + dependencies: + "@types/hast" "^3.0.0" + hast-util-raw "^9.0.0" + vfile "^6.0.0" + +rehype-recma@^1.0.0: + version "1.0.0" + resolved "https://registry.yarnpkg.com/rehype-recma/-/rehype-recma-1.0.0.tgz#d68ef6344d05916bd96e25400c6261775411aa76" + integrity sha512-lqA4rGUf1JmacCNWWZx0Wv1dHqMwxzsDWYMTowuplHF3xH0N/MmrZ/G3BDZnzAkRmxDadujCjaKM2hqYdCBOGw== + dependencies: + "@types/estree" "^1.0.0" + "@types/hast" "^3.0.0" + hast-util-to-estree "^3.0.0" + relateurl@^0.2.7: version "0.2.7" resolved "https://registry.npmjs.org/relateurl/-/relateurl-0.2.7.tgz" integrity sha512-G08Dxvm4iDN3MLM0EsP62EDV9IuhXPR6blNz6Utcp7zyV3tr4HVNINt6MpaRWbxoOHT3Q7YN2P+jaHX8vUbgog== -remark-emoji@^2.2.0: - version "2.2.0" - resolved "https://registry.npmjs.org/remark-emoji/-/remark-emoji-2.2.0.tgz" - integrity sha512-P3cj9s5ggsUvWw5fS2uzCHJMGuXYRb0NnZqYlNecewXt8QBU9n5vW3DUUKOhepS8F9CwdMx9B8a3i7pqFWAI5w== +remark-directive@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/remark-directive/-/remark-directive-3.0.0.tgz#34452d951b37e6207d2e2a4f830dc33442923268" + integrity sha512-l1UyWJ6Eg1VPU7Hm/9tt0zKtReJQNOA4+iDMAxTyZNWnJnFlbS/7zhiel/rogTLQ2vMYwDzSJa4BiVNqGlqIMA== dependencies: - emoticon "^3.2.0" - node-emoji "^1.10.0" - unist-util-visit "^2.0.3" + "@types/mdast" "^4.0.0" + mdast-util-directive "^3.0.0" + micromark-extension-directive "^3.0.0" + unified "^11.0.0" -remark-footnotes@2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/remark-footnotes/-/remark-footnotes-2.0.0.tgz" - integrity sha512-3Clt8ZMH75Ayjp9q4CorNeyjwIxHFcTkaektplKGl2A1jNGEUey8cKL0ZC5vJwfcD5GFGsNLImLG/NGzWIzoMQ== - -remark-mdx@1.6.22: - version "1.6.22" - resolved "https://registry.npmjs.org/remark-mdx/-/remark-mdx-1.6.22.tgz" - integrity sha512-phMHBJgeV76uyFkH4rvzCftLfKCr2RZuF+/gmVcaKrpsihyzmhXjA0BEMDaPTXG5y8qZOKPVo83NAOX01LPnOQ== - dependencies: - "@babel/core" "7.12.9" - "@babel/helper-plugin-utils" "7.10.4" - "@babel/plugin-proposal-object-rest-spread" "7.12.1" - "@babel/plugin-syntax-jsx" "7.12.1" - "@mdx-js/util" "1.6.22" - is-alphabetical "1.0.4" - remark-parse "8.0.3" - unified "9.2.0" - -remark-parse@8.0.3: - version "8.0.3" - resolved "https://registry.npmjs.org/remark-parse/-/remark-parse-8.0.3.tgz" - integrity sha512-E1K9+QLGgggHxCQtLt++uXltxEprmWzNfg+MxpfHsZlrddKzZ/hZyWHDbK3/Ap8HJQqYJRXP+jHczdL6q6i85Q== - dependencies: - ccount "^1.0.0" - collapse-white-space "^1.0.2" - is-alphabetical "^1.0.0" - is-decimal "^1.0.0" - is-whitespace-character "^1.0.0" - is-word-character "^1.0.0" - markdown-escapes "^1.0.0" - parse-entities "^2.0.0" - repeat-string "^1.5.4" - state-toggle "^1.0.0" - trim "0.0.1" - trim-trailing-lines "^1.0.0" - unherit "^1.0.4" - unist-util-remove-position "^2.0.0" - vfile-location "^3.0.0" - xtend "^4.0.1" - -remark-squeeze-paragraphs@4.0.0: +remark-emoji@^4.0.0: + version "4.0.1" + resolved "https://registry.yarnpkg.com/remark-emoji/-/remark-emoji-4.0.1.tgz#671bfda668047689e26b2078c7356540da299f04" + integrity sha512-fHdvsTR1dHkWKev9eNyhTo4EFwbUvJ8ka9SgeWkMPYFX4WoI7ViVBms3PjlQYgw5TLvNQso3GUB/b/8t3yo+dg== + dependencies: + "@types/mdast" "^4.0.2" + emoticon "^4.0.1" + mdast-util-find-and-replace "^3.0.1" + node-emoji "^2.1.0" + unified "^11.0.4" + +remark-frontmatter@^5.0.0: + version "5.0.0" + resolved "https://registry.yarnpkg.com/remark-frontmatter/-/remark-frontmatter-5.0.0.tgz#b68d61552a421ec412c76f4f66c344627dc187a2" + integrity sha512-XTFYvNASMe5iPN0719nPrdItC9aU0ssC4v14mH1BCi1u0n1gAocqcujWUrByftZTbLhRtiKRyjYTSIOcr69UVQ== + dependencies: + "@types/mdast" "^4.0.0" + mdast-util-frontmatter "^2.0.0" + micromark-extension-frontmatter "^2.0.0" + unified "^11.0.0" + +remark-gfm@^4.0.0: version "4.0.0" - resolved "https://registry.npmjs.org/remark-squeeze-paragraphs/-/remark-squeeze-paragraphs-4.0.0.tgz" - integrity sha512-8qRqmL9F4nuLPIgl92XUuxI3pFxize+F1H0e/W3llTk0UsjJaj01+RrirkMw7P21RKe4X6goQhYRSvNWX+70Rw== + resolved "https://registry.yarnpkg.com/remark-gfm/-/remark-gfm-4.0.0.tgz#aea777f0744701aa288b67d28c43565c7e8c35de" + integrity sha512-U92vJgBPkbw4Zfu/IiW2oTZLSL3Zpv+uI7My2eq8JxKgqraFdU8YUGicEJCEgSbeaG+QDFqIcwwfMTOEelPxuA== + dependencies: + "@types/mdast" "^4.0.0" + mdast-util-gfm "^3.0.0" + micromark-extension-gfm "^3.0.0" + remark-parse "^11.0.0" + remark-stringify "^11.0.0" + unified "^11.0.0" + +remark-mdx@^3.0.0: + version "3.1.0" + resolved "https://registry.yarnpkg.com/remark-mdx/-/remark-mdx-3.1.0.tgz#f979be729ecb35318fa48e2135c1169607a78343" + integrity sha512-Ngl/H3YXyBV9RcRNdlYsZujAmhsxwzxpDzpDEhFBVAGthS4GDgnctpDjgFl/ULx5UEDzqtW1cyBSNKqYYrqLBA== + dependencies: + mdast-util-mdx "^3.0.0" + micromark-extension-mdxjs "^3.0.0" + +remark-parse@^11.0.0: + version "11.0.0" + resolved "https://registry.yarnpkg.com/remark-parse/-/remark-parse-11.0.0.tgz#aa60743fcb37ebf6b069204eb4da304e40db45a1" + integrity sha512-FCxlKLNGknS5ba/1lmpYijMUzX2esxW5xQqjWxw2eHFfS2MSdaHVINFmhjo+qN1WhZhNimq0dZATN9pH0IDrpA== + dependencies: + "@types/mdast" "^4.0.0" + mdast-util-from-markdown "^2.0.0" + micromark-util-types "^2.0.0" + unified "^11.0.0" + +remark-rehype@^11.0.0: + version "11.1.1" + resolved "https://registry.yarnpkg.com/remark-rehype/-/remark-rehype-11.1.1.tgz#f864dd2947889a11997c0a2667cd6b38f685bca7" + integrity sha512-g/osARvjkBXb6Wo0XvAeXQohVta8i84ACbenPpoSsxTOQH/Ae0/RGP4WZgnMH5pMLpsj4FG7OHmcIcXxpza8eQ== + dependencies: + "@types/hast" "^3.0.0" + "@types/mdast" "^4.0.0" + mdast-util-to-hast "^13.0.0" + unified "^11.0.0" + vfile "^6.0.0" + +remark-stringify@^11.0.0: + version "11.0.0" + resolved "https://registry.yarnpkg.com/remark-stringify/-/remark-stringify-11.0.0.tgz#4c5b01dd711c269df1aaae11743eb7e2e7636fd3" + integrity sha512-1OSmLd3awB/t8qdoEOMazZkNsfVTeY4fTsgzcQFdXNq8ToTN4ZGwrMnlda4K6smTFKD+GRV6O48i6Z4iKgPPpw== dependencies: - mdast-squeeze-paragraphs "^4.0.0" + "@types/mdast" "^4.0.0" + mdast-util-to-markdown "^2.0.0" + unified "^11.0.0" renderkid@^3.0.0: version "3.0.0" @@ -6599,9 +8388,9 @@ renderkid@^3.0.0: lodash "^4.17.21" strip-ansi "^6.0.1" -repeat-string@^1.5.4: +repeat-string@^1.0.0: version "1.6.1" - resolved "https://registry.npmjs.org/repeat-string/-/repeat-string-1.6.1.tgz" + resolved "https://registry.yarnpkg.com/repeat-string/-/repeat-string-1.6.1.tgz#8dcae470e1c88abc2d600fff4a776286da75e637" integrity sha512-PV0dzCYDNfRi1jCDbJzpW7jNNDRuCOG/jI5ctQcGKt/clZD+YcPS3yIlWuTJMmESC8aevCFmWJy5wjAFgNqN6w== require-from-string@^2.0.2: @@ -6619,6 +8408,11 @@ requires-port@^1.0.0: resolved "https://registry.npmjs.org/requires-port/-/requires-port-1.0.0.tgz" integrity sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ== +resolve-alpn@^1.2.0: + version "1.2.1" + resolved "https://registry.yarnpkg.com/resolve-alpn/-/resolve-alpn-1.2.1.tgz#b7adbdac3546aaaec20b45e7d8265927072726f9" + integrity sha512-0a1F4l73/ZFZOakJnQ3FvkJ2+gSTQWz/r2KE5OdDY0TxPm5h4GkqkWWfM47T7HsbnOtcJVEF4epCVy6u7Q3K+g== + resolve-from@^4.0.0: version "4.0.0" resolved "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz" @@ -6629,7 +8423,7 @@ resolve-pathname@^3.0.0: resolved "https://registry.npmjs.org/resolve-pathname/-/resolve-pathname-3.0.0.tgz" integrity sha512-C7rARubxI8bXFNB/hqcp/4iUeIXJhJZvFPFPiSPRnhU5UPxzMFIl+2E6yY6c4k9giDJAhtV+enfA+G89N6Csng== -resolve@^1.1.6, resolve@^1.14.2, resolve@^1.3.2: +resolve@^1.1.6, resolve@^1.14.2: version "1.22.1" resolved "https://registry.npmjs.org/resolve/-/resolve-1.22.1.tgz" integrity sha512-nBpuuYuY5jFsli/JIs1oldw6fOQCBioohqWZg/2hiaOybXOft4lonv85uDOKXdf8rhyK159cxU5cDcK/NKk8zw== @@ -6638,12 +8432,12 @@ resolve@^1.1.6, resolve@^1.14.2, resolve@^1.3.2: path-parse "^1.0.7" supports-preserve-symlinks-flag "^1.0.0" -responselike@^1.0.2: - version "1.0.2" - resolved "https://registry.npmjs.org/responselike/-/responselike-1.0.2.tgz" - integrity sha512-/Fpe5guzJk1gPqdJLJR5u7eG/gNY4nImjbRDaVWVMRhne55TCmj2i9Q+54PBRfatRC8v/rIiv9BN0pMd9OV5EQ== +responselike@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/responselike/-/responselike-3.0.0.tgz#20decb6c298aff0dbee1c355ca95461d42823626" + integrity sha512-40yHxbNcl2+rzXvZuVkrYohathsSJlMTXKryG5y8uciHv1+xDLHQpgjG64JUO9nrEq2jGLH6IZ8BcZyw3wrweg== dependencies: - lowercase-keys "^1.0.0" + lowercase-keys "^3.0.0" retry@^0.13.1: version "0.13.1" @@ -6667,14 +8461,14 @@ rtl-detect@^1.0.4: resolved "https://registry.npmjs.org/rtl-detect/-/rtl-detect-1.0.4.tgz" integrity sha512-EBR4I2VDSSYr7PkBmFy04uhycIpDKp+21p/jARYXlCSjQksTBQcJ0HFUPOO79EPPH5JS6VAhiIQbycf0O3JAxQ== -rtlcss@^3.5.0: - version "3.5.0" - resolved "https://registry.npmjs.org/rtlcss/-/rtlcss-3.5.0.tgz" - integrity sha512-wzgMaMFHQTnyi9YOwsx9LjOxYXJPzS8sYnFaKm6R5ysvTkwzHiB0vxnbHwchHQT65PTdBjDG21/kQBWI7q9O7A== +rtlcss@^4.1.0: + version "4.3.0" + resolved "https://registry.yarnpkg.com/rtlcss/-/rtlcss-4.3.0.tgz#f8efd4d5b64f640ec4af8fa25b65bacd9e07cc97" + integrity sha512-FI+pHEn7Wc4NqKXMXFM+VAYKEj/mRIcW4h24YVwVtyjI+EqGrLc2Hx/Ny0lrZ21cBWU2goLy36eqMcNj3AQJig== dependencies: - find-up "^5.0.0" + escalade "^3.1.1" picocolors "^1.0.0" - postcss "^8.3.11" + postcss "^8.4.21" strip-json-comments "^3.1.1" run-parallel@^1.1.9: @@ -6684,13 +8478,6 @@ run-parallel@^1.1.9: dependencies: queue-microtask "^1.2.2" -rxjs@^7.5.4: - version "7.8.0" - resolved "https://registry.npmjs.org/rxjs/-/rxjs-7.8.0.tgz" - integrity sha512-F2+gxDshqmIub1KdvZkaEfGDwLNpPvk9Fs6LD/MyQxNgMds/WH9OdDDXOmxUZpME+iSK3rQCctkL0DYyytUqMg== - dependencies: - tslib "^2.1.0" - safe-buffer@5.1.2, safe-buffer@~5.1.0, safe-buffer@~5.1.1: version "5.1.2" resolved "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz" @@ -6711,13 +8498,12 @@ sax@^1.2.4: resolved "https://registry.npmjs.org/sax/-/sax-1.2.4.tgz" integrity sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw== -scheduler@^0.20.2: - version "0.20.2" - resolved "https://registry.npmjs.org/scheduler/-/scheduler-0.20.2.tgz" - integrity sha512-2eWfGgAqqWFGqtdMmcL5zCMK1U8KlXv8SQFGglL3CEtd0aDVDWgeF/YoCmvln55m5zSk3J/20hTaSBeSObsQDQ== +scheduler@^0.23.2: + version "0.23.2" + resolved "https://registry.yarnpkg.com/scheduler/-/scheduler-0.23.2.tgz#414ba64a3b282892e944cf2108ecc078d115cdc3" + integrity sha512-UOShsPwz7NrMUqhR6t0hWjFduvOzbtv7toDH1/hIrfRNIDBnnBWd0CwJTGvTpngVlmwGCdP9/Zl/tVrDqcuYzQ== dependencies: loose-envify "^1.1.0" - object-assign "^4.1.1" schema-utils@2.7.0: version "2.7.0" @@ -6728,15 +8514,6 @@ schema-utils@2.7.0: ajv "^6.12.2" ajv-keywords "^3.4.1" -schema-utils@^2.6.5: - version "2.7.1" - resolved "https://registry.npmjs.org/schema-utils/-/schema-utils-2.7.1.tgz" - integrity sha512-SHiNtMOUGWBQJwzISiVYKu82GiV4QYGePp3odlY1tuKO7gPtphAT5R/py0fA6xtbgLL/RvtJZnU9b8s0F1q0Xg== - dependencies: - "@types/json-schema" "^7.0.5" - ajv "^6.12.4" - ajv-keywords "^3.5.2" - schema-utils@^3.0.0, schema-utils@^3.1.1, schema-utils@^3.2.0: version "3.3.0" resolved "https://registry.npmjs.org/schema-utils/-/schema-utils-3.3.0.tgz" @@ -6756,6 +8533,16 @@ schema-utils@^4.0.0: ajv-formats "^2.1.1" ajv-keywords "^5.0.0" +schema-utils@^4.0.1, schema-utils@^4.3.0: + version "4.3.0" + resolved "https://registry.yarnpkg.com/schema-utils/-/schema-utils-4.3.0.tgz#3b669f04f71ff2dfb5aba7ce2d5a9d79b35622c0" + integrity sha512-Gf9qqc58SpCA/xdziiHz35F4GNIWYWZrEshUc/G/r5BnLph6xpKuLeoJoQuj5WfBIx/eQLf+hmVPYHaxJu7V2g== + dependencies: + "@types/json-schema" "^7.0.9" + ajv "^8.9.0" + ajv-formats "^2.1.1" + ajv-keywords "^5.1.0" + section-matter@^1.0.0: version "1.0.0" resolved "https://registry.npmjs.org/section-matter/-/section-matter-1.0.0.tgz" @@ -6776,30 +8563,30 @@ selfsigned@^2.1.1: dependencies: node-forge "^1" -semver-diff@^3.1.1: - version "3.1.1" - resolved "https://registry.npmjs.org/semver-diff/-/semver-diff-3.1.1.tgz" - integrity sha512-GX0Ix/CJcHyB8c4ykpHGIAvLyOwOobtM/8d+TQkAd81/bEjgPHrfba41Vpesr7jX/t8Uh+R3EX9eAS5be+jQYg== +semver-diff@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/semver-diff/-/semver-diff-4.0.0.tgz#3afcf5ed6d62259f5c72d0d5d50dffbdc9680df5" + integrity sha512-0Ju4+6A8iOnpL/Thra7dZsSlOHYAHIeMxfhWQRI1/VLcT3WDBZKKtQt/QkBOsiIN9ZpuvHE6cGZ0x4glCMmfiA== dependencies: - semver "^6.3.0" - -semver@^5.4.1: - version "5.7.2" - resolved "https://registry.npmjs.org/semver/-/semver-5.7.2.tgz" - integrity sha512-cBznnQ9KjJqU67B52RMC65CMarK2600WFnbkcaiwWq3xy/5haFJlshgnpjovMVJ+Hff49d8GEn0b87C5pDQ10g== + semver "^7.3.5" -semver@^6.0.0, semver@^6.1.1, semver@^6.1.2, semver@^6.2.0, semver@^6.3.0: +semver@^6.0.0, semver@^6.3.1: version "6.3.1" - resolved "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz" + resolved "https://registry.yarnpkg.com/semver/-/semver-6.3.1.tgz#556d2ef8689146e46dcea4bfdd095f3434dffcb4" integrity sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA== -semver@^7.3.2, semver@^7.3.4, semver@^7.3.5, semver@^7.3.7, semver@^7.3.8: +semver@^7.3.2, semver@^7.3.5, semver@^7.3.7: version "7.5.4" resolved "https://registry.npmjs.org/semver/-/semver-7.5.4.tgz" integrity sha512-1bCSESV6Pv+i21Hvpxp3Dx+pSD8lIPt8uVjRrxAUt/nbswYc+tK6Y2btiULjd4+fnq15PX+nqQDC7Oft7WkwcA== dependencies: lru-cache "^6.0.0" +semver@^7.5.4: + version "7.6.3" + resolved "https://registry.yarnpkg.com/semver/-/semver-7.6.3.tgz#980f7b5550bc175fb4dc09403085627f9eb33143" + integrity sha512-oVekP1cKtI+CTDvHWYFUcMtsK/00wmAEfyqKfNdARm8u1wNVhSgaX7A8d4UuIlUI5e84iEwOhs7ZPYRmzU9U6A== + send@0.19.0: version "0.19.0" resolved "https://registry.npmjs.org/send/-/send-0.19.0.tgz" @@ -6826,18 +8613,24 @@ serialize-javascript@^6.0.0, serialize-javascript@^6.0.1: dependencies: randombytes "^2.1.0" -serve-handler@^6.1.3: - version "6.1.5" - resolved "https://registry.npmjs.org/serve-handler/-/serve-handler-6.1.5.tgz" - integrity sha512-ijPFle6Hwe8zfmBxJdE+5fta53fdIY0lHISJvuikXB3VYFafRjMRpOffSPvCYsbKyBA7pvy9oYr/BT1O3EArlg== +serialize-javascript@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/serialize-javascript/-/serialize-javascript-6.0.2.tgz#defa1e055c83bf6d59ea805d8da862254eb6a6c2" + integrity sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g== + dependencies: + randombytes "^2.1.0" + +serve-handler@^6.1.6: + version "6.1.6" + resolved "https://registry.yarnpkg.com/serve-handler/-/serve-handler-6.1.6.tgz#50803c1d3e947cd4a341d617f8209b22bd76cfa1" + integrity sha512-x5RL9Y2p5+Sh3D38Fh9i/iQ5ZK+e4xuXRd/pGbM4D13tgo/MGwbttUk8emytcr1YYzBYs+apnUngBDFYfpjPuQ== dependencies: bytes "3.0.0" content-disposition "0.5.2" - fast-url-parser "1.1.3" mime-types "2.1.18" minimatch "3.1.2" path-is-inside "1.0.2" - path-to-regexp "2.2.1" + path-to-regexp "3.3.0" range-parser "1.2.0" serve-index@^1.9.1: @@ -6875,11 +8668,6 @@ set-function-length@^1.2.1: gopd "^1.0.1" has-property-descriptors "^1.0.2" -setimmediate@^1.0.5: - version "1.0.5" - resolved "https://registry.npmjs.org/setimmediate/-/setimmediate-1.0.5.tgz" - integrity sha512-MATJdZp8sLqDl/68LfQmbP8zKPLQNV6BIZoIgrscFDQ+RsvK/BxeDQOgyxKKoh0y/8h3BqVFnCqQ/gd+reiIXA== - setprototypeof@1.1.0: version "1.1.0" resolved "https://registry.npmjs.org/setprototypeof/-/setprototypeof-1.1.0.tgz" @@ -6931,6 +8719,11 @@ shell-quote@^1.7.3: resolved "https://registry.npmjs.org/shell-quote/-/shell-quote-1.8.0.tgz" integrity sha512-QHsz8GgQIGKlRi24yFc6a6lN69Idnx634w49ay6+jA5yFh7a1UY+4Rp6HPx/L/1zcEDPEij8cIsiqR6bQsE5VQ== +shell-quote@^1.8.1: + version "1.8.2" + resolved "https://registry.yarnpkg.com/shell-quote/-/shell-quote-1.8.2.tgz#d2d83e057959d53ec261311e9e9b8f51dcb2934a" + integrity sha512-AzqKpGKjrj7EM6rKVQEPpB288oCfnrEIuyoT9cyF4nmGa7V8Zk6f7RRqYisX8X9m+Q7bd632aZW4ky7EhbQztA== + shelljs@^0.8.5: version "0.8.5" resolved "https://registry.npmjs.org/shelljs/-/shelljs-0.8.5.tgz" @@ -6955,14 +8748,14 @@ signal-exit@^3.0.2, signal-exit@^3.0.3: resolved "https://registry.npmjs.org/signal-exit/-/signal-exit-3.0.7.tgz" integrity sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ== -sirv@^1.0.7: - version "1.0.19" - resolved "https://registry.npmjs.org/sirv/-/sirv-1.0.19.tgz" - integrity sha512-JuLThK3TnZG1TAKDwNIqNq6QA2afLOCcm+iE8D1Kj3GA40pSPsxQjjJl0J8X3tsR7T+CP1GavpzLwYkgVLWrZQ== +sirv@^2.0.3: + version "2.0.4" + resolved "https://registry.yarnpkg.com/sirv/-/sirv-2.0.4.tgz#5dd9a725c578e34e449f332703eb2a74e46a29b0" + integrity sha512-94Bdh3cC2PKrbgSOUqTiGPWVZeSiXfKOVZNJniWoqrWrRkB1CJzBU3NEbiTsPcYy1lDsANA/THzS+9WBiy5nfQ== dependencies: - "@polka/url" "^1.0.0-next.20" - mrmime "^1.0.0" - totalist "^1.0.0" + "@polka/url" "^1.0.0-next.24" + mrmime "^2.0.0" + totalist "^3.0.0" sisteransi@^1.0.5: version "1.0.5" @@ -6979,6 +8772,13 @@ sitemap@^7.1.1: arg "^5.0.0" sax "^1.2.4" +skin-tone@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/skin-tone/-/skin-tone-2.0.0.tgz#4e3933ab45c0d4f4f781745d64b9f4c208e41237" + integrity sha512-kUMbT1oBJCpgrnKoSr0o6wPtvRWT9W9UKvGLwfJYO2WuahZRHOpEyL1ckyMGgMWh0UdpmaoFqKKD29WTomNEGA== + dependencies: + unicode-emoji-modifier-base "^1.0.0" + slash@^3.0.0: version "3.0.0" resolved "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz" @@ -6989,6 +8789,14 @@ slash@^4.0.0: resolved "https://registry.npmjs.org/slash/-/slash-4.0.0.tgz" integrity sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew== +snake-case@^3.0.4: + version "3.0.4" + resolved "https://registry.yarnpkg.com/snake-case/-/snake-case-3.0.4.tgz#4f2bbd568e9935abdfd593f34c691dadb49c452c" + integrity sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg== + dependencies: + dot-case "^3.0.4" + tslib "^2.0.3" + sockjs@^0.3.24: version "0.3.24" resolved "https://registry.npmjs.org/sockjs/-/sockjs-0.3.24.tgz" @@ -6998,20 +8806,20 @@ sockjs@^0.3.24: uuid "^8.3.2" websocket-driver "^0.7.4" -sort-css-media-queries@2.1.0: - version "2.1.0" - resolved "https://registry.npmjs.org/sort-css-media-queries/-/sort-css-media-queries-2.1.0.tgz" - integrity sha512-IeWvo8NkNiY2vVYdPa27MCQiR0MN0M80johAYFVxWWXQ44KU84WNxjslwBHmc/7ZL2ccwkM7/e6S5aiKZXm7jA== +sort-css-media-queries@2.2.0: + version "2.2.0" + resolved "https://registry.yarnpkg.com/sort-css-media-queries/-/sort-css-media-queries-2.2.0.tgz#aa33cf4a08e0225059448b6c40eddbf9f1c8334c" + integrity sha512-0xtkGhWCC9MGt/EzgnvbbbKhqWjl1+/rncmhTh5qCpbYguXh6S/qwePfv/JQ8jePXXmqingylxoC49pCkSPIbA== sort-object-keys@^1.1.3: version "1.1.3" resolved "https://registry.npmjs.org/sort-object-keys/-/sort-object-keys-1.1.3.tgz" integrity sha512-855pvK+VkU7PaKYPc+Jjnmt4EzejQHyhhF33q31qG8x7maDzkeFhAAThdCYay11CISO+qAMwjOBP+fPZe0IPyg== -source-map-js@^1.0.2: - version "1.0.2" - resolved "https://registry.npmjs.org/source-map-js/-/source-map-js-1.0.2.tgz" - integrity sha512-R0XvVJ9WusLiqTCEiGCmICCMplcCkIwwR11mOSD9CR5u+IXYdiseeEuXCVAjS54zqwkLcPNnmU4OeJ6tUrWhDw== +source-map-js@^1.0.1, source-map-js@^1.2.1: + version "1.2.1" + resolved "https://registry.yarnpkg.com/source-map-js/-/source-map-js-1.2.1.tgz#1ce5650fddd87abc099eda37dcff024c2667ae46" + integrity sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA== source-map-support@~0.5.20: version "0.5.21" @@ -7021,20 +8829,20 @@ source-map-support@~0.5.20: buffer-from "^1.0.0" source-map "^0.6.0" -source-map@^0.5.0: - version "0.5.7" - resolved "https://registry.npmjs.org/source-map/-/source-map-0.5.7.tgz" - integrity sha512-LbrmJOMUSdEVxIKvdcJzQC+nQhe8FUZQTXQy6+I75skNgn3OoQ0DZA8YnFa7gp8tqtL3KPf1kmo0R5DoApeSGQ== - -source-map@^0.6.0, source-map@^0.6.1, source-map@~0.6.0: +source-map@^0.6.0, source-map@~0.6.0: version "0.6.1" resolved "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz" integrity sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g== -space-separated-tokens@^1.0.0: - version "1.1.5" - resolved "https://registry.npmjs.org/space-separated-tokens/-/space-separated-tokens-1.1.5.tgz" - integrity sha512-q/JSVd1Lptzhf5bkYm4ob4iWPjx0KiRe3sRFBNrVqbJkFaBm5vbbowy1mymoPNLRa52+oadOhJ+K49wsSeSjTA== +source-map@^0.7.0: + version "0.7.4" + resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.7.4.tgz#a9bbe705c9d8846f4e08ff6765acf0f1b0898656" + integrity sha512-l3BikUxvPOcn5E74dZiq5BGsTb5yEwhaTSzccU6t4sDOH8NWJCstKO5QT2CvtFoK6F0saL7p9xHAqHOlCPJygA== + +space-separated-tokens@^2.0.0: + version "2.0.2" + resolved "https://registry.yarnpkg.com/space-separated-tokens/-/space-separated-tokens-2.0.2.tgz#1ecd9d2350a3844572c3f4a312bceb018348859f" + integrity sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q== spdy-transport@^3.0.0: version "3.0.0" @@ -7064,15 +8872,10 @@ sprintf-js@~1.0.2: resolved "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz" integrity sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g== -stable@^0.1.8: - version "0.1.8" - resolved "https://registry.npmjs.org/stable/-/stable-0.1.8.tgz" - integrity sha512-ji9qxRnOVfcuLDySj9qzhGSEFVobyt1kIOSkj1qZzYLzq7Tos/oUUWvotUPQLlrsidqsK6tBH89Bc9kL5zHA6w== - -state-toggle@^1.0.0: - version "1.0.3" - resolved "https://registry.npmjs.org/state-toggle/-/state-toggle-1.0.3.tgz" - integrity sha512-d/5Z4/2iiCnHw6Xzghyhb+GcmF89bxwgXG60wjIiZaxnymbyOmI8Hk4VqHXiVVp6u2ysaskFfXg3ekCj4WNftQ== +srcset@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/srcset/-/srcset-4.0.0.tgz#336816b665b14cd013ba545b6fe62357f86e65f4" + integrity sha512-wvLeHgcVHKO8Sc/H/5lkGreJQVeYMm9rlmt8PuR1xE31rIuXhuzznUUqAt8MqLhB3MqJdFzlNAfpcWnxiFUcPw== statuses@2.0.1: version "2.0.1" @@ -7084,12 +8887,12 @@ statuses@2.0.1: resolved "https://registry.npmjs.org/statuses/-/statuses-1.5.0.tgz" integrity sha512-OpZ3zP+jT1PI7I8nemJX4AKmAX070ZkYPVWV/AaKTJl+tXCTGyVdC1a4SL8RUQYEwk/f34ZX8UTykN68FwrqAA== -std-env@^3.0.1: - version "3.3.1" - resolved "https://registry.npmjs.org/std-env/-/std-env-3.3.1.tgz" - integrity sha512-3H20QlwQsSm2OvAxWIYhs+j01MzzqwMwGiiO1NQaJYZgJZFPuAbf95/DiKRBSTYIJ2FeGUc+B/6mPGcWP9dO3Q== +std-env@^3.7.0: + version "3.8.0" + resolved "https://registry.yarnpkg.com/std-env/-/std-env-3.8.0.tgz#b56ffc1baf1a29dcc80a3bdf11d7fca7c315e7d5" + integrity sha512-Bc3YwwCB+OzldMxOXJIIvC6cPRWr/LxOp48CdQTOkPyk/t4JWWJbrilwBd7RJzKV8QW7tJkcgAmeuLLJugl5/w== -string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.2: +string-width@^4.1.0, string-width@^4.2.0: version "4.2.3" resolved "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz" integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g== @@ -7098,7 +8901,7 @@ string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2 is-fullwidth-code-point "^3.0.0" strip-ansi "^6.0.1" -string-width@^5.0.1: +string-width@^5.0.1, string-width@^5.1.2: version "5.1.2" resolved "https://registry.npmjs.org/string-width/-/string-width-5.1.2.tgz" integrity sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA== @@ -7121,6 +8924,14 @@ string_decoder@~1.1.1: dependencies: safe-buffer "~5.1.0" +stringify-entities@^4.0.0: + version "4.0.4" + resolved "https://registry.yarnpkg.com/stringify-entities/-/stringify-entities-4.0.4.tgz#b3b79ef5f277cc4ac73caeb0236c5ba939b3a4f3" + integrity sha512-IwfBptatlO+QCJUo19AqvrPNqlVMpW9YEL2LIVY+Rpv2qsjCGxaDLNRgeGsQWJhfItebuJhsGSLjaBbNSQ+ieg== + dependencies: + character-entities-html4 "^2.0.0" + character-entities-legacy "^3.0.0" + stringify-object@^3.3.0: version "3.3.0" resolved "https://registry.npmjs.org/stringify-object/-/stringify-object-3.3.0.tgz" @@ -7164,20 +8975,27 @@ strip-json-comments@~2.0.1: resolved "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-2.0.1.tgz" integrity sha512-4gB8na07fecVVkOI6Rs4e7T6NOTki5EmL7TUduTs6bu3EdnSycntVJ4re8kgZA+wx9IueI2Y11bfbgwtzuE0KQ== -style-to-object@0.3.0, style-to-object@^0.3.0: - version "0.3.0" - resolved "https://registry.npmjs.org/style-to-object/-/style-to-object-0.3.0.tgz" - integrity sha512-CzFnRRXhzWIdItT3OmF8SQfWyahHhjq3HwcMNCNLn+N7klOOqPjMeG/4JSu77D7ypZdGvSzvkrbyeTMizz2VrA== +style-to-object@^0.4.0: + version "0.4.4" + resolved "https://registry.yarnpkg.com/style-to-object/-/style-to-object-0.4.4.tgz#266e3dfd56391a7eefb7770423612d043c3f33ec" + integrity sha512-HYNoHZa2GorYNyqiCaBgsxvcJIn7OHq6inEga+E6Ke3m5JkoqpQbnFssk4jwe+K7AhGa2fcha4wSOf1Kn01dMg== dependencies: inline-style-parser "0.1.1" -stylehacks@^5.1.1: - version "5.1.1" - resolved "https://registry.npmjs.org/stylehacks/-/stylehacks-5.1.1.tgz" - integrity sha512-sBpcd5Hx7G6seo7b1LkpttvTz7ikD0LlH5RmdcBNb6fFR0Fl7LQwHDFr300q4cwUqi+IYrFGmsIHieMBfnN/Bw== +style-to-object@^1.0.0: + version "1.0.8" + resolved "https://registry.yarnpkg.com/style-to-object/-/style-to-object-1.0.8.tgz#67a29bca47eaa587db18118d68f9d95955e81292" + integrity sha512-xT47I/Eo0rwJmaXC4oilDGDWLohVhR6o/xAQcPQN8q6QBuZVL8qMYL85kLmST5cPjAorwvqIA4qXTRQoYHaL6g== + dependencies: + inline-style-parser "0.2.4" + +stylehacks@^6.1.1: + version "6.1.1" + resolved "https://registry.yarnpkg.com/stylehacks/-/stylehacks-6.1.1.tgz#543f91c10d17d00a440430362d419f79c25545a6" + integrity sha512-gSTTEQ670cJNoaeIp9KX6lZmm8LJ3jPB5yJmX8Zq/wQxOsAFXV3qjWzHas3YYk1qesuVIyYWWUpZ0vSE/dTSGg== dependencies: - browserslist "^4.21.4" - postcss-selector-parser "^6.0.4" + browserslist "^4.23.0" + postcss-selector-parser "^6.0.16" supports-color@^5.3.0: version "5.5.0" @@ -7210,18 +9028,18 @@ svg-parser@^2.0.4: resolved "https://registry.npmjs.org/svg-parser/-/svg-parser-2.0.4.tgz" integrity sha512-e4hG1hRwoOdRb37cIMSgzNsxyzKfayW6VOflrwvR+/bzrkyxY/31WkbgnQpgtrNp1SdpJvpUAGTa/ZoiPNDuRQ== -svgo@^2.7.0, svgo@^2.8.0: - version "2.8.0" - resolved "https://registry.npmjs.org/svgo/-/svgo-2.8.0.tgz" - integrity sha512-+N/Q9kV1+F+UeWYoSiULYo4xYSDQlTgb+ayMobAXPwMnLvop7oxKMo9OzIrX5x3eS4L4f2UHhc9axXwY8DpChg== +svgo@^3.0.2, svgo@^3.2.0: + version "3.3.2" + resolved "https://registry.yarnpkg.com/svgo/-/svgo-3.3.2.tgz#ad58002652dffbb5986fc9716afe52d869ecbda8" + integrity sha512-OoohrmuUlBs8B8o6MB2Aevn+pRIH9zDALSR+6hhqVfa6fRwG/Qw9VUMSMW9VNg2CFc/MTIfabtdOVl9ODIJjpw== dependencies: "@trysound/sax" "0.2.0" commander "^7.2.0" - css-select "^4.1.3" - css-tree "^1.1.3" - csso "^4.2.0" + css-select "^5.1.0" + css-tree "^2.3.1" + css-what "^6.1.0" + csso "^5.0.5" picocolors "^1.0.0" - stable "^0.1.8" synp@^1.9.10: version "1.9.10" @@ -7243,12 +9061,12 @@ tapable@^1.0.0: resolved "https://registry.npmjs.org/tapable/-/tapable-1.1.3.tgz" integrity sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA== -tapable@^2.0.0, tapable@^2.1.1, tapable@^2.2.0: +tapable@^2.0.0, tapable@^2.1.1, tapable@^2.2.0, tapable@^2.2.1: version "2.2.1" resolved "https://registry.npmjs.org/tapable/-/tapable-2.2.1.tgz" integrity sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ== -terser-webpack-plugin@^5.3.10, terser-webpack-plugin@^5.3.3: +terser-webpack-plugin@^5.3.10: version "5.3.10" resolved "https://registry.npmjs.org/terser-webpack-plugin/-/terser-webpack-plugin-5.3.10.tgz" integrity sha512-BKFPWlPDndPs+NGGCr1U59t0XScL5317Y0UReNrHaw9/FwhPENlq6bfgs+4yPfyP51vqC1bQ4rp1EfXW5ZSH9w== @@ -7259,6 +9077,17 @@ terser-webpack-plugin@^5.3.10, terser-webpack-plugin@^5.3.3: serialize-javascript "^6.0.1" terser "^5.26.0" +terser-webpack-plugin@^5.3.9: + version "5.3.11" + resolved "https://registry.yarnpkg.com/terser-webpack-plugin/-/terser-webpack-plugin-5.3.11.tgz#93c21f44ca86634257cac176f884f942b7ba3832" + integrity sha512-RVCsMfuD0+cTt3EwX8hSl2Ks56EbFHWmhluwcqoPKtBnfjiT6olaq7PRIRfhyU8nnC2MrnDrBLfrD/RGE+cVXQ== + dependencies: + "@jridgewell/trace-mapping" "^0.3.25" + jest-worker "^27.4.5" + schema-utils "^4.3.0" + serialize-javascript "^6.0.2" + terser "^5.31.1" + terser@^5.10.0, terser@^5.26.0: version "5.36.0" resolved "https://registry.npmjs.org/terser/-/terser-5.36.0.tgz" @@ -7269,6 +9098,16 @@ terser@^5.10.0, terser@^5.26.0: commander "^2.20.0" source-map-support "~0.5.20" +terser@^5.15.1, terser@^5.31.1: + version "5.37.0" + resolved "https://registry.yarnpkg.com/terser/-/terser-5.37.0.tgz#38aa66d1cfc43d0638fab54e43ff8a4f72a21ba3" + integrity sha512-B8wRRkmre4ERucLM/uXx4MOV5cbnOlVAqUst+1+iLKPI0dOgFO28f84ptoQt9HEI537PMzfYa/d+GEPKTRXmYA== + dependencies: + "@jridgewell/source-map" "^0.3.3" + acorn "^8.8.2" + commander "^2.20.0" + source-map-support "~0.5.20" + text-table@^0.2.0: version "0.2.0" resolved "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz" @@ -7294,11 +9133,6 @@ to-fast-properties@^2.0.0: resolved "https://registry.npmjs.org/to-fast-properties/-/to-fast-properties-2.0.0.tgz" integrity sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog== -to-readable-stream@^1.0.0: - version "1.0.0" - resolved "https://registry.npmjs.org/to-readable-stream/-/to-readable-stream-1.0.0.tgz" - integrity sha512-Iq25XBt6zD5npPhlLVXGFN3/gyR2/qODcKNNyTMd4vbm39HUaOiAM4PMq0eMVC/Tkxz+Zjdsc55g9yyz+Yq00Q== - to-regex-range@^5.0.1: version "5.0.1" resolved "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz" @@ -7311,47 +9145,47 @@ toidentifier@1.0.1: resolved "https://registry.npmjs.org/toidentifier/-/toidentifier-1.0.1.tgz" integrity sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA== -totalist@^1.0.0: - version "1.1.0" - resolved "https://registry.npmjs.org/totalist/-/totalist-1.1.0.tgz" - integrity sha512-gduQwd1rOdDMGxFG1gEvhV88Oirdo2p+KjoYFU7k2g+i7n6AFFbDQ5kMPUsW0pNbfQsB/cwXvT1i4Bue0s9g5g== - -tr46@~0.0.3: - version "0.0.3" - resolved "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz" - integrity sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw== - -trim-trailing-lines@^1.0.0: - version "1.1.4" - resolved "https://registry.npmjs.org/trim-trailing-lines/-/trim-trailing-lines-1.1.4.tgz" - integrity sha512-rjUWSqnfTNrjbB9NQWfPMH/xRK1deHeGsHoVfpxJ++XeYXE0d6B1En37AHfw3jtfTU7dzMzZL2jjpe8Qb5gLIQ== +totalist@^3.0.0: + version "3.0.1" + resolved "https://registry.yarnpkg.com/totalist/-/totalist-3.0.1.tgz#ba3a3d600c915b1a97872348f79c127475f6acf8" + integrity sha512-sf4i37nQ2LBx4m3wB74y+ubopq6W/dIzXg0FDGjsYnZHVa1Da8FH853wlL2gtUhg+xJXjfk3kUZS3BRoQeoQBQ== -trim@0.0.1: - version "0.0.1" - resolved "https://registry.npmjs.org/trim/-/trim-0.0.1.tgz" - integrity sha512-YzQV+TZg4AxpKxaTHK3c3D+kRDCGVEE7LemdlQZoQXn0iennk10RsIoY6ikzAqJTc9Xjl9C1/waHom/J86ziAQ== +trim-lines@^3.0.0: + version "3.0.1" + resolved "https://registry.yarnpkg.com/trim-lines/-/trim-lines-3.0.1.tgz#d802e332a07df861c48802c04321017b1bd87338" + integrity sha512-kRj8B+YHZCc9kQYdWfJB2/oUl9rA99qbowYYBtr4ui4mZyAQ2JpvVBd/6U2YloATfqBhBTSMhTpgBHtU0Mf3Rg== trim@^1.0.1: version "1.0.1" resolved "https://registry.npmjs.org/trim/-/trim-1.0.1.tgz" integrity sha512-3JVP2YVqITUisXblCDq/Bi4P9457G/sdEamInkyvCsjbTcXLXIiG7XCb4kGMFWh6JGXesS3TKxOPtrncN/xe8w== -trough@^1.0.0: - version "1.0.5" - resolved "https://registry.npmjs.org/trough/-/trough-1.0.5.tgz" - integrity sha512-rvuRbTarPXmMb79SmzEp8aqXNKcK+y0XaB298IXueQ8I2PsrATcPBCSPyK/dDNa2iWOhKlfNnOjdAOTBU/nkFA== +trough@^2.0.0: + version "2.2.0" + resolved "https://registry.yarnpkg.com/trough/-/trough-2.2.0.tgz#94a60bd6bd375c152c1df911a4b11d5b0256f50f" + integrity sha512-tmMpK00BjZiUyVyvrBK7knerNgmgvcV/KLVyuma/SC+TQN167GrMRciANTz09+k3zW8L8t60jWO1GpfkZdjTaw== -tslib@^2.0.3, tslib@^2.1.0, tslib@^2.4.0: +tslib@^2.0.3, tslib@^2.4.0: version "2.5.0" resolved "https://registry.npmjs.org/tslib/-/tslib-2.5.0.tgz" integrity sha512-336iVw3rtn2BUK7ORdIAHTyxHGRIHVReokCR3XjbckJMK7ms8FysBfhLR8IXnAgy7T0PTPNBWKiH514FOW/WSg== -type-fest@^0.20.2: - version "0.20.2" - resolved "https://registry.npmjs.org/type-fest/-/type-fest-0.20.2.tgz" - integrity sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ== +tslib@^2.6.0: + version "2.8.1" + resolved "https://registry.yarnpkg.com/tslib/-/tslib-2.8.1.tgz#612efe4ed235d567e8aba5f2a5fab70280ade83f" + integrity sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w== + +type-fest@^0.21.3: + version "0.21.3" + resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-0.21.3.tgz#d260a24b0198436e133fa26a524a6d65fa3b2e37" + integrity sha512-t0rzBq87m3fVcduHDUFhKmyyX+9eo6WQjZvf51Ea/M0Q7+T374Jp1aUiyUl0GKxp8M/OETVHSDvmkyPgvX+X2w== -type-fest@^2.5.0: +type-fest@^1.0.1: + version "1.4.0" + resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-1.4.0.tgz#e9fb813fe3bf1744ec359d55d1affefa76f14be1" + integrity sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA== + +type-fest@^2.13.0, type-fest@^2.5.0: version "2.19.0" resolved "https://registry.npmjs.org/type-fest/-/type-fest-2.19.0.tgz" integrity sha512-RAH822pAdBgcNMAfWnCBU3CFZcfZ/i1eZjwFU/dsLKumyuuP3niueg2UAukXYF0E2AAoc82ZSSf9J0WQBinzHA== @@ -7371,24 +9205,21 @@ typedarray-to-buffer@^3.1.5: dependencies: is-typedarray "^1.0.0" -ua-parser-js@^0.7.30, ua-parser-js@^0.7.33: +ua-parser-js@^0.7.33: version "0.7.39" resolved "https://registry.yarnpkg.com/ua-parser-js/-/ua-parser-js-0.7.39.tgz#c71efb46ebeabc461c4612d22d54f88880fabe7e" integrity sha512-IZ6acm6RhQHNibSt7+c09hhvsKy9WUr4DVbeq9U8o71qxyYtJpQeDxQnMrVqnIFMLcQjHO0I9wgfO2vIahht4w== -unherit@^1.0.4: - version "1.1.3" - resolved "https://registry.npmjs.org/unherit/-/unherit-1.1.3.tgz" - integrity sha512-Ft16BJcnapDKp0+J/rqFC3Rrk6Y/Ng4nzsC028k2jdDII/rdZ7Wd3pPT/6+vIIxRagwRc9K0IUX0Ra4fKvw+WQ== - dependencies: - inherits "^2.0.0" - xtend "^4.0.0" - unicode-canonical-property-names-ecmascript@^2.0.0: version "2.0.0" resolved "https://registry.npmjs.org/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-2.0.0.tgz" integrity sha512-yY5PpDlfVIU5+y/BSCxAJRBIS1Zc2dDG3Ujq+sR0U+JjUevW2JhocOF+soROYDSaAezOzOKuyyixhD6mBknSmQ== +unicode-emoji-modifier-base@^1.0.0: + version "1.0.0" + resolved "https://registry.yarnpkg.com/unicode-emoji-modifier-base/-/unicode-emoji-modifier-base-1.0.0.tgz#dbbd5b54ba30f287e2a8d5a249da6c0cef369459" + integrity sha512-yLSH4py7oFH3oG/9K+XWrz1pSi3dfUrWEnInbxMfArOfc1+33BlGPQtLsOYwvdMy11AwUBetYuaRxSPqgkq+8g== + unicode-match-property-ecmascript@^2.0.0: version "2.0.0" resolved "https://registry.npmjs.org/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-2.0.0.tgz" @@ -7407,94 +9238,70 @@ unicode-property-aliases-ecmascript@^2.0.0: resolved "https://registry.npmjs.org/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-2.1.0.tgz" integrity sha512-6t3foTQI9qne+OZoVQB/8x8rk2k1eVy1gRXhV3oFQ5T6R1dqQ1xtin3XqSlx3+ATBkliTaR/hHyJBm+LVPNM8w== -unified@9.2.0: - version "9.2.0" - resolved "https://registry.npmjs.org/unified/-/unified-9.2.0.tgz" - integrity sha512-vx2Z0vY+a3YoTj8+pttM3tiJHCwY5UFbYdiWrwBEbHmK8pvsPj2rtAX2BFfgXen8T39CJWblWRDT4L5WGXtDdg== +unified@^11.0.0, unified@^11.0.3, unified@^11.0.4: + version "11.0.5" + resolved "https://registry.yarnpkg.com/unified/-/unified-11.0.5.tgz#f66677610a5c0a9ee90cab2b8d4d66037026d9e1" + integrity sha512-xKvGhPWw3k84Qjh8bI3ZeJjqnyadK+GEFtazSfZv/rKeTkTjOJho6mFqh2SM96iIcZokxiOpg78GazTSg8+KHA== dependencies: - bail "^1.0.0" + "@types/unist" "^3.0.0" + bail "^2.0.0" + devlop "^1.0.0" extend "^3.0.0" - is-buffer "^2.0.0" - is-plain-obj "^2.0.0" - trough "^1.0.0" - vfile "^4.0.0" + is-plain-obj "^4.0.0" + trough "^2.0.0" + vfile "^6.0.0" -unified@^9.2.2: - version "9.2.2" - resolved "https://registry.npmjs.org/unified/-/unified-9.2.2.tgz" - integrity sha512-Sg7j110mtefBD+qunSLO1lqOEKdrwBFBrR6Qd8f4uwkhWNlbkaqwHse6e7QvD3AP/MNoJdEDLaf8OxYyoWgorQ== +unique-string@^3.0.0: + version "3.0.0" + resolved "https://registry.yarnpkg.com/unique-string/-/unique-string-3.0.0.tgz#84a1c377aff5fd7a8bc6b55d8244b2bd90d75b9a" + integrity sha512-VGXBUVwxKMBUznyffQweQABPRRW1vHZAbadFZud4pLFAqRGvv/96vafgjWFqzourzr8YonlQiPgH0YCJfawoGQ== dependencies: - bail "^1.0.0" - extend "^3.0.0" - is-buffer "^2.0.0" - is-plain-obj "^2.0.0" - trough "^1.0.0" - vfile "^4.0.0" + crypto-random-string "^4.0.0" -unique-string@^2.0.0: - version "2.0.0" - resolved "https://registry.npmjs.org/unique-string/-/unique-string-2.0.0.tgz" - integrity sha512-uNaeirEPvpZWSgzwsPGtU2zVSTrn/8L5q/IexZmH0eH6SA73CmAA5U4GwORTxQAZs95TAXLNqeLoPPNO5gZfWg== +unist-util-is@^6.0.0: + version "6.0.0" + resolved "https://registry.yarnpkg.com/unist-util-is/-/unist-util-is-6.0.0.tgz#b775956486aff107a9ded971d996c173374be424" + integrity sha512-2qCTHimwdxLfz+YzdGfkqNlH0tLi9xjTnHddPmJwtIG9MGsdbutfTc4P+haPD7l7Cjxf/WZj+we5qfVPvvxfYw== dependencies: - crypto-random-string "^2.0.0" - -unist-builder@2.0.3, unist-builder@^2.0.0: - version "2.0.3" - resolved "https://registry.npmjs.org/unist-builder/-/unist-builder-2.0.3.tgz" - integrity sha512-f98yt5pnlMWlzP539tPc4grGMsFaQQlP/vM396b00jngsiINumNmsY8rkXjfoi1c6QaM8nQ3vaGDuoKWbe/1Uw== - -unist-util-generated@^1.0.0: - version "1.1.6" - resolved "https://registry.npmjs.org/unist-util-generated/-/unist-util-generated-1.1.6.tgz" - integrity sha512-cln2Mm1/CZzN5ttGK7vkoGw+RZ8VcUH6BtGbq98DDtRGquAAOXig1mrBQYelOwMXYS8rK+vZDyyojSjp7JX+Lg== - -unist-util-is@^4.0.0: - version "4.1.0" - resolved "https://registry.npmjs.org/unist-util-is/-/unist-util-is-4.1.0.tgz" - integrity sha512-ZOQSsnce92GrxSqlnEEseX0gi7GH9zTJZ0p9dtu87WRb/37mMPO2Ilx1s/t9vBHrFhbgweUwb+t7cIn5dxPhZg== - -unist-util-position@^3.0.0: - version "3.1.0" - resolved "https://registry.npmjs.org/unist-util-position/-/unist-util-position-3.1.0.tgz" - integrity sha512-w+PkwCbYSFw8vpgWD0v7zRCl1FpY3fjDSQ3/N/wNd9Ffa4gPi8+4keqt99N3XW6F99t/mUzp2xAhNmfKWp95QA== + "@types/unist" "^3.0.0" -unist-util-remove-position@^2.0.0: - version "2.0.1" - resolved "https://registry.npmjs.org/unist-util-remove-position/-/unist-util-remove-position-2.0.1.tgz" - integrity sha512-fDZsLYIe2uT+oGFnuZmy73K6ZxOPG/Qcm+w7jbEjaFcJgbQ6cqjs/eSPzXhsmGpAsWPkqZM9pYjww5QTn3LHMA== +unist-util-position-from-estree@^2.0.0: + version "2.0.0" + resolved "https://registry.yarnpkg.com/unist-util-position-from-estree/-/unist-util-position-from-estree-2.0.0.tgz#d94da4df596529d1faa3de506202f0c9a23f2200" + integrity sha512-KaFVRjoqLyF6YXCbVLNad/eS4+OfPQQn2yOd7zF/h5T/CSL2v8NpN6a5TPvtbXthAGw5nG+PuTtq+DdIZr+cRQ== dependencies: - unist-util-visit "^2.0.0" + "@types/unist" "^3.0.0" -unist-util-remove@^2.0.0: - version "2.1.0" - resolved "https://registry.npmjs.org/unist-util-remove/-/unist-util-remove-2.1.0.tgz" - integrity sha512-J8NYPyBm4baYLdCbjmf1bhPu45Cr1MWTm77qd9istEkzWpnN6O9tMsEbB2JhNnBCqGENRqEWomQ+He6au0B27Q== +unist-util-position@^5.0.0: + version "5.0.0" + resolved "https://registry.yarnpkg.com/unist-util-position/-/unist-util-position-5.0.0.tgz#678f20ab5ca1207a97d7ea8a388373c9cf896be4" + integrity sha512-fucsC7HjXvkB5R3kTCO7kUjRdrS0BJt3M/FPxmHMBOm8JQi2BsHAHFsy27E0EolP8rp0NzXsJ+jNPyDWvOJZPA== dependencies: - unist-util-is "^4.0.0" + "@types/unist" "^3.0.0" -unist-util-stringify-position@^2.0.0: - version "2.0.3" - resolved "https://registry.npmjs.org/unist-util-stringify-position/-/unist-util-stringify-position-2.0.3.tgz" - integrity sha512-3faScn5I+hy9VleOq/qNbAd6pAx7iH5jYBMS9I1HgQVijz/4mv5Bvw5iw1sC/90CODiKo81G/ps8AJrISn687g== +unist-util-stringify-position@^4.0.0: + version "4.0.0" + resolved "https://registry.yarnpkg.com/unist-util-stringify-position/-/unist-util-stringify-position-4.0.0.tgz#449c6e21a880e0855bf5aabadeb3a740314abac2" + integrity sha512-0ASV06AAoKCDkS2+xw5RXJywruurpbC4JZSm7nr7MOt1ojAzvyyaO+UxZf18j8FCF6kmzCZKcAgN/yu2gm2XgQ== dependencies: - "@types/unist" "^2.0.2" + "@types/unist" "^3.0.0" -unist-util-visit-parents@^3.0.0: - version "3.1.1" - resolved "https://registry.npmjs.org/unist-util-visit-parents/-/unist-util-visit-parents-3.1.1.tgz" - integrity sha512-1KROIZWo6bcMrZEwiH2UrXDyalAa0uqzWCxCJj6lPOvTve2WkfgCytoDTPaMnodXh1WrXOq0haVYHj99ynJlsg== +unist-util-visit-parents@^6.0.0: + version "6.0.1" + resolved "https://registry.yarnpkg.com/unist-util-visit-parents/-/unist-util-visit-parents-6.0.1.tgz#4d5f85755c3b8f0dc69e21eca5d6d82d22162815" + integrity sha512-L/PqWzfTP9lzzEa6CKs0k2nARxTdZduw3zyh8d2NVBnsyvHjSX4TWse388YrrQKbvI8w20fGjGlhgT96WwKykw== dependencies: - "@types/unist" "^2.0.0" - unist-util-is "^4.0.0" + "@types/unist" "^3.0.0" + unist-util-is "^6.0.0" -unist-util-visit@2.0.3, unist-util-visit@^2.0.0, unist-util-visit@^2.0.3: - version "2.0.3" - resolved "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-2.0.3.tgz" - integrity sha512-iJ4/RczbJMkD0712mGktuGpm/U4By4FfDonL7N/9tATGIF4imikjOuagyMY53tnZq3NP6BcmlrHhEKAfGWjh7Q== +unist-util-visit@^5.0.0: + version "5.0.0" + resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-5.0.0.tgz#a7de1f31f72ffd3519ea71814cccf5fd6a9217d6" + integrity sha512-MR04uvD+07cwl/yhVuVWAtw+3GOR/knlL55Nd/wAdblk27GCVt3lqpTivy/tkJcZoNPzTwS1Y+KMojlLDhoTzg== dependencies: - "@types/unist" "^2.0.0" - unist-util-is "^4.0.0" - unist-util-visit-parents "^3.0.0" + "@types/unist" "^3.0.0" + unist-util-is "^6.0.0" + unist-util-visit-parents "^6.0.0" universalify@^2.0.0: version "2.0.0" @@ -7514,25 +9321,25 @@ update-browserslist-db@^1.1.1: escalade "^3.2.0" picocolors "^1.1.0" -update-notifier@^5.1.0: - version "5.1.0" - resolved "https://registry.npmjs.org/update-notifier/-/update-notifier-5.1.0.tgz" - integrity sha512-ItnICHbeMh9GqUy31hFPrD1kcuZ3rpxDZbf4KUDavXwS0bW5m7SLbDQpGX3UYr072cbrF5hFUs3r5tUsPwjfHw== +update-notifier@^6.0.2: + version "6.0.2" + resolved "https://registry.yarnpkg.com/update-notifier/-/update-notifier-6.0.2.tgz#a6990253dfe6d5a02bd04fbb6a61543f55026b60" + integrity sha512-EDxhTEVPZZRLWYcJ4ZXjGFN0oP7qYvbXWzEgRm/Yql4dHX5wDbvh89YHP6PK1lzZJYrMtXUuZZz8XGK+U6U1og== dependencies: - boxen "^5.0.0" - chalk "^4.1.0" - configstore "^5.0.1" - has-yarn "^2.1.0" - import-lazy "^2.1.0" - is-ci "^2.0.0" + boxen "^7.0.0" + chalk "^5.0.1" + configstore "^6.0.0" + has-yarn "^3.0.0" + import-lazy "^4.0.0" + is-ci "^3.0.1" is-installed-globally "^0.4.0" - is-npm "^5.0.0" - is-yarn-global "^0.3.0" - latest-version "^5.1.0" - pupa "^2.1.1" - semver "^7.3.4" - semver-diff "^3.1.1" - xdg-basedir "^4.0.0" + is-npm "^6.0.0" + is-yarn-global "^0.4.0" + latest-version "^7.0.0" + pupa "^3.1.0" + semver "^7.3.7" + semver-diff "^4.0.0" + xdg-basedir "^5.1.0" uri-js@^4.2.2: version "4.4.1" @@ -7550,35 +9357,6 @@ url-loader@^4.1.1: mime-types "^2.1.27" schema-utils "^3.0.0" -url-parse-lax@^3.0.0: - version "3.0.0" - resolved "https://registry.npmjs.org/url-parse-lax/-/url-parse-lax-3.0.0.tgz" - integrity sha512-NjFKA0DidqPa5ciFcSrXnAltTtzz84ogy+NebPvfEgAck0+TNg4UJ4IN+fB7zRZfbgUf0syOo9MDxFkDSMuFaQ== - dependencies: - prepend-http "^2.0.0" - -use-composed-ref@^1.3.0: - version "1.3.0" - resolved "https://registry.npmjs.org/use-composed-ref/-/use-composed-ref-1.3.0.tgz" - integrity sha512-GLMG0Jc/jiKov/3Ulid1wbv3r54K9HlMW29IWcDFPEqFkSO2nS0MuefWgMJpeHQ9YJeXDL3ZUF+P3jdXlZX/cQ== - -use-isomorphic-layout-effect@^1.1.1: - version "1.1.2" - resolved "https://registry.npmjs.org/use-isomorphic-layout-effect/-/use-isomorphic-layout-effect-1.1.2.tgz" - integrity sha512-49L8yCO3iGT/ZF9QttjwLF/ZD9Iwto5LnH5LmEdk/6cFmXddqi2ulF0edxTwjj+7mqvpVVGQWvbXZdn32wRSHA== - -use-latest@^1.2.1: - version "1.2.1" - resolved "https://registry.npmjs.org/use-latest/-/use-latest-1.2.1.tgz" - integrity sha512-xA+AVm/Wlg3e2P/JiItTziwS7FK92LWrDB0p+hgXloIMuVCeJJ8v6f0eeHyPZaJrM+usM1FkFfbNCrJGs8A/zw== - dependencies: - use-isomorphic-layout-effect "^1.1.1" - -use-sync-external-store@^1.2.0: - version "1.2.0" - resolved "https://registry.npmjs.org/use-sync-external-store/-/use-sync-external-store-1.2.0.tgz" - integrity sha512-eEgnFxGQ1Ife9bzYs6VLi8/4X6CObHMw9Qr9tPY43iKwsPw8xE8+EFsf/2cFZ5S3esXgpWgtSCtLNS41F+sKPA== - util-deprecate@^1.0.1, util-deprecate@^1.0.2, util-deprecate@~1.0.1: version "1.0.2" resolved "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz" @@ -7614,39 +9392,29 @@ vary@~1.1.2: resolved "https://registry.npmjs.org/vary/-/vary-1.1.2.tgz" integrity sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg== -vfile-location@^3.0.0, vfile-location@^3.2.0: - version "3.2.0" - resolved "https://registry.npmjs.org/vfile-location/-/vfile-location-3.2.0.tgz" - integrity sha512-aLEIZKv/oxuCDZ8lkJGhuhztf/BW4M+iHdCwglA/eWc+vtuRFJj8EtgceYFX4LRjOhCAAiNHsKGssC6onJ+jbA== - -vfile-message@^2.0.0: - version "2.0.4" - resolved "https://registry.npmjs.org/vfile-message/-/vfile-message-2.0.4.tgz" - integrity sha512-DjssxRGkMvifUOJre00juHoP9DPWuzjxKuMDrhNbk2TdaYYBNMStsNhEOt3idrtI12VQYM/1+iM0KOzXi4pxwQ== +vfile-location@^5.0.0: + version "5.0.3" + resolved "https://registry.yarnpkg.com/vfile-location/-/vfile-location-5.0.3.tgz#cb9eacd20f2b6426d19451e0eafa3d0a846225c3" + integrity sha512-5yXvWDEgqeiYiBe1lbxYF7UMAIm/IcopxMHrMQDq3nvKcjPKIhZklUKL+AE7J7uApI4kwe2snsK+eI6UTj9EHg== dependencies: - "@types/unist" "^2.0.0" - unist-util-stringify-position "^2.0.0" + "@types/unist" "^3.0.0" + vfile "^6.0.0" -vfile@^4.0.0: - version "4.2.1" - resolved "https://registry.npmjs.org/vfile/-/vfile-4.2.1.tgz" - integrity sha512-O6AE4OskCG5S1emQ/4gl8zK586RqA3srz3nfK/Viy0UPToBc5Trp9BVFb1u0CjsKrAWwnpr4ifM/KBXPWwJbCA== +vfile-message@^4.0.0: + version "4.0.2" + resolved "https://registry.yarnpkg.com/vfile-message/-/vfile-message-4.0.2.tgz#c883c9f677c72c166362fd635f21fc165a7d1181" + integrity sha512-jRDZ1IMLttGj41KcZvlrYAaI3CfqpLpfpf+Mfig13viT6NKvRzWZ+lXz0Y5D60w6uJIBAOGq9mSHf0gktF0duw== dependencies: - "@types/unist" "^2.0.0" - is-buffer "^2.0.0" - unist-util-stringify-position "^2.0.0" - vfile-message "^2.0.0" + "@types/unist" "^3.0.0" + unist-util-stringify-position "^4.0.0" -wait-on@^6.0.1: - version "6.0.1" - resolved "https://registry.npmjs.org/wait-on/-/wait-on-6.0.1.tgz" - integrity sha512-zht+KASY3usTY5u2LgaNqn/Cd8MukxLGjdcZxT2ns5QzDmTFc4XoWBgC+C/na+sMRZTuVygQoMYwdcVjHnYIVw== +vfile@^6.0.0, vfile@^6.0.1: + version "6.0.3" + resolved "https://registry.yarnpkg.com/vfile/-/vfile-6.0.3.tgz#3652ab1c496531852bf55a6bac57af981ebc38ab" + integrity sha512-KzIbH/9tXat2u30jf+smMwFCsno4wHVdNmzFyL+T/L3UGqqk6JKfVqOFOZEpZSHADH1k40ab6NUIXZq422ov3Q== dependencies: - axios "^0.25.0" - joi "^17.6.0" - lodash "^4.17.21" - minimist "^1.2.5" - rxjs "^7.5.4" + "@types/unist" "^3.0.0" + vfile-message "^4.0.0" watchpack@^2.4.1: version "2.4.2" @@ -7663,34 +9431,32 @@ wbuf@^1.1.0, wbuf@^1.7.3: dependencies: minimalistic-assert "^1.0.0" -web-namespaces@^1.0.0: - version "1.1.4" - resolved "https://registry.npmjs.org/web-namespaces/-/web-namespaces-1.1.4.tgz" - integrity sha512-wYxSGajtmoP4WxfejAPIr4l0fVh+jeMXZb08wNc0tMg6xsfZXj3cECqIK0G7ZAqUq0PP8WlMDtaOGVBTAWztNw== - -webidl-conversions@^3.0.0: - version "3.0.1" - resolved "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz" - integrity sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ== +web-namespaces@^2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/web-namespaces/-/web-namespaces-2.0.1.tgz#1010ff7c650eccb2592cebeeaf9a1b253fd40692" + integrity sha512-bKr1DkiNa2krS7qxNtdrtHAmzuYGFQLiQ13TsorsdT6ULTkPLKuu5+GsFpDlg6JFjUTwX2DyhMPG2be8uPrqsQ== -webpack-bundle-analyzer@^4.5.0: - version "4.7.0" - resolved "https://registry.npmjs.org/webpack-bundle-analyzer/-/webpack-bundle-analyzer-4.7.0.tgz" - integrity sha512-j9b8ynpJS4K+zfO5GGwsAcQX4ZHpWV+yRiHDiL+bE0XHJ8NiPYLTNVQdlFYWxtpg9lfAQNlwJg16J9AJtFSXRg== +webpack-bundle-analyzer@^4.10.2: + version "4.10.2" + resolved "https://registry.yarnpkg.com/webpack-bundle-analyzer/-/webpack-bundle-analyzer-4.10.2.tgz#633af2862c213730be3dbdf40456db171b60d5bd" + integrity sha512-vJptkMm9pk5si4Bv922ZbKLV8UTT4zib4FPgXMhgzUny0bfDDkLXAVQs3ly3fS4/TN9ROFtb0NFrm04UXFE/Vw== dependencies: + "@discoveryjs/json-ext" "0.5.7" acorn "^8.0.4" acorn-walk "^8.0.0" - chalk "^4.1.0" commander "^7.2.0" + debounce "^1.2.1" + escape-string-regexp "^4.0.0" gzip-size "^6.0.0" - lodash "^4.17.20" + html-escaper "^2.0.2" opener "^1.5.2" - sirv "^1.0.7" + picocolors "^1.0.0" + sirv "^2.0.3" ws "^7.3.1" -webpack-dev-middleware@^5.3.1: +webpack-dev-middleware@^5.3.4: version "5.3.4" - resolved "https://registry.npmjs.org/webpack-dev-middleware/-/webpack-dev-middleware-5.3.4.tgz" + resolved "https://registry.yarnpkg.com/webpack-dev-middleware/-/webpack-dev-middleware-5.3.4.tgz#eb7b39281cbce10e104eb2b8bf2b63fce49a3517" integrity sha512-BVdTqhhs+0IfoeAf7EoH5WE+exCmqGerHfDM0IL096Px60Tq2Mn9MAbnaGUe6HiMa41KMCYF19gyzZmBcq/o4Q== dependencies: colorette "^2.0.10" @@ -7699,10 +9465,10 @@ webpack-dev-middleware@^5.3.1: range-parser "^1.2.1" schema-utils "^4.0.0" -webpack-dev-server@^4.9.3: - version "4.11.1" - resolved "https://registry.npmjs.org/webpack-dev-server/-/webpack-dev-server-4.11.1.tgz" - integrity sha512-lILVz9tAUy1zGFwieuaQtYiadImb5M3d+H+L1zDYalYoDl0cksAB1UNyuE5MMWJrG6zR1tXkCP2fitl7yoUJiw== +webpack-dev-server@^4.15.2: + version "4.15.2" + resolved "https://registry.yarnpkg.com/webpack-dev-server/-/webpack-dev-server-4.15.2.tgz#9e0c70a42a012560860adb186986da1248333173" + integrity sha512-0XavAZbNJ5sDrCbkpWL8mia0o5WPOd2YGtxrEiZkBK9FjLppIUK2TgxK6qGD2P3hUXTJNNPVibrerKcx5WkR1g== dependencies: "@types/bonjour" "^3.5.9" "@types/connect-history-api-fallback" "^1.3.5" @@ -7710,7 +9476,7 @@ webpack-dev-server@^4.9.3: "@types/serve-index" "^1.9.1" "@types/serve-static" "^1.13.10" "@types/sockjs" "^0.3.33" - "@types/ws" "^8.5.1" + "@types/ws" "^8.5.5" ansi-html-community "^0.0.8" bonjour-service "^1.0.11" chokidar "^3.5.3" @@ -7723,6 +9489,7 @@ webpack-dev-server@^4.9.3: html-entities "^2.3.2" http-proxy-middleware "^2.0.3" ipaddr.js "^2.0.1" + launch-editor "^2.6.0" open "^8.0.9" p-retry "^4.5.0" rimraf "^3.0.2" @@ -7731,23 +9498,62 @@ webpack-dev-server@^4.9.3: serve-index "^1.9.1" sockjs "^0.3.24" spdy "^4.0.2" - webpack-dev-middleware "^5.3.1" - ws "^8.4.2" + webpack-dev-middleware "^5.3.4" + ws "^8.13.0" -webpack-merge@^5.8.0: - version "5.8.0" - resolved "https://registry.npmjs.org/webpack-merge/-/webpack-merge-5.8.0.tgz" - integrity sha512-/SaI7xY0831XwP6kzuwhKWVKDP9t1QY1h65lAFLbZqMPIuYcD9QAW4u9STIbU9kaJbPBB/geU/gLr1wDjOhQ+Q== +webpack-merge@^5.9.0: + version "5.10.0" + resolved "https://registry.yarnpkg.com/webpack-merge/-/webpack-merge-5.10.0.tgz#a3ad5d773241e9c682803abf628d4cd62b8a4177" + integrity sha512-+4zXKdx7UnO+1jaN4l2lHVD+mFvnlZQP/6ljaJVb4SZiwIKeUnrT5l0gkT8z+n4hKpC+jpOv6O9R+gLtag7pSA== dependencies: clone-deep "^4.0.1" + flat "^5.0.2" wildcard "^2.0.0" -webpack-sources@^3.2.2, webpack-sources@^3.2.3: +webpack-merge@^6.0.1: + version "6.0.1" + resolved "https://registry.yarnpkg.com/webpack-merge/-/webpack-merge-6.0.1.tgz#50c776868e080574725abc5869bd6e4ef0a16c6a" + integrity sha512-hXXvrjtx2PLYx4qruKl+kyRSLc52V+cCvMxRjmKwoA+CBbbF5GfIBtR6kCvl0fYGqTUPKB+1ktVmTHqMOzgCBg== + dependencies: + clone-deep "^4.0.1" + flat "^5.0.2" + wildcard "^2.0.1" + +webpack-sources@^3.2.3: version "3.2.3" resolved "https://registry.npmjs.org/webpack-sources/-/webpack-sources-3.2.3.tgz" integrity sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w== -webpack@^5.73.0, webpack@^5.94.0: +webpack@^5.88.1, webpack@^5.95.0: + version "5.97.1" + resolved "https://registry.yarnpkg.com/webpack/-/webpack-5.97.1.tgz#972a8320a438b56ff0f1d94ade9e82eac155fa58" + integrity sha512-EksG6gFY3L1eFMROS/7Wzgrii5mBAFe4rIr3r2BTfo7bcc+DWwFZ4OJ/miOuHJO/A85HwyI4eQ0F6IKXesO7Fg== + dependencies: + "@types/eslint-scope" "^3.7.7" + "@types/estree" "^1.0.6" + "@webassemblyjs/ast" "^1.14.1" + "@webassemblyjs/wasm-edit" "^1.14.1" + "@webassemblyjs/wasm-parser" "^1.14.1" + acorn "^8.14.0" + browserslist "^4.24.0" + chrome-trace-event "^1.0.2" + enhanced-resolve "^5.17.1" + es-module-lexer "^1.2.1" + eslint-scope "5.1.1" + events "^3.2.0" + glob-to-regexp "^0.4.1" + graceful-fs "^4.2.11" + json-parse-even-better-errors "^2.3.1" + loader-runner "^4.2.0" + mime-types "^2.1.27" + neo-async "^2.6.2" + schema-utils "^3.2.0" + tapable "^2.1.1" + terser-webpack-plugin "^5.3.10" + watchpack "^2.4.1" + webpack-sources "^3.2.3" + +webpack@^5.94.0: version "5.94.0" resolved "https://registry.npmjs.org/webpack/-/webpack-5.94.0.tgz" integrity sha512-KcsGn50VT+06JH/iunZJedYGUJS5FGjow8wb9c0v5n1Om8O1g4L6LjtfxwlXIATopoQu+vOXXa7gYisWxCoPyg== @@ -7776,15 +9582,19 @@ webpack@^5.73.0, webpack@^5.94.0: watchpack "^2.4.1" webpack-sources "^3.2.3" -webpackbar@^5.0.2: - version "5.0.2" - resolved "https://registry.npmjs.org/webpackbar/-/webpackbar-5.0.2.tgz" - integrity sha512-BmFJo7veBDgQzfWXl/wwYXr/VFus0614qZ8i9znqcl9fnEdiVkdbi0TedLQ6xAK92HZHDJ0QmyQ0fmuZPAgCYQ== +webpackbar@^6.0.1: + version "6.0.1" + resolved "https://registry.yarnpkg.com/webpackbar/-/webpackbar-6.0.1.tgz#5ef57d3bf7ced8b19025477bc7496ea9d502076b" + integrity sha512-TnErZpmuKdwWBdMoexjio3KKX6ZtoKHRVvLIU0A47R0VVBDtx3ZyOJDktgYixhoJokZTYTt1Z37OkO9pnGJa9Q== dependencies: - chalk "^4.1.0" - consola "^2.15.3" + ansi-escapes "^4.3.2" + chalk "^4.1.2" + consola "^3.2.3" + figures "^3.2.0" + markdown-table "^2.0.0" pretty-time "^1.1.0" - std-env "^3.0.1" + std-env "^3.7.0" + wrap-ansi "^7.0.0" websocket-driver@>=0.5.1, websocket-driver@^0.7.4: version "0.7.4" @@ -7800,14 +9610,6 @@ websocket-extensions@>=0.1.1: resolved "https://registry.npmjs.org/websocket-extensions/-/websocket-extensions-0.1.4.tgz" integrity sha512-OqedPIGOfsDlo31UNwYbCFMSaO9m9G/0faIHj5/dZFDMFqPTcx6UwqyOy3COEaEOg/9VsGIpdqn62W5KhoKSpg== -whatwg-url@^5.0.0: - version "5.0.0" - resolved "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz" - integrity sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw== - dependencies: - tr46 "~0.0.3" - webidl-conversions "^3.0.0" - which@^1.2.9, which@^1.3.1: version "1.3.1" resolved "https://registry.npmjs.org/which/-/which-1.3.1.tgz" @@ -7822,13 +9624,6 @@ which@^2.0.1: dependencies: isexe "^2.0.0" -widest-line@^3.1.0: - version "3.1.0" - resolved "https://registry.npmjs.org/widest-line/-/widest-line-3.1.0.tgz" - integrity sha512-NsmoXalsWVDMGupxZ5R08ka9flZjjiLvHVAWYOKtiKM8ujtZWr9cRffak+uSE48+Ob8ObalXpwyeUiyDD6QFgg== - dependencies: - string-width "^4.0.0" - widest-line@^4.0.1: version "4.0.1" resolved "https://registry.npmjs.org/widest-line/-/widest-line-4.0.1.tgz" @@ -7841,6 +9636,11 @@ wildcard@^2.0.0: resolved "https://registry.npmjs.org/wildcard/-/wildcard-2.0.0.tgz" integrity sha512-JcKqAHLPxcdb9KM49dufGXn2x3ssnfjbcaQdLlfZsL9rH9wgDQjUtDxbo8NE0F6SFvydeu1VhZe7hZuHsB2/pw== +wildcard@^2.0.1: + version "2.0.1" + resolved "https://registry.yarnpkg.com/wildcard/-/wildcard-2.0.1.tgz#5ab10d02487198954836b6349f74fff961e10f67" + integrity sha512-CC1bOL87PIWSBhDcTrdeLo6eGT7mCFtrg0uIJtqJUFyK+eJnzl8A1niH56uu7KMa5XFrtiV+AQuHO3n7DsHnLQ== + wrap-ansi@^7.0.0: version "7.0.0" resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz" @@ -7850,7 +9650,7 @@ wrap-ansi@^7.0.0: string-width "^4.1.0" strip-ansi "^6.0.0" -wrap-ansi@^8.0.1: +wrap-ansi@^8.0.1, wrap-ansi@^8.1.0: version "8.1.0" resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-8.1.0.tgz" integrity sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ== @@ -7864,9 +9664,9 @@ wrappy@1: resolved "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz" integrity sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ== -write-file-atomic@^3.0.0: +write-file-atomic@^3.0.3: version "3.0.3" - resolved "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-3.0.3.tgz" + resolved "https://registry.yarnpkg.com/write-file-atomic/-/write-file-atomic-3.0.3.tgz#56bd5c5a5c70481cd19c571bd39ab965a5de56e8" integrity sha512-AvHcyZ5JnSfq3ioSyjrBkH9yW4m7Ayk8/9My/DD9onKeu/94fwrMocemO2QAJFAlnnDN+ZDS+ZjAR5ua1/PV/Q== dependencies: imurmurhash "^0.1.4" @@ -7879,15 +9679,15 @@ ws@^7.3.1: resolved "https://registry.npmjs.org/ws/-/ws-7.5.10.tgz" integrity sha512-+dbF1tHwZpXcbOJdVOkzLDxZP1ailvSxM6ZweXTegylPny803bFhA+vqBYw4s31NSAk4S2Qz+AKXK9a4wkdjcQ== -ws@^8.4.2: +ws@^8.13.0: version "8.18.0" - resolved "https://registry.npmjs.org/ws/-/ws-8.18.0.tgz" + resolved "https://registry.yarnpkg.com/ws/-/ws-8.18.0.tgz#0d7505a6eafe2b0e712d232b42279f53bc289bbc" integrity sha512-8VbfWfHLbbwu3+N6OKsOMpBdT4kXPDDB9cJk2bJ6mh9ucxdlnNvH1e+roYkKmN9Nxw2yjz7VzeO9oOz2zJ04Pw== -xdg-basedir@^4.0.0: - version "4.0.0" - resolved "https://registry.npmjs.org/xdg-basedir/-/xdg-basedir-4.0.0.tgz" - integrity sha512-PSNhEJDejZYV7h50BohL09Er9VaIefr2LMAf3OEmpCkjOi34eYyQYAXUTjEQtZJTKcF0E2UKTh+osDLsgNim9Q== +xdg-basedir@^5.0.1, xdg-basedir@^5.1.0: + version "5.1.0" + resolved "https://registry.yarnpkg.com/xdg-basedir/-/xdg-basedir-5.1.0.tgz#1efba19425e73be1bc6f2a6ceb52a3d2c884c0c9" + integrity sha512-GCPAHLvrIH13+c0SuacwvRYj2SxJXQ4kaVTT5xgL3kPrz56XxkF21IGhjSE1+W0aw7gpBWRGXLCPnPby6lSpmQ== xml-js@^1.6.11: version "1.6.11" @@ -7896,11 +9696,6 @@ xml-js@^1.6.11: dependencies: sax "^1.2.4" -xtend@^4.0.0, xtend@^4.0.1: - version "4.0.2" - resolved "https://registry.npmjs.org/xtend/-/xtend-4.0.2.tgz" - integrity sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ== - yallist@^2.1.2: version "2.1.2" resolved "https://registry.npmjs.org/yallist/-/yallist-2.1.2.tgz" @@ -7916,7 +9711,7 @@ yallist@^4.0.0: resolved "https://registry.npmjs.org/yallist/-/yallist-4.0.0.tgz" integrity sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A== -yaml@^1.10.0, yaml@^1.10.2, yaml@^1.7.2, yaml@^2.2.2: +yaml@^1.7.2, yaml@^2.2.2: version "2.6.1" resolved "https://registry.yarnpkg.com/yaml/-/yaml-2.6.1.tgz#42f2b1ba89203f374609572d5349fb8686500773" integrity sha512-7r0XPzioN/Q9kXBro/XPnA6kznR73DHq+GXh5ON7ZozRO6aMjbmiBuKste2wslTFkC5d1dw0GooOCepZXJ2SAg== @@ -7955,7 +9750,7 @@ yocto-queue@^1.0.0: resolved "https://registry.npmjs.org/yocto-queue/-/yocto-queue-1.0.0.tgz" integrity sha512-9bnSc/HEW2uRy67wc+T8UwauLuPJVn28jb+GtJY16iiKWyvmYJRXVT4UamsAEGQfPohgr2q4Tq0sQbQlxTfi1g== -zwitch@^1.0.0: - version "1.0.5" - resolved "https://registry.npmjs.org/zwitch/-/zwitch-1.0.5.tgz" - integrity sha512-V50KMwwzqJV0NpZIZFwfOD5/lyny3WlSzRiXgA0G7VUnRlqttta1L6UQIHzd6EuBY/cHGfwTIck7w1yH6Q5zUw== +zwitch@^2.0.0: + version "2.0.4" + resolved "https://registry.yarnpkg.com/zwitch/-/zwitch-2.0.4.tgz#c827d4b0acb76fc3e685a4c6ec2902d51070e9d7" + integrity sha512-bXE4cR/kVZhKZX/RjPEflHaKVhUVl85noU3v6b8apfQEc1x4A+zBxjZ4lN8LqGd6WZ3dl98pY4o717VFmoPp+A== From ebd25fda81351c05986caa873a7ad107084ca92d Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 09:22:34 +0100 Subject: [PATCH 02/12] docs: fix import statements --- .../docs/cluster-management/managing-clusters-without-capi.mdx | 1 + website/docs/gitopssets/api-reference.mdx | 1 + website/docs/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../versioned_docs/version-0.20.0/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../versioned_docs/version-0.21.1/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../versioned_docs/version-0.21.2/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../versioned_docs/version-0.22.0/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../versioned_docs/version-0.23.0/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../versioned_docs/version-0.24.0/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../versioned_docs/version-0.25.0/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-existing-clusters.mdx | 1 + .../versioned_docs/version-0.26.0/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.27.0/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.28.0/gitopssets/api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../version-0.29.0/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.30.0/gitopssets/api-reference.mdx | 1 + .../version-0.30.0/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.31.2/gitopssets/api-reference.mdx | 1 + .../version-0.31.2/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.32.0/gitopssets/api-reference.mdx | 1 + .../version-0.32.0/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.33.0/gitopssets/api-reference.mdx | 1 + .../version-0.33.0/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.34.0/gitopssets/api-reference.mdx | 1 + .../version-0.34.0/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.35.0/gitopssets/api-reference.mdx | 1 + .../version-0.35.0/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.36.0/gitopssets/api-reference.mdx | 1 + .../version-0.36.0/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.37.0/gitopssets/api-reference.mdx | 1 + .../version-0.37.0/gitopssets/gitopssets-api-reference.mdx | 1 + .../cluster-management/managing-clusters-without-capi.mdx | 1 + .../versioned_docs/version-0.38.0/gitopssets/api-reference.mdx | 1 + .../version-0.38.0/gitopssets/gitopssets-api-reference.mdx | 1 + 56 files changed, 56 insertions(+) diff --git a/website/docs/cluster-management/managing-clusters-without-capi.mdx b/website/docs/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/docs/cluster-management/managing-clusters-without-capi.mdx +++ b/website/docs/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/docs/gitopssets/api-reference.mdx b/website/docs/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/docs/gitopssets/api-reference.mdx +++ b/website/docs/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/docs/gitopssets/gitopssets-api-reference.mdx b/website/docs/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/docs/gitopssets/gitopssets-api-reference.mdx +++ b/website/docs/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.16.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.16.0/cluster-management/managing-existing-clusters.mdx index 6499409b2a..79790c77e9 100644 --- a/website/versioned_docs/version-0.16.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.16.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.17.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.17.0/cluster-management/managing-existing-clusters.mdx index 695293152a..fe3a60b9fa 100644 --- a/website/versioned_docs/version-0.17.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.17.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.19.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.19.0/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.19.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.19.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.20.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.20.0/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.20.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.20.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.20.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.20.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.20.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.20.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.21.1/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.21.1/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.21.1/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.21.1/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.21.1/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.21.1/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.21.1/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.21.1/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.21.2/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.21.2/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.21.2/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.21.2/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.21.2/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.21.2/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.21.2/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.21.2/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.22.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.22.0/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.22.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.22.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.22.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.22.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.22.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.22.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.23.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.23.0/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.23.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.23.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.23.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.23.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.23.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.23.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.24.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.24.0/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.24.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.24.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.24.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.24.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.24.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.24.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.25.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.25.0/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.25.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.25.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.25.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.25.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.25.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.25.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.26.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.26.0/cluster-management/managing-existing-clusters.mdx index b40849670c..e9b44fa342 100644 --- a/website/versioned_docs/version-0.26.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.26.0/cluster-management/managing-existing-clusters.mdx @@ -15,6 +15,7 @@ import TierLabel from "../_components/TierLabel"; Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterprise. The only thing we need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.26.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.26.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.26.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.26.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.27.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.27.0/cluster-management/managing-clusters-without-capi.mdx index 2b872fbf46..8afa82d4e6 100644 --- a/website/versioned_docs/version-0.27.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.27.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave Gitops Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.27.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.27.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.27.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.27.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.28.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.28.0/cluster-management/managing-clusters-without-capi.mdx index 2b872fbf46..8afa82d4e6 100644 --- a/website/versioned_docs/version-0.28.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.28.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave Gitops Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.28.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.28.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.28.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.28.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.29.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.29.0/cluster-management/managing-clusters-without-capi.mdx index 2b872fbf46..8afa82d4e6 100644 --- a/website/versioned_docs/version-0.29.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.29.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave Gitops Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.29.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.29.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.29.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.29.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.30.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.30.0/cluster-management/managing-clusters-without-capi.mdx index 2e08b9738a..615790243b 100644 --- a/website/versioned_docs/version-0.30.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.30.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + ; diff --git a/website/versioned_docs/version-0.30.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.30.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.30.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.30.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.30.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.30.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.30.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.30.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.31.2/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.31.2/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/versioned_docs/version-0.31.2/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.31.2/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/versioned_docs/version-0.31.2/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.31.2/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.31.2/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.31.2/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.31.2/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.31.2/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.31.2/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.31.2/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.32.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.32.0/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/versioned_docs/version-0.32.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.32.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/versioned_docs/version-0.32.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.32.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.32.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.32.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.32.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.32.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.32.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.32.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.33.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.33.0/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/versioned_docs/version-0.33.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.33.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/versioned_docs/version-0.33.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.33.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.33.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.33.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.33.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.33.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.33.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.33.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.34.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.34.0/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/versioned_docs/version-0.34.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.34.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/versioned_docs/version-0.34.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.34.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.34.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.34.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.34.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.34.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.34.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.34.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.35.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.35.0/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/versioned_docs/version-0.35.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.35.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/versioned_docs/version-0.35.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.35.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.35.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.35.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.35.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.35.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.35.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.35.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.36.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.36.0/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/versioned_docs/version-0.36.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.36.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/versioned_docs/version-0.36.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.36.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.36.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.36.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.36.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.36.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.36.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.36.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.37.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.37.0/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/versioned_docs/version-0.37.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.37.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/versioned_docs/version-0.37.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.37.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.37.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.37.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.37.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.37.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.37.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.37.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.38.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.38.0/cluster-management/managing-clusters-without-capi.mdx index b3dba1c9b5..89a94bf05f 100644 --- a/website/versioned_docs/version-0.38.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.38.0/cluster-management/managing-clusters-without-capi.mdx @@ -15,6 +15,7 @@ import BrowserOnly from "@docusaurus/BrowserOnly"; You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps Enterprise. The only thing you need is a secret containing a valid `kubeconfig`. import TOCInline from "@theme/TOCInline"; + diff --git a/website/versioned_docs/version-0.38.0/gitopssets/api-reference.mdx b/website/versioned_docs/version-0.38.0/gitopssets/api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.38.0/gitopssets/api-reference.mdx +++ b/website/versioned_docs/version-0.38.0/gitopssets/api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; diff --git a/website/versioned_docs/version-0.38.0/gitopssets/gitopssets-api-reference.mdx b/website/versioned_docs/version-0.38.0/gitopssets/gitopssets-api-reference.mdx index 94c3b31de6..6063455537 100644 --- a/website/versioned_docs/version-0.38.0/gitopssets/gitopssets-api-reference.mdx +++ b/website/versioned_docs/version-0.38.0/gitopssets/gitopssets-api-reference.mdx @@ -5,6 +5,7 @@ hide_title: true import GeneratedAPI from './_api.mdx'; import apiToc from './_api-toc.json'; + export const toc = apiToc; From 15cb389fc16c9560ed26f184001b6f3c59a9fcb2 Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 09:59:21 +0100 Subject: [PATCH 03/12] docs: fix code blocks --- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 12 +++++++++--- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 12 +++++++++--- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 12 +++++++++--- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 12 +++++++++--- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 12 +++++++++--- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 4 +++- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 12 +++++++++--- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- .../cli-reference/gitops_completion_bash.md | 12 +++++++++--- .../cli-reference/gitops_completion_zsh.md | 16 ++++++++++++---- 50 files changed, 501 insertions(+), 167 deletions(-) diff --git a/website/docs/references/cli-reference/gitops_completion_bash.md b/website/docs/references/cli-reference/gitops_completion_bash.md index da1751d6ad..0085b9c107 100644 --- a/website/docs/references/cli-reference/gitops_completion_bash.md +++ b/website/docs/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/docs/references/cli-reference/gitops_completion_zsh.md b/website/docs/references/cli-reference/gitops_completion_zsh.md index 8dc779b228..d623de5343 100644 --- a/website/docs/references/cli-reference/gitops_completion_zsh.md +++ b/website/docs/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.16.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.16.0/references/cli-reference/gitops_completion_bash.md index f4de4e9fe8..86c4bbacf7 100644 --- a/website/versioned_docs/version-0.16.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.16.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.16.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.16.0/references/cli-reference/gitops_completion_zsh.md index b3144d87dd..455d85f793 100644 --- a/website/versioned_docs/version-0.16.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.16.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.17.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.17.0/references/cli-reference/gitops_completion_bash.md index 750530cd22..9daee0ff0d 100644 --- a/website/versioned_docs/version-0.17.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.17.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.17.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.17.0/references/cli-reference/gitops_completion_zsh.md index 01f2554fa8..538ddee5fc 100644 --- a/website/versioned_docs/version-0.17.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.17.0/references/cli-reference/gitops_completion_zsh.md @@ -13,17 +13,23 @@ to enable it. You can execute the following once: To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.18.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.18.0/references/cli-reference/gitops_completion_bash.md index ffc797e14e..e5e0f35b86 100644 --- a/website/versioned_docs/version-0.18.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.18.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.18.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.18.0/references/cli-reference/gitops_completion_zsh.md index d6e2c9df10..e52541cedd 100644 --- a/website/versioned_docs/version-0.18.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.18.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.19.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.19.0/references/cli-reference/gitops_completion_bash.md index 9ec4880d5d..6e721c186c 100644 --- a/website/versioned_docs/version-0.19.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.19.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.19.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.19.0/references/cli-reference/gitops_completion_zsh.md index 85426afc3f..40e9635032 100644 --- a/website/versioned_docs/version-0.19.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.19.0/references/cli-reference/gitops_completion_zsh.md @@ -13,17 +13,23 @@ to enable it. You can execute the following once: To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.20.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.20.0/references/cli-reference/gitops_completion_bash.md index d0ae1778bf..07e5cb360d 100644 --- a/website/versioned_docs/version-0.20.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.20.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.20.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.20.0/references/cli-reference/gitops_completion_zsh.md index f345816d99..64ad8471f3 100644 --- a/website/versioned_docs/version-0.20.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.20.0/references/cli-reference/gitops_completion_zsh.md @@ -13,17 +13,23 @@ to enable it. You can execute the following once: To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.21.1/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.21.1/references/cli-reference/gitops_completion_bash.md index 177aae204e..335cb3bc80 100644 --- a/website/versioned_docs/version-0.21.1/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.21.1/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.21.1/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.21.1/references/cli-reference/gitops_completion_zsh.md index 38080a7ee1..50614aa34a 100644 --- a/website/versioned_docs/version-0.21.1/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.21.1/references/cli-reference/gitops_completion_zsh.md @@ -13,17 +13,23 @@ to enable it. You can execute the following once: To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.21.2/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.21.2/references/cli-reference/gitops_completion_bash.md index 36903a3729..db91af2e3e 100644 --- a/website/versioned_docs/version-0.21.2/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.21.2/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.21.2/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.21.2/references/cli-reference/gitops_completion_zsh.md index ea8d805554..e99bd19d14 100644 --- a/website/versioned_docs/version-0.21.2/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.21.2/references/cli-reference/gitops_completion_zsh.md @@ -13,17 +13,23 @@ to enable it. You can execute the following once: To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.22.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.22.0/references/cli-reference/gitops_completion_bash.md index c726f45690..b95694e149 100644 --- a/website/versioned_docs/version-0.22.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.22.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.22.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.22.0/references/cli-reference/gitops_completion_zsh.md index 712038dffd..865c4e0971 100644 --- a/website/versioned_docs/version-0.22.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.22.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.23.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.23.0/references/cli-reference/gitops_completion_bash.md index 3639679661..929bae5068 100644 --- a/website/versioned_docs/version-0.23.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.23.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.23.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.23.0/references/cli-reference/gitops_completion_zsh.md index a931c191ef..45360201fa 100644 --- a/website/versioned_docs/version-0.23.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.23.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.24.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.24.0/references/cli-reference/gitops_completion_bash.md index 94c861eacf..4eb841d353 100644 --- a/website/versioned_docs/version-0.24.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.24.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.24.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.24.0/references/cli-reference/gitops_completion_zsh.md index df6caa3920..b35caa2e31 100644 --- a/website/versioned_docs/version-0.24.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.24.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.25.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.25.0/references/cli-reference/gitops_completion_bash.md index 984c6c6e2a..ecd0f8c616 100644 --- a/website/versioned_docs/version-0.25.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.25.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.25.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.25.0/references/cli-reference/gitops_completion_zsh.md index 803504169f..1e56840351 100644 --- a/website/versioned_docs/version-0.25.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.25.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.26.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.26.0/references/cli-reference/gitops_completion_bash.md index 3b08787766..d70e55882b 100644 --- a/website/versioned_docs/version-0.26.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.26.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.26.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.26.0/references/cli-reference/gitops_completion_zsh.md index e99a6b8b17..be76db5864 100644 --- a/website/versioned_docs/version-0.26.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.26.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.27.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.27.0/references/cli-reference/gitops_completion_bash.md index ec0b3165fd..f9d6f4e211 100644 --- a/website/versioned_docs/version-0.27.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.27.0/references/cli-reference/gitops_completion_bash.md @@ -11,7 +11,9 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: diff --git a/website/versioned_docs/version-0.27.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.27.0/references/cli-reference/gitops_completion_zsh.md index dc14e81a9e..48df449d43 100644 --- a/website/versioned_docs/version-0.27.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.27.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.28.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.28.0/references/cli-reference/gitops_completion_bash.md index 66e6c0517f..148ec162a1 100644 --- a/website/versioned_docs/version-0.28.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.28.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.28.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.28.0/references/cli-reference/gitops_completion_zsh.md index dcb48caa57..36fbb20d7c 100644 --- a/website/versioned_docs/version-0.28.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.28.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh); compdef _gitops gitops +``` +source <(gitops completion zsh); compdef _gitops gitops +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.29.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.29.0/references/cli-reference/gitops_completion_bash.md index cf6d06d9ac..b955cef3cc 100644 --- a/website/versioned_docs/version-0.29.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.29.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.29.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.29.0/references/cli-reference/gitops_completion_zsh.md index 7aea8681fe..20f5e71070 100644 --- a/website/versioned_docs/version-0.29.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.29.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.30.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.30.0/references/cli-reference/gitops_completion_bash.md index b513e28aa6..dc4f008d49 100644 --- a/website/versioned_docs/version-0.30.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.30.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.30.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.30.0/references/cli-reference/gitops_completion_zsh.md index d51dfcd882..676ff7d58f 100644 --- a/website/versioned_docs/version-0.30.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.30.0/references/cli-reference/gitops_completion_zsh.md @@ -13,17 +13,23 @@ to enable it. You can execute the following once: To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.31.2/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.31.2/references/cli-reference/gitops_completion_bash.md index 56e9a2a69a..8bb45cb880 100644 --- a/website/versioned_docs/version-0.31.2/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.31.2/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.31.2/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.31.2/references/cli-reference/gitops_completion_zsh.md index c893092fea..bac0a5e1f7 100644 --- a/website/versioned_docs/version-0.31.2/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.31.2/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.32.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.32.0/references/cli-reference/gitops_completion_bash.md index 62d4ea68fb..6ebd9b82d5 100644 --- a/website/versioned_docs/version-0.32.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.32.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.32.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.32.0/references/cli-reference/gitops_completion_zsh.md index bc4451e258..9ca4c208aa 100644 --- a/website/versioned_docs/version-0.32.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.32.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.33.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.33.0/references/cli-reference/gitops_completion_bash.md index 307e4fce90..e4a10e143b 100644 --- a/website/versioned_docs/version-0.33.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.33.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.33.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.33.0/references/cli-reference/gitops_completion_zsh.md index d2db0202b7..1e50d09da3 100644 --- a/website/versioned_docs/version-0.33.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.33.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.34.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.34.0/references/cli-reference/gitops_completion_bash.md index 97b3973376..51a6adf2c1 100644 --- a/website/versioned_docs/version-0.34.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.34.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.34.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.34.0/references/cli-reference/gitops_completion_zsh.md index b2ca28951f..f199e2934a 100644 --- a/website/versioned_docs/version-0.34.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.34.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.35.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.35.0/references/cli-reference/gitops_completion_bash.md index 8dfad72875..2391208509 100644 --- a/website/versioned_docs/version-0.35.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.35.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.35.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.35.0/references/cli-reference/gitops_completion_zsh.md index 816c9e4df6..bba773946f 100644 --- a/website/versioned_docs/version-0.35.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.35.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.36.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.36.0/references/cli-reference/gitops_completion_bash.md index 8737de86f8..427e8f8610 100644 --- a/website/versioned_docs/version-0.36.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.36.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.36.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.36.0/references/cli-reference/gitops_completion_zsh.md index c84bb9c773..27df37e47d 100644 --- a/website/versioned_docs/version-0.36.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.36.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.37.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.37.0/references/cli-reference/gitops_completion_bash.md index 7e719fdeaa..4ff35ecbb8 100644 --- a/website/versioned_docs/version-0.37.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.37.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.37.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.37.0/references/cli-reference/gitops_completion_zsh.md index e4ed3ed5c7..6baf49fba6 100644 --- a/website/versioned_docs/version-0.37.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.37.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.38.0/references/cli-reference/gitops_completion_bash.md b/website/versioned_docs/version-0.38.0/references/cli-reference/gitops_completion_bash.md index da1751d6ad..0085b9c107 100644 --- a/website/versioned_docs/version-0.38.0/references/cli-reference/gitops_completion_bash.md +++ b/website/versioned_docs/version-0.38.0/references/cli-reference/gitops_completion_bash.md @@ -11,17 +11,23 @@ If it is not installed already, you can install it via your OS's package manager To load completions in your current shell session: - source <(gitops completion bash) +``` +source <(gitops completion bash) +``` To load completions for every new session, execute once: #### Linux: - gitops completion bash > /etc/bash_completion.d/gitops +``` +gitops completion bash > /etc/bash_completion.d/gitops +``` #### macOS: - gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` +gitops completion bash > $(brew --prefix)/etc/bash_completion.d/gitops +``` You will need to start a new shell for this setup to take effect. diff --git a/website/versioned_docs/version-0.38.0/references/cli-reference/gitops_completion_zsh.md b/website/versioned_docs/version-0.38.0/references/cli-reference/gitops_completion_zsh.md index 8dc779b228..d623de5343 100644 --- a/website/versioned_docs/version-0.38.0/references/cli-reference/gitops_completion_zsh.md +++ b/website/versioned_docs/version-0.38.0/references/cli-reference/gitops_completion_zsh.md @@ -9,21 +9,29 @@ Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: - echo "autoload -U compinit; compinit" >> ~/.zshrc +``` +echo "autoload -U compinit; compinit" >> ~/.zshrc +``` To load completions in your current shell session: - source <(gitops completion zsh) +``` +source <(gitops completion zsh) +``` To load completions for every new session, execute once: #### Linux: - gitops completion zsh > "${fpath[1]}/_gitops" +``` +gitops completion zsh > "${fpath[1]}/_gitops" +``` #### macOS: - gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` +gitops completion zsh > $(brew --prefix)/share/zsh/site-functions/_gitops +``` You will need to start a new shell for this setup to take effect. From 020938e15e9472310864fa9deb663640148ee6e7 Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 10:00:35 +0100 Subject: [PATCH 04/12] docs: fix raw links --- website/src/pages/security/index.md | 2 +- website/versioned_docs/version-0.16.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.17.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.18.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.19.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.20.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.21.1/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.21.2/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.22.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.23.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.24.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.25.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.26.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.27.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.28.0/guides/cert-manager.md | 2 +- website/versioned_docs/version-0.29.0/guides/cert-manager.md | 2 +- 16 files changed, 16 insertions(+), 16 deletions(-) diff --git a/website/src/pages/security/index.md b/website/src/pages/security/index.md index 0d87538817..2b6a48ca71 100644 --- a/website/src/pages/security/index.md +++ b/website/src/pages/security/index.md @@ -13,7 +13,7 @@ This document defines security reporting, handling, disclosure, and audit inform ### Report a Vulnerability -- To make a report please email the private security list at with the details. +- To make a report please email the private security list at [security@weaveworks.org](security@weaveworks.org) with the details. We ask that reporters act in good faith by not disclosing the issue to others. - Reported vulnerabilities are triaged by Weaveworks Security team. - Weaveworks Security team would acknowledge to the reporter for any valid request. diff --git a/website/versioned_docs/version-0.16.0/guides/cert-manager.md b/website/versioned_docs/version-0.16.0/guides/cert-manager.md index e1bdb523b0..cf61fc3243 100644 --- a/website/versioned_docs/version-0.16.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.16.0/guides/cert-manager.md @@ -63,7 +63,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.17.0/guides/cert-manager.md b/website/versioned_docs/version-0.17.0/guides/cert-manager.md index e1bdb523b0..cf61fc3243 100644 --- a/website/versioned_docs/version-0.17.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.17.0/guides/cert-manager.md @@ -63,7 +63,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.18.0/guides/cert-manager.md b/website/versioned_docs/version-0.18.0/guides/cert-manager.md index 286b575ff8..53bacf2d2a 100644 --- a/website/versioned_docs/version-0.18.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.18.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.19.0/guides/cert-manager.md b/website/versioned_docs/version-0.19.0/guides/cert-manager.md index 286b575ff8..53bacf2d2a 100644 --- a/website/versioned_docs/version-0.19.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.19.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.20.0/guides/cert-manager.md b/website/versioned_docs/version-0.20.0/guides/cert-manager.md index 286b575ff8..53bacf2d2a 100644 --- a/website/versioned_docs/version-0.20.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.20.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.21.1/guides/cert-manager.md b/website/versioned_docs/version-0.21.1/guides/cert-manager.md index 286b575ff8..53bacf2d2a 100644 --- a/website/versioned_docs/version-0.21.1/guides/cert-manager.md +++ b/website/versioned_docs/version-0.21.1/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.21.2/guides/cert-manager.md b/website/versioned_docs/version-0.21.2/guides/cert-manager.md index 286b575ff8..53bacf2d2a 100644 --- a/website/versioned_docs/version-0.21.2/guides/cert-manager.md +++ b/website/versioned_docs/version-0.21.2/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.22.0/guides/cert-manager.md b/website/versioned_docs/version-0.22.0/guides/cert-manager.md index 286b575ff8..53bacf2d2a 100644 --- a/website/versioned_docs/version-0.22.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.22.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.23.0/guides/cert-manager.md b/website/versioned_docs/version-0.23.0/guides/cert-manager.md index 286b575ff8..53bacf2d2a 100644 --- a/website/versioned_docs/version-0.23.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.23.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.24.0/guides/cert-manager.md b/website/versioned_docs/version-0.24.0/guides/cert-manager.md index 43011f1d32..31254548d1 100644 --- a/website/versioned_docs/version-0.24.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.24.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.25.0/guides/cert-manager.md b/website/versioned_docs/version-0.25.0/guides/cert-manager.md index 55374522f1..8640eeebea 100644 --- a/website/versioned_docs/version-0.25.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.25.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.26.0/guides/cert-manager.md b/website/versioned_docs/version-0.26.0/guides/cert-manager.md index 55374522f1..8640eeebea 100644 --- a/website/versioned_docs/version-0.26.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.26.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.27.0/guides/cert-manager.md b/website/versioned_docs/version-0.27.0/guides/cert-manager.md index 55374522f1..8640eeebea 100644 --- a/website/versioned_docs/version-0.27.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.27.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.28.0/guides/cert-manager.md b/website/versioned_docs/version-0.28.0/guides/cert-manager.md index 40aa760de3..e2966482ac 100644 --- a/website/versioned_docs/version-0.28.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.28.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority diff --git a/website/versioned_docs/version-0.29.0/guides/cert-manager.md b/website/versioned_docs/version-0.29.0/guides/cert-manager.md index 3317b926a6..af4764423b 100644 --- a/website/versioned_docs/version-0.29.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.29.0/guides/cert-manager.md @@ -67,7 +67,7 @@ spec: :::note cert-manager version At time of writing, cert manager v1.8.0 was the latest available release and a newer version may exist, please -ensure to check for updates. +ensure to check [https://github.com/cert-manager/cert-manager/tags](https://github.com/cert-manager/cert-manager/tags) for updates. ::: Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent the certificate authority From 6d17a8e70da8acd4e3e2a3d7b53f075356ca7270 Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 10:05:04 +0100 Subject: [PATCH 05/12] docs: fix details/summary --- website/README.md | 6 +++-- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- website/docs/explorer/configuration.mdx | 12 ++++++---- website/docs/gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../guides/configuring-oidc-with-keycloak.mdx | 6 +++-- website/docs/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../getting-started/install-OSS.mdx | 3 ++- website/docs/operations/monitoring.mdx | 6 +++-- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../docs/pipelines/pipelines-templates.mdx | 9 ++++--- .../docs/pipelines/pipelines-with-jenkins.mdx | 3 ++- .../docs/pipelines/promoting-applications.mdx | 18 +++++++++----- website/docs/policy/commit-time-checks.mdx | 3 ++- website/docs/policy/getting-started.mdx | 9 ++++--- website/docs/policy/policy-configuration.mdx | 6 +++-- website/docs/policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 24 ++++++++++++------- .../docs/secrets/bootstrapping-secrets.mdx | 6 +++-- website/docs/secrets/getting-started.mdx | 6 +++-- website/docs/secrets/setup-eso.mdx | 6 +++-- website/docs/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- website/docs/workspaces/multi-tenancy.mdx | 12 ++++++---- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../version-0.18.0/getting-started/deploy.mdx | 3 ++- .../version-0.18.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/templates.mdx | 3 ++- .../gitopssets/_rbac_warning.mdx | 3 ++- .../version-0.18.0/guides/cert-manager.md | 6 +++-- .../version-0.18.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.18.0/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../installation/aws-marketplace.mdx | 6 +++-- .../weave-gitops-enterprise/airgap.mdx | 18 +++++++++----- .../weave-gitops-enterprise/index.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/policy-configuration.mdx | 6 +++-- .../version-0.18.0/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../version-0.19.0/getting-started/deploy.mdx | 3 ++- .../version-0.19.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../gitopssets/_rbac_warning.mdx | 3 ++- .../version-0.19.0/guides/cert-manager.md | 6 +++-- .../version-0.19.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.19.0/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../installation/aws-marketplace.mdx | 6 +++-- .../weave-gitops-enterprise/airgap.mdx | 18 +++++++++----- .../weave-gitops-enterprise/index.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.19.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../version-0.19.0/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../version-0.20.0/getting-started/deploy.mdx | 3 ++- .../version-0.20.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.20.0/guides/cert-manager.md | 6 +++-- .../version-0.20.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.20.0/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../installation/aws-marketplace.mdx | 6 +++-- .../weave-gitops-enterprise/airgap.mdx | 18 +++++++++----- .../weave-gitops-enterprise/index.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.20.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstraping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.20.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.20.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../version-0.20.0/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../version-0.21.1/getting-started/deploy.mdx | 3 ++- .../version-0.21.1/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.21.1/guides/cert-manager.md | 6 +++-- .../version-0.21.1/guides/delivery.mdx | 18 +++++++++----- .../version-0.21.1/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../installation/aws-marketplace.mdx | 6 +++-- .../weave-gitops-enterprise/airgap.mdx | 18 +++++++++----- .../weave-gitops-enterprise/index.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.21.1/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstraping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.21.1/secrets/setup-eso.mdx | 6 +++-- .../version-0.21.1/secrets/setup-sops.mdx | 21 ++++++++++------ .../version-0.21.1/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../version-0.21.2/getting-started/deploy.mdx | 3 ++- .../version-0.21.2/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.21.2/guides/cert-manager.md | 6 +++-- .../version-0.21.2/guides/delivery.mdx | 18 +++++++++----- .../version-0.21.2/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../installation/aws-marketplace.mdx | 6 +++-- .../weave-gitops-enterprise/airgap.mdx | 18 +++++++++----- .../weave-gitops-enterprise/index.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.21.2/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstraping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.21.2/secrets/setup-eso.mdx | 6 +++-- .../version-0.21.2/secrets/setup-sops.mdx | 21 ++++++++++------ .../version-0.21.2/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../version-0.22.0/explorer/configuration.mdx | 12 ++++++---- .../version-0.22.0/getting-started/deploy.mdx | 3 ++- .../version-0.22.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.22.0/guides/cert-manager.md | 6 +++-- .../version-0.22.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.22.0/guides/fluxga-upgrade.mdx | 3 ++- .../version-0.22.0/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../installation/aws-marketplace.mdx | 6 +++-- .../weave-gitops-enterprise/airgap.mdx | 18 +++++++++----- .../weave-gitops-enterprise/index.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.22.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstraping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.22.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.22.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../version-0.22.0/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../version-0.23.0/explorer/configuration.mdx | 12 ++++++---- .../version-0.23.0/getting-started/deploy.mdx | 3 ++- .../version-0.23.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.23.0/guides/cert-manager.md | 6 +++-- .../version-0.23.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.23.0/guides/fluxga-upgrade.mdx | 3 ++- .../version-0.23.0/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../installation/aws-marketplace.mdx | 6 +++-- .../weave-gitops-enterprise/airgap.mdx | 18 +++++++++----- .../weave-gitops-enterprise/index.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.23.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstraping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.23.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.23.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../version-0.23.0/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../getting-started/aws-marketplace.mdx | 6 +++-- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 3 ++- .../version-0.24.0/explorer/configuration.mdx | 12 ++++++---- .../version-0.24.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.24.0/guides/cert-manager.md | 6 +++-- .../version-0.24.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.24.0/guides/fluxga-upgrade.mdx | 3 ++- .../version-0.24.0/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.24.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstraping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.24.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.24.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../version-0.24.0/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../getting-started/aws-marketplace.mdx | 6 +++-- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 3 ++- .../version-0.25.0/explorer/configuration.mdx | 12 ++++++---- .../version-0.25.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.25.0/guides/cert-manager.md | 6 +++-- .../version-0.25.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.25.0/guides/fluxga-upgrade.mdx | 3 ++- .../version-0.25.0/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.25.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstraping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.25.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.25.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../version-0.25.0/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/getting-started.mdx | 9 ++++--- .../managing-existing-clusters.mdx | 9 ++++--- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../getting-started/aws-marketplace.mdx | 6 +++-- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 3 ++- .../version-0.26.0/explorer/configuration.mdx | 12 ++++++---- .../version-0.26.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.26.0/guides/cert-manager.md | 6 +++-- .../version-0.26.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.26.0/guides/fluxga-upgrade.mdx | 3 ++- .../version-0.26.0/guides/setting-up-dex.md | 9 ++++--- .../guides/using-terraform-templates.mdx | 9 ++++--- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.26.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstraping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.26.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.26.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../version-0.26.0/terraform/oci-artifact.mdx | 3 ++- .../using-terraform-cr/custom-backend.mdx | 3 ++- .../using-terraform-cr/customize-runner.mdx | 6 +++-- .../using-terraform-cr/depends-on.mdx | 6 +++-- .../terraform/using-terraform-cr/modules.mdx | 3 ++- .../set-variables-for-trraform-resources.mdx | 6 +++-- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 3 ++- .../version-0.27.0/explorer/configuration.mdx | 12 ++++++---- .../version-0.27.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.27.0/guides/cert-manager.md | 6 +++-- .../version-0.27.0/guides/delivery.mdx | 18 +++++++++----- .../version-0.27.0/guides/fluxga-upgrade.mdx | 3 ++- .../version-0.27.0/guides/setting-up-dex.md | 9 ++++--- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.27.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.27.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.27.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 3 ++- .../version-0.28.0/explorer/configuration.mdx | 12 ++++++---- .../version-0.28.0/gitops-run/get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.28.0/guides/cert-manager.md | 6 +++-- .../version-0.28.0/guides/fluxga-upgrade.mdx | 3 ++- .../version-0.28.0/guides/setting-up-dex.md | 9 ++++--- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/getting-started.mdx | 3 ++- .../pipelines/pipeline-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 21 ++++++++++------ .../policy/commit-time-checks.mdx | 3 ++- .../version-0.28.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 18 +++++++++----- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.28.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.28.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../recommended-rbac-configuration.mdx | 3 ++- .../configuration/user-permissions.mdx | 6 +++-- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 3 ++- .../version-0.29.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-run/gitops-run-get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.29.0/guides/cert-manager.md | 6 +++-- .../version-0.29.0/guides/fluxga-upgrade.mdx | 3 ++- .../version-0.29.0/guides/setting-up-dex.md | 9 ++++--- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.29.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 18 +++++++++----- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.29.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.29.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../version-0.30.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-run/gitops-run-get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.30.0/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.30.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 18 +++++++++----- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.30.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.30.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- .../version-0.31.2/explorer/configuration.mdx | 12 ++++++---- .../gitops-run/gitops-run-get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.31.2/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.31.2/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 18 +++++++++----- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.31.2/secrets/setup-eso.mdx | 6 +++-- .../version-0.31.2/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- .../version-0.32.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-run/gitops-run-get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.32.0/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.32.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 24 ++++++++++++------- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.32.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.32.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- .../version-0.33.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-run/gitops-run-get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.33.0/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.33.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 24 ++++++++++++------- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.33.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.33.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- .../version-0.34.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.34.0/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../version-0.34.0/operations/monitoring.mdx | 9 ++++--- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.34.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 24 ++++++++++++------- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.34.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.34.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- .../version-0.35.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-run/gitops-run-get-started.mdx | 9 ++++--- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.35.0/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../version-0.35.0/operations/monitoring.mdx | 6 +++-- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.35.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 24 ++++++++++++------- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.35.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.35.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- .../version-0.36.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../version-0.36.0/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../version-0.36.0/operations/monitoring.mdx | 6 +++-- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.36.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 24 ++++++++++++------- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.36.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.36.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- .../version-0.37.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../guides/configuring-oidc-with-keycloak.mdx | 6 +++-- .../version-0.37.0/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../version-0.37.0/operations/monitoring.mdx | 6 +++-- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.37.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 24 ++++++++++++------- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.37.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.37.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- .../cluster-management/deploying-capa-eks.mdx | 6 +++-- .../managing-clusters-without-capi.mdx | 15 ++++++++---- .../install-enterprise-airgap.mdx | 18 +++++++++----- .../getting-started/install-enterprise.mdx | 15 ++++++++---- .../join-cluster-azure-flux.mdx | 9 ++++--- .../version-0.38.0/explorer/configuration.mdx | 12 ++++++---- .../gitops-templates/profiles.mdx | 3 ++- .../gitops-templates/quickstart-templates.mdx | 3 ++- .../gitops-templates/repo-rendered-paths.mdx | 3 ++- .../guides/configuring-oidc-with-keycloak.mdx | 6 +++-- .../version-0.38.0/guides/fluxga-upgrade.mdx | 3 ++- .../getting-started/aws-marketplace.mdx | 6 +++-- .../getting-started/deploy-OSS.mdx | 3 ++- .../version-0.38.0/operations/monitoring.mdx | 6 +++-- .../pipelines/pipelines-getting-started.mdx | 3 ++- .../pipelines/pipelines-templates.mdx | 9 ++++--- .../pipelines/pipelines-with-jenkins.mdx | 3 ++- .../pipelines/promoting-applications.mdx | 18 +++++++++----- .../policy/commit-time-checks.mdx | 3 ++- .../version-0.38.0/policy/getting-started.mdx | 9 ++++--- .../policy/policy-configuration.mdx | 6 +++-- .../policy/weave-policy-profile.mdx | 3 ++- .../progressive-delivery-flagger-install.mdx | 24 ++++++++++++------- .../secrets/bootstrapping-secrets.mdx | 6 +++-- .../secrets/getting-started.mdx | 6 +++-- .../version-0.38.0/secrets/setup-eso.mdx | 6 +++-- .../version-0.38.0/secrets/setup-sops.mdx | 21 ++++++++++------ .../terraform/using-terraform-templates.mdx | 9 ++++--- .../workspaces/multi-tenancy.mdx | 12 ++++++---- 727 files changed, 3768 insertions(+), 1884 deletions(-) diff --git a/website/README.md b/website/README.md index fa26437af6..56ec4d11cb 100644 --- a/website/README.md +++ b/website/README.md @@ -128,7 +128,8 @@ Smaller chunks are usually fine. But for anything more that 10 lines it is neater to wrap it. ~~~markdown -
Expand to see this awesome HelmRepository +
+Expand to see this awesome HelmRepository Don't forget to leave a line break below the opening tag... ```yaml @@ -141,7 +142,8 @@ and before the closing one.
~~~ -
Expand to see this awesome HelmRepository +
+Expand to see this awesome HelmRepository Don't forget to leave a line break below the opening tag... ``` diff --git a/website/docs/cluster-management/deploying-capa-eks.mdx b/website/docs/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/docs/cluster-management/deploying-capa-eks.mdx +++ b/website/docs/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/docs/enterprise/getting-started/install-enterprise-airgap.mdx b/website/docs/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/docs/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/docs/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/docs/enterprise/getting-started/install-enterprise.mdx b/website/docs/enterprise/getting-started/install-enterprise.mdx index e0130f121a..4bbb072598 100644 --- a/website/docs/enterprise/getting-started/install-enterprise.mdx +++ b/website/docs/enterprise/getting-started/install-enterprise.mdx @@ -256,7 +256,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -368,7 +369,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -416,7 +418,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -792,7 +795,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1057,7 +1061,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/docs/explorer/configuration.mdx b/website/docs/explorer/configuration.mdx index 9bfad80a52..8cf7706c3e 100644 --- a/website/docs/explorer/configuration.mdx +++ b/website/docs/explorer/configuration.mdx @@ -114,7 +114,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -129,7 +130,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -158,7 +160,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -181,7 +184,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/docs/gitops-templates/profiles.mdx b/website/docs/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/docs/gitops-templates/profiles.mdx +++ b/website/docs/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/docs/gitops-templates/quickstart-templates.mdx b/website/docs/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/docs/gitops-templates/quickstart-templates.mdx +++ b/website/docs/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/docs/gitops-templates/repo-rendered-paths.mdx b/website/docs/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/docs/gitops-templates/repo-rendered-paths.mdx +++ b/website/docs/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/docs/guides/configuring-oidc-with-keycloak.mdx b/website/docs/guides/configuring-oidc-with-keycloak.mdx index b3ba33f739..afddb7cacb 100644 --- a/website/docs/guides/configuring-oidc-with-keycloak.mdx +++ b/website/docs/guides/configuring-oidc-with-keycloak.mdx @@ -193,7 +193,8 @@ To configure Weave GitOps for OIDC authentication via Keycloak, we need to confi - the `claimGroups` to `groups` to work with our mapper, mapping from roles->groups - the `claimUsername` to `sub` -
Expand to see secret definition +
+Expand to see secret definition ```yaml apiVersion: v1 @@ -221,7 +222,8 @@ The following example assumes that the ClusterRole `wego-admin-cluster-role` and in the `wego-admin` group within Keycloak admin access. See the [recommendations on setting up RBAC](../../enterprise/getting-started/install-enterprise/#recommended-rbac-configuration) for details. -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- diff --git a/website/docs/guides/fluxga-upgrade.mdx b/website/docs/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/docs/guides/fluxga-upgrade.mdx +++ b/website/docs/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/docs/open-source/getting-started/aws-marketplace.mdx b/website/docs/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/docs/open-source/getting-started/aws-marketplace.mdx +++ b/website/docs/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/docs/open-source/getting-started/deploy-OSS.mdx b/website/docs/open-source/getting-started/deploy-OSS.mdx index 8997f2a22b..6f6acf2771 100644 --- a/website/docs/open-source/getting-started/deploy-OSS.mdx +++ b/website/docs/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/docs/open-source/getting-started/install-OSS.mdx b/website/docs/open-source/getting-started/install-OSS.mdx index 062eefceae..399efddfc8 100644 --- a/website/docs/open-source/getting-started/install-OSS.mdx +++ b/website/docs/open-source/getting-started/install-OSS.mdx @@ -236,7 +236,8 @@ You could optionally unlock more from Weave GitOps by installing other component 2. Leverage [Flux Post-Rendering](https://fluxcd.io/flux/components/helm/helmreleases/#post-renderers) to label Deployments and CRDs with `app.kubernetes.io/part-of: weave-gitops` -
Expand to see a simplified example for TF-controller +
+Expand to see a simplified example for TF-controller ```yaml apiVersion: helm.toolkit.fluxcd.io/v2beta2 diff --git a/website/docs/operations/monitoring.mdx b/website/docs/operations/monitoring.mdx index 5275110618..87a1d0b273 100644 --- a/website/docs/operations/monitoring.mdx +++ b/website/docs/operations/monitoring.mdx @@ -46,7 +46,8 @@ This setup follows the same [monitoring approach as Flux](https://fluxcd.io/flux 1. [Enable](#setup) the monitoring server with the metrics endpoint. 2. Install [Kube Prometheus Stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack). -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1 @@ -85,7 +86,8 @@ spec: 3. Deploy Weave GitOps Monitoring Config -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1 diff --git a/website/docs/pipelines/pipelines-getting-started.mdx b/website/docs/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/docs/pipelines/pipelines-getting-started.mdx +++ b/website/docs/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/docs/pipelines/pipelines-templates.mdx b/website/docs/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/docs/pipelines/pipelines-templates.mdx +++ b/website/docs/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/docs/pipelines/pipelines-with-jenkins.mdx b/website/docs/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/docs/pipelines/pipelines-with-jenkins.mdx +++ b/website/docs/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/docs/pipelines/promoting-applications.mdx b/website/docs/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/docs/pipelines/promoting-applications.mdx +++ b/website/docs/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/docs/policy/commit-time-checks.mdx b/website/docs/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/docs/policy/commit-time-checks.mdx +++ b/website/docs/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/docs/policy/getting-started.mdx b/website/docs/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/docs/policy/getting-started.mdx +++ b/website/docs/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/docs/policy/policy-configuration.mdx b/website/docs/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/docs/policy/policy-configuration.mdx +++ b/website/docs/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/docs/policy/weave-policy-profile.mdx b/website/docs/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/docs/policy/weave-policy-profile.mdx +++ b/website/docs/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/docs/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/docs/progressive-delivery/progressive-delivery-flagger-install.mdx index f0b866be90..5f80d3413d 100644 --- a/website/docs/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/docs/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -82,7 +82,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -172,7 +173,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -265,7 +267,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -330,7 +333,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -394,7 +398,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -438,7 +443,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -533,7 +539,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -717,7 +724,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/docs/secrets/bootstrapping-secrets.mdx b/website/docs/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/docs/secrets/bootstrapping-secrets.mdx +++ b/website/docs/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/docs/secrets/getting-started.mdx b/website/docs/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/docs/secrets/getting-started.mdx +++ b/website/docs/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/docs/secrets/setup-eso.mdx b/website/docs/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/docs/secrets/setup-eso.mdx +++ b/website/docs/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/docs/secrets/setup-sops.mdx b/website/docs/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/docs/secrets/setup-sops.mdx +++ b/website/docs/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/docs/terraform/using-terraform-templates.mdx b/website/docs/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/docs/terraform/using-terraform-templates.mdx +++ b/website/docs/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/docs/workspaces/multi-tenancy.mdx b/website/docs/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/docs/workspaces/multi-tenancy.mdx +++ b/website/docs/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx index e9b44fa342..d284ddd8ed 100644 --- a/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx @@ -47,7 +47,8 @@ kubectl create secret generic demo-01-kubeconfig \ 1. Add RBAC permissions for the service account -
Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.18.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.18.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.18.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.18.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.18.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.18.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.18.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.18.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.18.0/getting-started/deploy.mdx b/website/versioned_docs/version-0.18.0/getting-started/deploy.mdx index d4d4e6ac6f..f8db3af96b 100644 --- a/website/versioned_docs/version-0.18.0/getting-started/deploy.mdx +++ b/website/versioned_docs/version-0.18.0/getting-started/deploy.mdx @@ -79,7 +79,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.18.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.18.0/gitops-run/get-started.mdx index 3d7afb8b10..9e04ecc4b4 100644 --- a/website/versioned_docs/version-0.18.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.18.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.18.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.18.0/gitops-templates/quickstart-templates.mdx index 6e66e53d6f..0648f23a21 100644 --- a/website/versioned_docs/version-0.18.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.18.0/gitops-templates/quickstart-templates.mdx @@ -19,7 +19,8 @@ github repo. To get started, just check the helm release in your weave gitops enterprise configuration repo for your management cluster to deploy. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.18.0/gitops-templates/templates.mdx b/website/versioned_docs/version-0.18.0/gitops-templates/templates.mdx index 662e5a56be..702f6e5e6f 100644 --- a/website/versioned_docs/version-0.18.0/gitops-templates/templates.mdx +++ b/website/versioned_docs/version-0.18.0/gitops-templates/templates.mdx @@ -412,7 +412,8 @@ This example works with the CAPD provider, see [Cluster API Providers](../cluste import CodeBlock from "@theme/CodeBlock"; import CapdTemplate from "!!raw-loader!../assets/templates/capd-template.yaml"; -
Expand to view +
+Expand to view Expand to see SA resources +
+Expand to see SA resources ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.18.0/guides/cert-manager.md b/website/versioned_docs/version-0.18.0/guides/cert-manager.md index 53bacf2d2a..279e557062 100644 --- a/website/versioned_docs/version-0.18.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.18.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.18.0/guides/delivery.mdx b/website/versioned_docs/version-0.18.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.18.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.18.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.18.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.18.0/guides/setting-up-dex.md index 00d92922fb..20a272be15 100644 --- a/website/versioned_docs/version-0.18.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.18.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.18.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.18.0/guides/using-terraform-templates.mdx index 498921bd16..fe20138104 100644 --- a/website/versioned_docs/version-0.18.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.18.0/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](installation/weave-gitops-enterprise/index.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.18.0/installation/aws-marketplace.mdx b/website/versioned_docs/version-0.18.0/installation/aws-marketplace.mdx index 929b1910b8..2421ffbb20 100644 --- a/website/versioned_docs/version-0.18.0/installation/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.18.0/installation/aws-marketplace.mdx @@ -33,7 +33,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -89,7 +90,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/airgap.mdx b/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/airgap.mdx index d51c6fe148..89473630d4 100644 --- a/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/airgap.mdx +++ b/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/airgap.mdx @@ -81,7 +81,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -191,7 +192,8 @@ EOF ``` Execute `make` using the following makefile to intialise capi in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -238,7 +240,8 @@ capi-cluster: Apply the following example manifest to deploy the terraform controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -279,7 +282,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -423,7 +427,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. The following Makefile is supplied to help you with each stage. -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -495,7 +500,8 @@ with the following considerations: An example of how it would look like for Weave Gitops Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx index 0345ae8881..1a2a22e0b8 100644 --- a/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx @@ -308,7 +308,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx index 81920dc052..9fab5a69c8 100644 --- a/website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx @@ -46,7 +46,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -120,7 +121,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -230,7 +232,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.18.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.18.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.18.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.18.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.18.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.18.0/pipelines/promoting-applications.mdx index 5b77cfe8dd..3683037739 100644 --- a/website/versioned_docs/version-0.18.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.18.0/pipelines/promoting-applications.mdx @@ -180,7 +180,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -234,7 +235,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -242,7 +244,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -279,14 +282,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -296,7 +301,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -405,7 +411,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.18.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.18.0/policy/policy-configuration.mdx index d2607d0179..03d8dc7afc 100644 --- a/website/versioned_docs/version-0.18.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.18.0/policy/policy-configuration.mdx @@ -87,7 +87,8 @@ A new `PolicyConfig` CRD allows using policies with multiple configurations by c We have Kustomization application `app-a` and deployment `deployment-1` part of this application -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 @@ -272,7 +273,8 @@ spec: :::note You can use one or more policies as the following example: -
Expand to see policy example +
+ Expand to see policy example ```yaml --- diff --git a/website/versioned_docs/version-0.18.0/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.18.0/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.18.0/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.18.0/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.18.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.18.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.18.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.18.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.19.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.19.0/cluster-management/getting-started.mdx index 911a403b09..50292acfc2 100644 --- a/website/versioned_docs/version-0.19.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.19.0/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.19.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.19.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.19.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.19.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.19.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.19.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.19.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.19.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.19.0/getting-started/deploy.mdx b/website/versioned_docs/version-0.19.0/getting-started/deploy.mdx index d4d4e6ac6f..f8db3af96b 100644 --- a/website/versioned_docs/version-0.19.0/getting-started/deploy.mdx +++ b/website/versioned_docs/version-0.19.0/getting-started/deploy.mdx @@ -79,7 +79,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.19.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.19.0/gitops-run/get-started.mdx index 3d7afb8b10..9e04ecc4b4 100644 --- a/website/versioned_docs/version-0.19.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.19.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.19.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.19.0/gitops-templates/profiles.mdx index a7ffd6a6c8..3c301d8e84 100644 --- a/website/versioned_docs/version-0.19.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.19.0/gitops-templates/profiles.mdx @@ -43,7 +43,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile| | `editable` | (default=false) Allow the user to edit the values.yaml of this profile| -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.19.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.19.0/gitops-templates/quickstart-templates.mdx index ea32317412..645955f8b4 100644 --- a/website/versioned_docs/version-0.19.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.19.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.19.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.19.0/gitops-templates/repo-rendered-paths.mdx index 28fbf8c5b8..f1a96dbaf2 100644 --- a/website/versioned_docs/version-0.19.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.19.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.19.0/gitopssets/_rbac_warning.mdx b/website/versioned_docs/version-0.19.0/gitopssets/_rbac_warning.mdx index d1c4d943d3..b55b2cd86d 100644 --- a/website/versioned_docs/version-0.19.0/gitopssets/_rbac_warning.mdx +++ b/website/versioned_docs/version-0.19.0/gitopssets/_rbac_warning.mdx @@ -14,7 +14,8 @@ for each `GitOpsSet` that has the required permissions for creating the rendered Additional RBAC for the `gitopssets-controller-manager` service account: -
Expand to see SA resources +
+Expand to see SA resources ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.19.0/guides/cert-manager.md b/website/versioned_docs/version-0.19.0/guides/cert-manager.md index 53bacf2d2a..279e557062 100644 --- a/website/versioned_docs/version-0.19.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.19.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.19.0/guides/delivery.mdx b/website/versioned_docs/version-0.19.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.19.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.19.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.19.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.19.0/guides/setting-up-dex.md index 00d92922fb..20a272be15 100644 --- a/website/versioned_docs/version-0.19.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.19.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.19.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.19.0/guides/using-terraform-templates.mdx index 498921bd16..fe20138104 100644 --- a/website/versioned_docs/version-0.19.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.19.0/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](installation/weave-gitops-enterprise/index.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.19.0/installation/aws-marketplace.mdx b/website/versioned_docs/version-0.19.0/installation/aws-marketplace.mdx index 929b1910b8..2421ffbb20 100644 --- a/website/versioned_docs/version-0.19.0/installation/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.19.0/installation/aws-marketplace.mdx @@ -33,7 +33,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -89,7 +90,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/airgap.mdx b/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/airgap.mdx index d51c6fe148..89473630d4 100644 --- a/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/airgap.mdx +++ b/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/airgap.mdx @@ -81,7 +81,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -191,7 +192,8 @@ EOF ``` Execute `make` using the following makefile to intialise capi in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -238,7 +240,8 @@ capi-cluster: Apply the following example manifest to deploy the terraform controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -279,7 +282,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -423,7 +427,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. The following Makefile is supplied to help you with each stage. -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -495,7 +500,8 @@ with the following considerations: An example of how it would look like for Weave Gitops Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx index ff7500a38a..3e5bf10e99 100644 --- a/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx @@ -308,7 +308,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx index c83213b281..b86aaa7481 100644 --- a/website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.19.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.19.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.19.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.19.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.19.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.19.0/pipelines/promoting-applications.mdx index 5b77cfe8dd..3683037739 100644 --- a/website/versioned_docs/version-0.19.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.19.0/pipelines/promoting-applications.mdx @@ -180,7 +180,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -234,7 +235,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -242,7 +244,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -279,14 +282,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -296,7 +301,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -405,7 +411,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.19.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.19.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.19.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.19.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.19.0/policy/getting-started.mdx b/website/versioned_docs/version-0.19.0/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.19.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.19.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.19.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.19.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.19.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.19.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.19.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.19.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.19.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.19.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.19.0/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.19.0/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.19.0/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.19.0/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.19.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.19.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.19.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.19.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.20.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.20.0/cluster-management/getting-started.mdx index 785684efb7..d87a9cdff9 100644 --- a/website/versioned_docs/version-0.20.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.20.0/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.20.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.20.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.20.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.20.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.20.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.20.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.20.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.20.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.20.0/getting-started/deploy.mdx b/website/versioned_docs/version-0.20.0/getting-started/deploy.mdx index d4d4e6ac6f..f8db3af96b 100644 --- a/website/versioned_docs/version-0.20.0/getting-started/deploy.mdx +++ b/website/versioned_docs/version-0.20.0/getting-started/deploy.mdx @@ -79,7 +79,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.20.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.20.0/gitops-run/get-started.mdx index 3d7afb8b10..9e04ecc4b4 100644 --- a/website/versioned_docs/version-0.20.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.20.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.20.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.20.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.20.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.20.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.20.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.20.0/gitops-templates/quickstart-templates.mdx index ea32317412..645955f8b4 100644 --- a/website/versioned_docs/version-0.20.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.20.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.20.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.20.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.20.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.20.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.20.0/guides/cert-manager.md b/website/versioned_docs/version-0.20.0/guides/cert-manager.md index 53bacf2d2a..279e557062 100644 --- a/website/versioned_docs/version-0.20.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.20.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.20.0/guides/delivery.mdx b/website/versioned_docs/version-0.20.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.20.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.20.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.20.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.20.0/guides/setting-up-dex.md index 00d92922fb..20a272be15 100644 --- a/website/versioned_docs/version-0.20.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.20.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.20.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.20.0/guides/using-terraform-templates.mdx index 498921bd16..fe20138104 100644 --- a/website/versioned_docs/version-0.20.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.20.0/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](installation/weave-gitops-enterprise/index.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.20.0/installation/aws-marketplace.mdx b/website/versioned_docs/version-0.20.0/installation/aws-marketplace.mdx index 929b1910b8..2421ffbb20 100644 --- a/website/versioned_docs/version-0.20.0/installation/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.20.0/installation/aws-marketplace.mdx @@ -33,7 +33,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -89,7 +90,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/airgap.mdx b/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/airgap.mdx index d51c6fe148..89473630d4 100644 --- a/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/airgap.mdx +++ b/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/airgap.mdx @@ -81,7 +81,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -191,7 +192,8 @@ EOF ``` Execute `make` using the following makefile to intialise capi in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -238,7 +240,8 @@ capi-cluster: Apply the following example manifest to deploy the terraform controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -279,7 +282,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -423,7 +427,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. The following Makefile is supplied to help you with each stage. -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -495,7 +500,8 @@ with the following considerations: An example of how it would look like for Weave Gitops Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx index ff7500a38a..3e5bf10e99 100644 --- a/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx @@ -308,7 +308,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx index c83213b281..b86aaa7481 100644 --- a/website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.20.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.20.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.20.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.20.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.20.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.20.0/pipelines/promoting-applications.mdx index 1fae258d9c..6dfe794a22 100644 --- a/website/versioned_docs/version-0.20.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.20.0/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.20.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.20.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.20.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.20.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.20.0/policy/getting-started.mdx b/website/versioned_docs/version-0.20.0/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.20.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.20.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.20.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.20.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.20.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.20.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.20.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.20.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.20.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.20.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.20.0/secrets/bootstraping-secrets.mdx b/website/versioned_docs/version-0.20.0/secrets/bootstraping-secrets.mdx index 4553f73552..582533274a 100644 --- a/website/versioned_docs/version-0.20.0/secrets/bootstraping-secrets.mdx +++ b/website/versioned_docs/version-0.20.0/secrets/bootstraping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../releases.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.20.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.20.0/secrets/getting-started.mdx index 124ec7894c..86af56f464 100644 --- a/website/versioned_docs/version-0.20.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.20.0/secrets/getting-started.mdx @@ -31,7 +31,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -99,7 +100,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.20.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.20.0/secrets/setup-eso.mdx index dd348a3990..f9a9d23cf8 100644 --- a/website/versioned_docs/version-0.20.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.20.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx index 451f65f577..f648418732 100644 --- a/website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx @@ -29,7 +29,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -106,7 +107,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -199,7 +201,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -246,7 +249,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.20.0/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.20.0/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.20.0/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.20.0/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.20.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.20.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.20.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.20.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.21.1/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.21.1/cluster-management/getting-started.mdx index 785684efb7..d87a9cdff9 100644 --- a/website/versioned_docs/version-0.21.1/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.21.1/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.21.1/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.21.1/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.21.1/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.21.1/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.21.1/configuration/user-permissions.mdx b/website/versioned_docs/version-0.21.1/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.21.1/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.21.1/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.21.1/getting-started/deploy.mdx b/website/versioned_docs/version-0.21.1/getting-started/deploy.mdx index d4d4e6ac6f..f8db3af96b 100644 --- a/website/versioned_docs/version-0.21.1/getting-started/deploy.mdx +++ b/website/versioned_docs/version-0.21.1/getting-started/deploy.mdx @@ -79,7 +79,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.21.1/gitops-run/get-started.mdx b/website/versioned_docs/version-0.21.1/gitops-run/get-started.mdx index 3d7afb8b10..9e04ecc4b4 100644 --- a/website/versioned_docs/version-0.21.1/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.21.1/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.21.1/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.21.1/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.21.1/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.21.1/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.21.1/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.21.1/gitops-templates/quickstart-templates.mdx index ea32317412..645955f8b4 100644 --- a/website/versioned_docs/version-0.21.1/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.21.1/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.21.1/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.21.1/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.21.1/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.21.1/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.21.1/guides/cert-manager.md b/website/versioned_docs/version-0.21.1/guides/cert-manager.md index 53bacf2d2a..279e557062 100644 --- a/website/versioned_docs/version-0.21.1/guides/cert-manager.md +++ b/website/versioned_docs/version-0.21.1/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.21.1/guides/delivery.mdx b/website/versioned_docs/version-0.21.1/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.21.1/guides/delivery.mdx +++ b/website/versioned_docs/version-0.21.1/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.21.1/guides/setting-up-dex.md b/website/versioned_docs/version-0.21.1/guides/setting-up-dex.md index 00d92922fb..20a272be15 100644 --- a/website/versioned_docs/version-0.21.1/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.21.1/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.21.1/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.21.1/guides/using-terraform-templates.mdx index 498921bd16..fe20138104 100644 --- a/website/versioned_docs/version-0.21.1/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.21.1/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](installation/weave-gitops-enterprise/index.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.21.1/installation/aws-marketplace.mdx b/website/versioned_docs/version-0.21.1/installation/aws-marketplace.mdx index 929b1910b8..2421ffbb20 100644 --- a/website/versioned_docs/version-0.21.1/installation/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.21.1/installation/aws-marketplace.mdx @@ -33,7 +33,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -89,7 +90,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/airgap.mdx b/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/airgap.mdx index d51c6fe148..89473630d4 100644 --- a/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/airgap.mdx +++ b/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/airgap.mdx @@ -81,7 +81,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -191,7 +192,8 @@ EOF ``` Execute `make` using the following makefile to intialise capi in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -238,7 +240,8 @@ capi-cluster: Apply the following example manifest to deploy the terraform controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -279,7 +282,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -423,7 +427,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. The following Makefile is supplied to help you with each stage. -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -495,7 +500,8 @@ with the following considerations: An example of how it would look like for Weave Gitops Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/index.mdx index 99c002aa67..1c36fd972f 100644 --- a/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/index.mdx @@ -339,7 +339,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.21.1/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.21.1/pipelines/pipeline-templates.mdx index c83213b281..b86aaa7481 100644 --- a/website/versioned_docs/version-0.21.1/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.21.1/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.21.1/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.21.1/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.21.1/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.21.1/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.21.1/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.21.1/pipelines/promoting-applications.mdx index 1fae258d9c..6dfe794a22 100644 --- a/website/versioned_docs/version-0.21.1/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.21.1/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.21.1/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.21.1/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.21.1/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.21.1/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.21.1/policy/getting-started.mdx b/website/versioned_docs/version-0.21.1/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.21.1/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.21.1/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.21.1/policy/policy-configuration.mdx b/website/versioned_docs/version-0.21.1/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.21.1/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.21.1/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.21.1/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.21.1/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.21.1/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.21.1/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.21.1/secrets/bootstraping-secrets.mdx b/website/versioned_docs/version-0.21.1/secrets/bootstraping-secrets.mdx index 4553f73552..582533274a 100644 --- a/website/versioned_docs/version-0.21.1/secrets/bootstraping-secrets.mdx +++ b/website/versioned_docs/version-0.21.1/secrets/bootstraping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../releases.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.21.1/secrets/getting-started.mdx b/website/versioned_docs/version-0.21.1/secrets/getting-started.mdx index 124ec7894c..86af56f464 100644 --- a/website/versioned_docs/version-0.21.1/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.21.1/secrets/getting-started.mdx @@ -31,7 +31,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -99,7 +100,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.21.1/secrets/setup-eso.mdx b/website/versioned_docs/version-0.21.1/secrets/setup-eso.mdx index dd348a3990..f9a9d23cf8 100644 --- a/website/versioned_docs/version-0.21.1/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.21.1/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx b/website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx index 451f65f577..f648418732 100644 --- a/website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx @@ -29,7 +29,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -106,7 +107,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -199,7 +201,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -246,7 +249,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.21.1/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.21.1/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.21.1/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.21.1/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.21.1/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.21.1/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.21.1/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.21.1/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.21.2/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.21.2/cluster-management/getting-started.mdx index 785684efb7..d87a9cdff9 100644 --- a/website/versioned_docs/version-0.21.2/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.21.2/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.21.2/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.21.2/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.21.2/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.21.2/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.21.2/configuration/user-permissions.mdx b/website/versioned_docs/version-0.21.2/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.21.2/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.21.2/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.21.2/getting-started/deploy.mdx b/website/versioned_docs/version-0.21.2/getting-started/deploy.mdx index d4d4e6ac6f..f8db3af96b 100644 --- a/website/versioned_docs/version-0.21.2/getting-started/deploy.mdx +++ b/website/versioned_docs/version-0.21.2/getting-started/deploy.mdx @@ -79,7 +79,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.21.2/gitops-run/get-started.mdx b/website/versioned_docs/version-0.21.2/gitops-run/get-started.mdx index 3d7afb8b10..9e04ecc4b4 100644 --- a/website/versioned_docs/version-0.21.2/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.21.2/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.21.2/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.21.2/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.21.2/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.21.2/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.21.2/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.21.2/gitops-templates/quickstart-templates.mdx index ea32317412..645955f8b4 100644 --- a/website/versioned_docs/version-0.21.2/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.21.2/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.21.2/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.21.2/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.21.2/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.21.2/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.21.2/guides/cert-manager.md b/website/versioned_docs/version-0.21.2/guides/cert-manager.md index 53bacf2d2a..279e557062 100644 --- a/website/versioned_docs/version-0.21.2/guides/cert-manager.md +++ b/website/versioned_docs/version-0.21.2/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.21.2/guides/delivery.mdx b/website/versioned_docs/version-0.21.2/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.21.2/guides/delivery.mdx +++ b/website/versioned_docs/version-0.21.2/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.21.2/guides/setting-up-dex.md b/website/versioned_docs/version-0.21.2/guides/setting-up-dex.md index 00d92922fb..20a272be15 100644 --- a/website/versioned_docs/version-0.21.2/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.21.2/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.21.2/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.21.2/guides/using-terraform-templates.mdx index 498921bd16..fe20138104 100644 --- a/website/versioned_docs/version-0.21.2/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.21.2/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](installation/weave-gitops-enterprise/index.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.21.2/installation/aws-marketplace.mdx b/website/versioned_docs/version-0.21.2/installation/aws-marketplace.mdx index 929b1910b8..2421ffbb20 100644 --- a/website/versioned_docs/version-0.21.2/installation/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.21.2/installation/aws-marketplace.mdx @@ -33,7 +33,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -89,7 +90,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/airgap.mdx b/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/airgap.mdx index d51c6fe148..89473630d4 100644 --- a/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/airgap.mdx +++ b/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/airgap.mdx @@ -81,7 +81,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -191,7 +192,8 @@ EOF ``` Execute `make` using the following makefile to intialise capi in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -238,7 +240,8 @@ capi-cluster: Apply the following example manifest to deploy the terraform controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -279,7 +282,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -423,7 +427,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. The following Makefile is supplied to help you with each stage. -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -495,7 +500,8 @@ with the following considerations: An example of how it would look like for Weave Gitops Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/index.mdx index 99c002aa67..1c36fd972f 100644 --- a/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/index.mdx @@ -339,7 +339,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.21.2/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.21.2/pipelines/pipeline-templates.mdx index c83213b281..b86aaa7481 100644 --- a/website/versioned_docs/version-0.21.2/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.21.2/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.21.2/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.21.2/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.21.2/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.21.2/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.21.2/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.21.2/pipelines/promoting-applications.mdx index 1fae258d9c..6dfe794a22 100644 --- a/website/versioned_docs/version-0.21.2/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.21.2/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.21.2/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.21.2/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.21.2/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.21.2/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.21.2/policy/getting-started.mdx b/website/versioned_docs/version-0.21.2/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.21.2/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.21.2/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.21.2/policy/policy-configuration.mdx b/website/versioned_docs/version-0.21.2/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.21.2/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.21.2/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.21.2/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.21.2/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.21.2/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.21.2/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.21.2/secrets/bootstraping-secrets.mdx b/website/versioned_docs/version-0.21.2/secrets/bootstraping-secrets.mdx index 4553f73552..582533274a 100644 --- a/website/versioned_docs/version-0.21.2/secrets/bootstraping-secrets.mdx +++ b/website/versioned_docs/version-0.21.2/secrets/bootstraping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../releases.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.21.2/secrets/getting-started.mdx b/website/versioned_docs/version-0.21.2/secrets/getting-started.mdx index 124ec7894c..86af56f464 100644 --- a/website/versioned_docs/version-0.21.2/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.21.2/secrets/getting-started.mdx @@ -31,7 +31,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -99,7 +100,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.21.2/secrets/setup-eso.mdx b/website/versioned_docs/version-0.21.2/secrets/setup-eso.mdx index dd348a3990..f9a9d23cf8 100644 --- a/website/versioned_docs/version-0.21.2/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.21.2/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.21.2/secrets/setup-sops.mdx b/website/versioned_docs/version-0.21.2/secrets/setup-sops.mdx index 058a6e14d5..adfe20b0f4 100644 --- a/website/versioned_docs/version-0.21.2/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.21.2/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.21.2/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.21.2/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.21.2/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.21.2/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.21.2/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.21.2/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.21.2/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.21.2/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.22.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.22.0/cluster-management/getting-started.mdx index 18e74b7cc0..f8eba21cd6 100644 --- a/website/versioned_docs/version-0.22.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.22.0/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.22.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.22.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.22.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.22.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.22.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.22.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.22.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.22.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.22.0/explorer/configuration.mdx b/website/versioned_docs/version-0.22.0/explorer/configuration.mdx index 0fe899d986..cbf3a3459e 100644 --- a/website/versioned_docs/version-0.22.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.22.0/explorer/configuration.mdx @@ -101,7 +101,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount `collector` in `flux-system` namespace for any leaf cluster that you want to watch. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -116,7 +117,8 @@ metadata: 2. Create a ClusterRole `collector` with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -142,7 +144,8 @@ rules: 3. Create a ClusterRolebinding `collector` to assign permissions to `collector` ServiceAccount. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -165,7 +168,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.22.0/getting-started/deploy.mdx b/website/versioned_docs/version-0.22.0/getting-started/deploy.mdx index d4d4e6ac6f..f8db3af96b 100644 --- a/website/versioned_docs/version-0.22.0/getting-started/deploy.mdx +++ b/website/versioned_docs/version-0.22.0/getting-started/deploy.mdx @@ -79,7 +79,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.22.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.22.0/gitops-run/get-started.mdx index 3d7afb8b10..9e04ecc4b4 100644 --- a/website/versioned_docs/version-0.22.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.22.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.22.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.22.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.22.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.22.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.22.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.22.0/gitops-templates/quickstart-templates.mdx index ea32317412..645955f8b4 100644 --- a/website/versioned_docs/version-0.22.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.22.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.22.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.22.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.22.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.22.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.22.0/guides/cert-manager.md b/website/versioned_docs/version-0.22.0/guides/cert-manager.md index 53bacf2d2a..279e557062 100644 --- a/website/versioned_docs/version-0.22.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.22.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.22.0/guides/delivery.mdx b/website/versioned_docs/version-0.22.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.22.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.22.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.22.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.22.0/guides/fluxga-upgrade.mdx index 182505ec6d..03e1e03b7d 100644 --- a/website/versioned_docs/version-0.22.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.22.0/guides/fluxga-upgrade.mdx @@ -139,7 +139,8 @@ First we ensure any new clusters are bootstrapped with Flux GA, then we'll upgra `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`, make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.22.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.22.0/guides/setting-up-dex.md index 00d92922fb..20a272be15 100644 --- a/website/versioned_docs/version-0.22.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.22.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.22.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.22.0/guides/using-terraform-templates.mdx index 498921bd16..fe20138104 100644 --- a/website/versioned_docs/version-0.22.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.22.0/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](installation/weave-gitops-enterprise/index.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.22.0/installation/aws-marketplace.mdx b/website/versioned_docs/version-0.22.0/installation/aws-marketplace.mdx index 02a7eae6dc..3893b5171e 100644 --- a/website/versioned_docs/version-0.22.0/installation/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.22.0/installation/aws-marketplace.mdx @@ -32,7 +32,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -88,7 +89,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/airgap.mdx b/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/airgap.mdx index d51c6fe148..89473630d4 100644 --- a/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/airgap.mdx +++ b/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/airgap.mdx @@ -81,7 +81,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -191,7 +192,8 @@ EOF ``` Execute `make` using the following makefile to intialise capi in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -238,7 +240,8 @@ capi-cluster: Apply the following example manifest to deploy the terraform controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -279,7 +282,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -423,7 +427,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. The following Makefile is supplied to help you with each stage. -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -495,7 +500,8 @@ with the following considerations: An example of how it would look like for Weave Gitops Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/index.mdx index 8b11de1c5c..28210e18e6 100644 --- a/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/index.mdx @@ -339,7 +339,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.22.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.22.0/pipelines/pipeline-templates.mdx index c83213b281..b86aaa7481 100644 --- a/website/versioned_docs/version-0.22.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.22.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.22.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.22.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.22.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.22.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.22.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.22.0/pipelines/promoting-applications.mdx index 1fae258d9c..6dfe794a22 100644 --- a/website/versioned_docs/version-0.22.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.22.0/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.22.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.22.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.22.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.22.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.22.0/policy/getting-started.mdx b/website/versioned_docs/version-0.22.0/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.22.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.22.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.22.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.22.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.22.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.22.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.22.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.22.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.22.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.22.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.22.0/secrets/bootstraping-secrets.mdx b/website/versioned_docs/version-0.22.0/secrets/bootstraping-secrets.mdx index 4553f73552..582533274a 100644 --- a/website/versioned_docs/version-0.22.0/secrets/bootstraping-secrets.mdx +++ b/website/versioned_docs/version-0.22.0/secrets/bootstraping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../releases.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.22.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.22.0/secrets/getting-started.mdx index 124ec7894c..86af56f464 100644 --- a/website/versioned_docs/version-0.22.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.22.0/secrets/getting-started.mdx @@ -31,7 +31,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -99,7 +100,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.22.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.22.0/secrets/setup-eso.mdx index dd348a3990..f9a9d23cf8 100644 --- a/website/versioned_docs/version-0.22.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.22.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.22.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.22.0/secrets/setup-sops.mdx index 058a6e14d5..adfe20b0f4 100644 --- a/website/versioned_docs/version-0.22.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.22.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.22.0/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.22.0/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.22.0/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.22.0/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.22.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.22.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.22.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.22.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.23.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.23.0/cluster-management/getting-started.mdx index 18e74b7cc0..f8eba21cd6 100644 --- a/website/versioned_docs/version-0.23.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.23.0/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.23.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.23.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.23.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.23.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.23.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.23.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.23.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.23.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.23.0/explorer/configuration.mdx b/website/versioned_docs/version-0.23.0/explorer/configuration.mdx index 248f394134..db89f26546 100644 --- a/website/versioned_docs/version-0.23.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.23.0/explorer/configuration.mdx @@ -109,7 +109,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.23.0/getting-started/deploy.mdx b/website/versioned_docs/version-0.23.0/getting-started/deploy.mdx index d4d4e6ac6f..f8db3af96b 100644 --- a/website/versioned_docs/version-0.23.0/getting-started/deploy.mdx +++ b/website/versioned_docs/version-0.23.0/getting-started/deploy.mdx @@ -79,7 +79,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.23.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.23.0/gitops-run/get-started.mdx index 3d7afb8b10..9e04ecc4b4 100644 --- a/website/versioned_docs/version-0.23.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.23.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.23.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.23.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.23.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.23.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.23.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.23.0/gitops-templates/quickstart-templates.mdx index ea32317412..645955f8b4 100644 --- a/website/versioned_docs/version-0.23.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.23.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.23.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.23.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.23.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.23.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.23.0/guides/cert-manager.md b/website/versioned_docs/version-0.23.0/guides/cert-manager.md index 53bacf2d2a..279e557062 100644 --- a/website/versioned_docs/version-0.23.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.23.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.23.0/guides/delivery.mdx b/website/versioned_docs/version-0.23.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.23.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.23.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.23.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.23.0/guides/fluxga-upgrade.mdx index 182505ec6d..03e1e03b7d 100644 --- a/website/versioned_docs/version-0.23.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.23.0/guides/fluxga-upgrade.mdx @@ -139,7 +139,8 @@ First we ensure any new clusters are bootstrapped with Flux GA, then we'll upgra `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`, make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.23.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.23.0/guides/setting-up-dex.md index 00d92922fb..20a272be15 100644 --- a/website/versioned_docs/version-0.23.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.23.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.23.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.23.0/guides/using-terraform-templates.mdx index 498921bd16..fe20138104 100644 --- a/website/versioned_docs/version-0.23.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.23.0/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](installation/weave-gitops-enterprise/index.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.23.0/installation/aws-marketplace.mdx b/website/versioned_docs/version-0.23.0/installation/aws-marketplace.mdx index 929b1910b8..2421ffbb20 100644 --- a/website/versioned_docs/version-0.23.0/installation/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.23.0/installation/aws-marketplace.mdx @@ -33,7 +33,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -89,7 +90,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/airgap.mdx b/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/airgap.mdx index d51c6fe148..89473630d4 100644 --- a/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/airgap.mdx +++ b/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/airgap.mdx @@ -81,7 +81,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -191,7 +192,8 @@ EOF ``` Execute `make` using the following makefile to intialise capi in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -238,7 +240,8 @@ capi-cluster: Apply the following example manifest to deploy the terraform controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -279,7 +282,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -423,7 +427,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. The following Makefile is supplied to help you with each stage. -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -495,7 +500,8 @@ with the following considerations: An example of how it would look like for Weave Gitops Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/index.mdx index 8b11de1c5c..28210e18e6 100644 --- a/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/index.mdx @@ -339,7 +339,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.23.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.23.0/pipelines/pipeline-templates.mdx index c83213b281..b86aaa7481 100644 --- a/website/versioned_docs/version-0.23.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.23.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.23.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.23.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.23.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.23.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.23.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.23.0/pipelines/promoting-applications.mdx index 4db86b51aa..f1e3913dd4 100644 --- a/website/versioned_docs/version-0.23.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.23.0/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.23.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.23.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.23.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.23.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.23.0/policy/getting-started.mdx b/website/versioned_docs/version-0.23.0/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.23.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.23.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.23.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.23.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.23.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.23.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.23.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.23.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.23.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.23.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.23.0/secrets/bootstraping-secrets.mdx b/website/versioned_docs/version-0.23.0/secrets/bootstraping-secrets.mdx index 4553f73552..582533274a 100644 --- a/website/versioned_docs/version-0.23.0/secrets/bootstraping-secrets.mdx +++ b/website/versioned_docs/version-0.23.0/secrets/bootstraping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../releases.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.23.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.23.0/secrets/getting-started.mdx index 124ec7894c..86af56f464 100644 --- a/website/versioned_docs/version-0.23.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.23.0/secrets/getting-started.mdx @@ -31,7 +31,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -99,7 +100,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.23.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.23.0/secrets/setup-eso.mdx index dd348a3990..f9a9d23cf8 100644 --- a/website/versioned_docs/version-0.23.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.23.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.23.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.23.0/secrets/setup-sops.mdx index 058a6e14d5..adfe20b0f4 100644 --- a/website/versioned_docs/version-0.23.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.23.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.23.0/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.23.0/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.23.0/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.23.0/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.23.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.23.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.23.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.23.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.24.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.24.0/cluster-management/getting-started.mdx index 495f50fd2f..733ea1dc15 100644 --- a/website/versioned_docs/version-0.24.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.24.0/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.24.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.24.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.24.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.24.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.24.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.24.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.24.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.24.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.24.0/enterprise/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.24.0/enterprise/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.24.0/enterprise/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.24.0/enterprise/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise-airgap.mdx index ddd17021d5..d6c4a4ffaa 100644 --- a/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise capi in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the terraform controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. The following Makefile is supplied to help you with each stage. -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -494,7 +499,8 @@ with the following considerations: An example of how it would look like for Weave Gitops Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise.mdx index f5fad1f0bc..7b46ba4fe8 100644 --- a/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise.mdx @@ -336,7 +336,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.24.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.24.0/gitops-run/get-started.mdx index 0e04f65e45..b134bed88c 100644 --- a/website/versioned_docs/version-0.24.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.24.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.24.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.24.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.24.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.24.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.24.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.24.0/gitops-templates/quickstart-templates.mdx index fd57f83dab..2ab41b1185 100644 --- a/website/versioned_docs/version-0.24.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.24.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.24.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.24.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.24.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.24.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.24.0/guides/cert-manager.md b/website/versioned_docs/version-0.24.0/guides/cert-manager.md index 31254548d1..cdd93f04ed 100644 --- a/website/versioned_docs/version-0.24.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.24.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.24.0/guides/delivery.mdx b/website/versioned_docs/version-0.24.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.24.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.24.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.24.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.24.0/guides/fluxga-upgrade.mdx index 182505ec6d..03e1e03b7d 100644 --- a/website/versioned_docs/version-0.24.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.24.0/guides/fluxga-upgrade.mdx @@ -139,7 +139,8 @@ First we ensure any new clusters are bootstrapped with Flux GA, then we'll upgra `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`, make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.24.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.24.0/guides/setting-up-dex.md index 378c3f1b40..0a11f980fb 100644 --- a/website/versioned_docs/version-0.24.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.24.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.24.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.24.0/guides/using-terraform-templates.mdx index cbc45a825a..ed78bca35b 100644 --- a/website/versioned_docs/version-0.24.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.24.0/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.24.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.24.0/open-source/getting-started/deploy-OSS.mdx index d4d4e6ac6f..f8db3af96b 100644 --- a/website/versioned_docs/version-0.24.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.24.0/open-source/getting-started/deploy-OSS.mdx @@ -79,7 +79,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.24.0/pipelines/getting-started.mdx b/website/versioned_docs/version-0.24.0/pipelines/getting-started.mdx index 4fa61c1ff6..6f7f2dfdcc 100644 --- a/website/versioned_docs/version-0.24.0/pipelines/getting-started.mdx +++ b/website/versioned_docs/version-0.24.0/pipelines/getting-started.mdx @@ -29,7 +29,8 @@ There are three main concepts playing in a pipeline: You can define a delivery pipeline using a `Pipeline` custom resource. An example of how it looks for an application `podinfo` is shown below. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.24.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.24.0/pipelines/pipeline-templates.mdx index c83213b281..b86aaa7481 100644 --- a/website/versioned_docs/version-0.24.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.24.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.24.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.24.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.24.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.24.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.24.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.24.0/pipelines/promoting-applications.mdx index 4db86b51aa..f1e3913dd4 100644 --- a/website/versioned_docs/version-0.24.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.24.0/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.24.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.24.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.24.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.24.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.24.0/policy/getting-started.mdx b/website/versioned_docs/version-0.24.0/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.24.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.24.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.24.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.24.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.24.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.24.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.24.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.24.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.24.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.24.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.24.0/secrets/bootstraping-secrets.mdx b/website/versioned_docs/version-0.24.0/secrets/bootstraping-secrets.mdx index 90f4017d5a..2e4b1ad8d0 100644 --- a/website/versioned_docs/version-0.24.0/secrets/bootstraping-secrets.mdx +++ b/website/versioned_docs/version-0.24.0/secrets/bootstraping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.24.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.24.0/secrets/getting-started.mdx index 124ec7894c..86af56f464 100644 --- a/website/versioned_docs/version-0.24.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.24.0/secrets/getting-started.mdx @@ -31,7 +31,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -99,7 +100,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.24.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.24.0/secrets/setup-eso.mdx index dd348a3990..f9a9d23cf8 100644 --- a/website/versioned_docs/version-0.24.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.24.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.24.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.24.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.24.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.24.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.24.0/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.24.0/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.24.0/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.24.0/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.24.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.24.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.24.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.24.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.25.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.25.0/cluster-management/getting-started.mdx index 495f50fd2f..733ea1dc15 100644 --- a/website/versioned_docs/version-0.25.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.25.0/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.25.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.25.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.25.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.25.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.25.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.25.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.25.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.25.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.25.0/enterprise/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.25.0/enterprise/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.25.0/enterprise/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.25.0/enterprise/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise-airgap.mdx index 2fc25470cf..1d51c9cd70 100644 --- a/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise.mdx index eb646d2c57..38c85a9545 100644 --- a/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise.mdx @@ -350,7 +350,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.25.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.25.0/gitops-run/get-started.mdx index 1099016688..29c0265ce1 100644 --- a/website/versioned_docs/version-0.25.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.25.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.25.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.25.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.25.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.25.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.25.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.25.0/gitops-templates/quickstart-templates.mdx index 1dac2e0812..fd1f4d9f24 100644 --- a/website/versioned_docs/version-0.25.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.25.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.25.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.25.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.25.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.25.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.25.0/guides/cert-manager.md b/website/versioned_docs/version-0.25.0/guides/cert-manager.md index 8640eeebea..d55c19a9bf 100644 --- a/website/versioned_docs/version-0.25.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.25.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.25.0/guides/delivery.mdx b/website/versioned_docs/version-0.25.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.25.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.25.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.25.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.25.0/guides/fluxga-upgrade.mdx index 4a8468f383..dfc17ee74c 100644 --- a/website/versioned_docs/version-0.25.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.25.0/guides/fluxga-upgrade.mdx @@ -139,7 +139,8 @@ First we ensure any new clusters are bootstrapped with Flux GA, then we'll upgra `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`, make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.25.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.25.0/guides/setting-up-dex.md index b2fcaf2258..9a890c9f2b 100644 --- a/website/versioned_docs/version-0.25.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.25.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.25.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.25.0/guides/using-terraform-templates.mdx index d07d77693d..026137876a 100644 --- a/website/versioned_docs/version-0.25.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.25.0/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.25.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.25.0/open-source/getting-started/deploy-OSS.mdx index 2fb11fb10c..817938ce3e 100644 --- a/website/versioned_docs/version-0.25.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.25.0/open-source/getting-started/deploy-OSS.mdx @@ -74,7 +74,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.25.0/pipelines/getting-started.mdx b/website/versioned_docs/version-0.25.0/pipelines/getting-started.mdx index 4fa61c1ff6..6f7f2dfdcc 100644 --- a/website/versioned_docs/version-0.25.0/pipelines/getting-started.mdx +++ b/website/versioned_docs/version-0.25.0/pipelines/getting-started.mdx @@ -29,7 +29,8 @@ There are three main concepts playing in a pipeline: You can define a delivery pipeline using a `Pipeline` custom resource. An example of how it looks for an application `podinfo` is shown below. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.25.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.25.0/pipelines/pipeline-templates.mdx index b7962baa13..24386e0d92 100644 --- a/website/versioned_docs/version-0.25.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.25.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.25.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.25.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.25.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.25.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.25.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.25.0/pipelines/promoting-applications.mdx index 4db86b51aa..f1e3913dd4 100644 --- a/website/versioned_docs/version-0.25.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.25.0/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.25.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.25.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.25.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.25.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.25.0/policy/getting-started.mdx b/website/versioned_docs/version-0.25.0/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.25.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.25.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.25.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.25.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.25.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.25.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.25.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.25.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.25.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.25.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.25.0/secrets/bootstraping-secrets.mdx b/website/versioned_docs/version-0.25.0/secrets/bootstraping-secrets.mdx index 90f4017d5a..2e4b1ad8d0 100644 --- a/website/versioned_docs/version-0.25.0/secrets/bootstraping-secrets.mdx +++ b/website/versioned_docs/version-0.25.0/secrets/bootstraping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.25.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.25.0/secrets/getting-started.mdx index 124ec7894c..86af56f464 100644 --- a/website/versioned_docs/version-0.25.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.25.0/secrets/getting-started.mdx @@ -31,7 +31,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -99,7 +100,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.25.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.25.0/secrets/setup-eso.mdx index dd348a3990..f9a9d23cf8 100644 --- a/website/versioned_docs/version-0.25.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.25.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.25.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.25.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.25.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.25.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.25.0/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.25.0/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.25.0/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.25.0/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.25.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.25.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.25.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.25.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.26.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.26.0/cluster-management/getting-started.mdx index 495f50fd2f..733ea1dc15 100644 --- a/website/versioned_docs/version-0.26.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.26.0/cluster-management/getting-started.mdx @@ -73,7 +73,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -106,7 +107,8 @@ kubectl create secret generic demo-01-kubeconfig \ We'll use a helper script to generate the kubeconfig, save this into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -238,7 +240,8 @@ Once flux has reconciled the cluster you can inspect your flux resources via the To test a kubeconfig secret has been correctly setup apply the following manifest and check the logs after the job completes: -
Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.26.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.26.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.26.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.26.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.26.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.26.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.26.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.26.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.26.0/enterprise/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.26.0/enterprise/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.26.0/enterprise/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.26.0/enterprise/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise-airgap.mdx index 2fc25470cf..1d51c9cd70 100644 --- a/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise.mdx index eb646d2c57..38c85a9545 100644 --- a/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise.mdx @@ -350,7 +350,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.26.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.26.0/gitops-run/get-started.mdx index 1099016688..29c0265ce1 100644 --- a/website/versioned_docs/version-0.26.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.26.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.26.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.26.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.26.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.26.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.26.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.26.0/gitops-templates/quickstart-templates.mdx index 1dac2e0812..fd1f4d9f24 100644 --- a/website/versioned_docs/version-0.26.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.26.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.26.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.26.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.26.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.26.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.26.0/guides/cert-manager.md b/website/versioned_docs/version-0.26.0/guides/cert-manager.md index 8640eeebea..d55c19a9bf 100644 --- a/website/versioned_docs/version-0.26.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.26.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.26.0/guides/delivery.mdx b/website/versioned_docs/version-0.26.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.26.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.26.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.26.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.26.0/guides/fluxga-upgrade.mdx index 4a8468f383..dfc17ee74c 100644 --- a/website/versioned_docs/version-0.26.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.26.0/guides/fluxga-upgrade.mdx @@ -139,7 +139,8 @@ First we ensure any new clusters are bootstrapped with Flux GA, then we'll upgra `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`, make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.26.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.26.0/guides/setting-up-dex.md index b2fcaf2258..9a890c9f2b 100644 --- a/website/versioned_docs/version-0.26.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.26.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.26.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.26.0/guides/using-terraform-templates.mdx index d07d77693d..026137876a 100644 --- a/website/versioned_docs/version-0.26.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.26.0/guides/using-terraform-templates.mdx @@ -22,7 +22,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -175,7 +176,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -250,7 +252,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.26.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.26.0/open-source/getting-started/deploy-OSS.mdx index 2fb11fb10c..817938ce3e 100644 --- a/website/versioned_docs/version-0.26.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.26.0/open-source/getting-started/deploy-OSS.mdx @@ -74,7 +74,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/my-cluster/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.26.0/pipelines/getting-started.mdx b/website/versioned_docs/version-0.26.0/pipelines/getting-started.mdx index 4fa61c1ff6..6f7f2dfdcc 100644 --- a/website/versioned_docs/version-0.26.0/pipelines/getting-started.mdx +++ b/website/versioned_docs/version-0.26.0/pipelines/getting-started.mdx @@ -29,7 +29,8 @@ There are three main concepts playing in a pipeline: You can define a delivery pipeline using a `Pipeline` custom resource. An example of how it looks for an application `podinfo` is shown below. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.26.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.26.0/pipelines/pipeline-templates.mdx index b7962baa13..24386e0d92 100644 --- a/website/versioned_docs/version-0.26.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.26.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.26.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.26.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.26.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.26.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.26.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.26.0/pipelines/promoting-applications.mdx index 4db86b51aa..f1e3913dd4 100644 --- a/website/versioned_docs/version-0.26.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.26.0/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.26.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.26.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.26.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.26.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.26.0/policy/getting-started.mdx b/website/versioned_docs/version-0.26.0/policy/getting-started.mdx index 5220ffa3d0..d2a9171f65 100644 --- a/website/versioned_docs/version-0.26.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.26.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the [secret](../cluster-management/getting-started.mdx#add-a-cluster-bootstrap-config) you created while bootstrapping flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.26.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.26.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.26.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.26.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.26.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.26.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.26.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.26.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.26.0/secrets/bootstraping-secrets.mdx b/website/versioned_docs/version-0.26.0/secrets/bootstraping-secrets.mdx index 90f4017d5a..2e4b1ad8d0 100644 --- a/website/versioned_docs/version-0.26.0/secrets/bootstraping-secrets.mdx +++ b/website/versioned_docs/version-0.26.0/secrets/bootstraping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.26.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.26.0/secrets/getting-started.mdx index 124ec7894c..86af56f464 100644 --- a/website/versioned_docs/version-0.26.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.26.0/secrets/getting-started.mdx @@ -31,7 +31,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -99,7 +100,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.26.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.26.0/secrets/setup-eso.mdx index dd348a3990..f9a9d23cf8 100644 --- a/website/versioned_docs/version-0.26.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.26.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.26.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.26.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.26.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.26.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.26.0/terraform/oci-artifact.mdx b/website/versioned_docs/version-0.26.0/terraform/oci-artifact.mdx index 48e9978633..6f990c0896 100644 --- a/website/versioned_docs/version-0.26.0/terraform/oci-artifact.mdx +++ b/website/versioned_docs/version-0.26.0/terraform/oci-artifact.mdx @@ -21,7 +21,8 @@ flux tag artifact oci://ghcr.io/tf-controller/helloworld:$(git rev-parse --short To use the OCI artifact as the source for your `Terraform` object, you'll need to define an `OCIRepository` and use it as the `spec.sourceRef` of your `Terraform` object: -
Expand to view +
+Expand to view ```yaml {5,20-22} --- diff --git a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/custom-backend.mdx index da3a831f64..4cd4641d48 100644 --- a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/custom-backend.mdx @@ -20,7 +20,8 @@ in the `Terraform` object. Here is an example of how to use a custom backend with the `Terraform` object: -
Expand to view +
+Expand to view ```yaml {9-21} --- diff --git a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/customize-runner.mdx b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/customize-runner.mdx index 4fcbebe649..0c560a31ee 100644 --- a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/customize-runner.mdx +++ b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/customize-runner.mdx @@ -9,7 +9,8 @@ In some situations, it is needed to add custom labels and annotations to the run For example, for Azure AKS to grant pod active directory permissions using Azure Active Directory (AAD) Pod Identity, a label like `aadpodidbinding: myIdentity` on the pod is required. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 @@ -38,7 +39,8 @@ spec: By default, the Terraform controller uses `RUNNER_POD_IMAGE` environment variable to identify the Runner Pod's image to use. You can customize the image on the global level by updating the value of the environment variable or, you can specify an image to use per Terraform object for its reconciliation. -
Expand to view +
+Expand to view ```yaml apiVersion: infra.contrib.fluxcd.io/v1alpha1 diff --git a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/depends-on.mdx b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/depends-on.mdx index d4e6cd1dae..f89cf6a96c 100644 --- a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/depends-on.mdx +++ b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/depends-on.mdx @@ -22,7 +22,8 @@ First, create a `Terraform` object to provision the S3 bucket, name it `aws-s3-b The S3 bucket is provisioned by the Terraform module `aws_s3_bucket` in the OCI image `aws-package-v4.33.0`. It is configured to use the `auto-apply` mode, and write outputs to the secret `aws-s3-bucket-outputs`. -
Expand to view +
+Expand to view ```yaml {20-24} --- @@ -71,7 +72,8 @@ For example, the `spec.values.bucket` field in the `aws-s3-bucket-acl` Terraform Please note that we use `${{` and `}}` as the delimiters for the variable name, instead of the Helm default ones, `{{` and `}}`. -
Expand to view +
+Expand to view ```yaml hl_lines="11 18 20-21" --- diff --git a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/modules.mdx b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/modules.mdx index d518e663c2..b5c71b49bf 100644 --- a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/modules.mdx +++ b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/modules.mdx @@ -36,7 +36,8 @@ will be converted to an HCL variable, and passed to the Terraform module. 4. We need to set the `spec.approvePlan` field to `auto` to automatically approve the plan. -
Expand to view +
+Expand to view ```yaml {19-26} --- diff --git a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 0ee2c2e9b9..a27eb22e37 100644 --- a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -40,7 +40,8 @@ passed to `varsFrom`. Here is an example of a `Terraform` object that sets inline variables using the `vars` field and retrieves variables from a `ConfigMap` and `Secret` using the `varsFrom` field: -
Expand to view +
+Expand to view ```yaml {15-20,22-28} --- @@ -88,7 +89,8 @@ the "node_count" field is a number, and the "public" field is a boolean. This allows you to set variables in your Terraform configuration in a flexible and dynamic way, using data that can be passed in through the `Terraform` object. -
Expand to view +
+Expand to view ```hcl {3-6} variable "cluster_spec" { diff --git a/website/versioned_docs/version-0.26.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.26.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.26.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.26.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.27.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.27.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.27.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.27.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -210,7 +212,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.27.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.27.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.27.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.27.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.27.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.27.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.27.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.27.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.27.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.27.0/enterprise/getting-started/install-enterprise-airgap.mdx index 2fc25470cf..1d51c9cd70 100644 --- a/website/versioned_docs/version-0.27.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.27.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.27.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.27.0/enterprise/getting-started/install-enterprise.mdx index f58f489a82..925c6fc7bd 100644 --- a/website/versioned_docs/version-0.27.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.27.0/enterprise/getting-started/install-enterprise.mdx @@ -302,7 +302,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.27.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.27.0/gitops-run/get-started.mdx index 1099016688..29c0265ce1 100644 --- a/website/versioned_docs/version-0.27.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.27.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.27.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.27.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.27.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.27.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.27.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.27.0/gitops-templates/quickstart-templates.mdx index 1dac2e0812..fd1f4d9f24 100644 --- a/website/versioned_docs/version-0.27.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.27.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.27.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.27.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.27.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.27.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.27.0/guides/cert-manager.md b/website/versioned_docs/version-0.27.0/guides/cert-manager.md index 8640eeebea..d55c19a9bf 100644 --- a/website/versioned_docs/version-0.27.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.27.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.27.0/guides/delivery.mdx b/website/versioned_docs/version-0.27.0/guides/delivery.mdx index 55c199c935..15c70fc538 100644 --- a/website/versioned_docs/version-0.27.0/guides/delivery.mdx +++ b/website/versioned_docs/version-0.27.0/guides/delivery.mdx @@ -90,7 +90,8 @@ directory. These are: - A `HelmRelease` resource to install the latest version of Linkerd from that `HelmRepository` -
Expand to see the Linkerd manifests +
+Expand to see the Linkerd manifests ```yaml title="linkerd/namespace.yaml" --- @@ -180,7 +181,8 @@ Next, add the following file to instruct Kustomize to patch any `Secrets` that a `HelmRelease` manifests, and add a `Kustomization` which references all the other `linkerd` resource files. -
Expand to see the linkerd Kustomization manifests +
+Expand to see the linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -274,7 +276,8 @@ These are: tester app, which is used to generate from that synthetic traffic during the analysis phase, from that `HelmRepository` -
Expand to see the Flagger resource manifests +
+Expand to see the Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -339,7 +342,8 @@ spec: Finally, add the following Kustomization file that references all the previous files that were added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -398,7 +402,8 @@ Create a new `test` directory and add the following Canary resources under it: service resource, instead this is specified within the Canary definition and created by Flagger) -
Expand to see the Canary resource manifests +
+Expand to see the Canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -582,7 +587,8 @@ spec: Finally, add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.27.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.27.0/guides/fluxga-upgrade.mdx index 4a8468f383..dfc17ee74c 100644 --- a/website/versioned_docs/version-0.27.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.27.0/guides/fluxga-upgrade.mdx @@ -139,7 +139,8 @@ First we ensure any new clusters are bootstrapped with Flux GA, then we'll upgra `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`, make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.27.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.27.0/guides/setting-up-dex.md index b2fcaf2258..9a890c9f2b 100644 --- a/website/versioned_docs/version-0.27.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.27.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.27.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.27.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.27.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.27.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.27.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.27.0/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.27.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.27.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.27.0/pipelines/getting-started.mdx b/website/versioned_docs/version-0.27.0/pipelines/getting-started.mdx index 4c4197a9b9..15459b41fe 100644 --- a/website/versioned_docs/version-0.27.0/pipelines/getting-started.mdx +++ b/website/versioned_docs/version-0.27.0/pipelines/getting-started.mdx @@ -29,7 +29,8 @@ There are three main concepts playing in a pipeline: You can define a delivery pipeline using a `Pipeline` custom resource. An example of how it looks for an application `podinfo` is shown below. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.27.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.27.0/pipelines/pipeline-templates.mdx index b7962baa13..24386e0d92 100644 --- a/website/versioned_docs/version-0.27.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.27.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.27.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.27.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.27.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.27.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.27.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.27.0/pipelines/promoting-applications.mdx index 4db86b51aa..f1e3913dd4 100644 --- a/website/versioned_docs/version-0.27.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.27.0/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.27.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.27.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.27.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.27.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.27.0/policy/getting-started.mdx b/website/versioned_docs/version-0.27.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.27.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.27.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.27.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.27.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.27.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.27.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.27.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.27.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.27.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.27.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.27.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.27.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.27.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.27.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.27.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.27.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.27.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.27.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.27.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.27.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.27.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.27.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.27.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.27.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.27.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.27.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.27.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.27.0/terraform/using-terraform-templates.mdx index 2a370d9fe2..ed96296f05 100644 --- a/website/versioned_docs/version-0.27.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.27.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.27.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.27.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.27.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.27.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.28.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.28.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.28.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.28.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -210,7 +212,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.28.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.28.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.28.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.28.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.28.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.28.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.28.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.28.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.28.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.28.0/enterprise/getting-started/install-enterprise-airgap.mdx index 2fc25470cf..1d51c9cd70 100644 --- a/website/versioned_docs/version-0.28.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.28.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.28.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.28.0/enterprise/getting-started/install-enterprise.mdx index 8559bbaa9a..7dab81f61c 100644 --- a/website/versioned_docs/version-0.28.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.28.0/enterprise/getting-started/install-enterprise.mdx @@ -302,7 +302,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.28.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.28.0/gitops-run/get-started.mdx index 1099016688..29c0265ce1 100644 --- a/website/versioned_docs/version-0.28.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.28.0/gitops-run/get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.28.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.28.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.28.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.28.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.28.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.28.0/gitops-templates/quickstart-templates.mdx index 1dac2e0812..fd1f4d9f24 100644 --- a/website/versioned_docs/version-0.28.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.28.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.28.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.28.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.28.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.28.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.28.0/guides/cert-manager.md b/website/versioned_docs/version-0.28.0/guides/cert-manager.md index e2966482ac..f3f6cb6d5b 100644 --- a/website/versioned_docs/version-0.28.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.28.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.28.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.28.0/guides/fluxga-upgrade.mdx index 4a8468f383..dfc17ee74c 100644 --- a/website/versioned_docs/version-0.28.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.28.0/guides/fluxga-upgrade.mdx @@ -139,7 +139,8 @@ First we ensure any new clusters are bootstrapped with Flux GA, then we'll upgra `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`, make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.28.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.28.0/guides/setting-up-dex.md index b2fcaf2258..9a890c9f2b 100644 --- a/website/versioned_docs/version-0.28.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.28.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.28.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.28.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.28.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.28.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.28.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.28.0/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.28.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.28.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.28.0/pipelines/getting-started.mdx b/website/versioned_docs/version-0.28.0/pipelines/getting-started.mdx index 4c4197a9b9..15459b41fe 100644 --- a/website/versioned_docs/version-0.28.0/pipelines/getting-started.mdx +++ b/website/versioned_docs/version-0.28.0/pipelines/getting-started.mdx @@ -29,7 +29,8 @@ There are three main concepts playing in a pipeline: You can define a delivery pipeline using a `Pipeline` custom resource. An example of how it looks for an application `podinfo` is shown below. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.28.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.28.0/pipelines/pipeline-templates.mdx index b7962baa13..24386e0d92 100644 --- a/website/versioned_docs/version-0.28.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.28.0/pipelines/pipeline-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.28.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.28.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.28.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.28.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.28.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.28.0/pipelines/promoting-applications.mdx index 4db86b51aa..f1e3913dd4 100644 --- a/website/versioned_docs/version-0.28.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.28.0/pipelines/promoting-applications.mdx @@ -181,7 +181,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -235,7 +236,8 @@ Adopt as much of the recommendations in this section to reduce the risks associa 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and for security and auditing perspective, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
@@ -243,7 +245,8 @@ and for security and auditing perspective, you don't want to impersonate a real 2. **Restrict access to the secret**: the promotion credentials needs to reside in the same Namespace as the Pipeline resource on the management cluster. Restrict via RBAC that only `pipeline-controller` service account is able to read it. -
Expand to see example +
+Expand to see example ```yaml --- @@ -280,14 +283,16 @@ subjects: 3. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
4. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -297,7 +302,8 @@ allow access to the single repo that your configuration manifests exist. 5. **Review active access tokens on a regular basis**: to ensure that only the ones that are required are present at all times. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -406,7 +412,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.28.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.28.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.28.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.28.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.28.0/policy/getting-started.mdx b/website/versioned_docs/version-0.28.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.28.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.28.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.28.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.28.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.28.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.28.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.28.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.28.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.28.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.28.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.28.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.28.0/progressive-delivery/progressive-delivery-flagger-install.mdx index b0998cd0e7..44b249c215 100644 --- a/website/versioned_docs/version-0.28.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.28.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -77,7 +77,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -167,7 +168,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -260,7 +262,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -325,7 +328,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -382,7 +386,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -566,7 +571,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.28.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.28.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.28.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.28.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.28.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.28.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.28.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.28.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.28.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.28.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.28.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.28.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.28.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.28.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.28.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.28.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.28.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.28.0/terraform/using-terraform-templates.mdx index 2a370d9fe2..ed96296f05 100644 --- a/website/versioned_docs/version-0.28.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.28.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.28.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.28.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.28.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.28.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.29.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.29.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.29.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.29.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -210,7 +212,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.29.0/configuration/recommended-rbac-configuration.mdx b/website/versioned_docs/version-0.29.0/configuration/recommended-rbac-configuration.mdx index 03721cfdf3..6c0411b298 100644 --- a/website/versioned_docs/version-0.29.0/configuration/recommended-rbac-configuration.mdx +++ b/website/versioned_docs/version-0.29.0/configuration/recommended-rbac-configuration.mdx @@ -75,7 +75,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role diff --git a/website/versioned_docs/version-0.29.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.29.0/configuration/user-permissions.mdx index 2ec436f633..fbd4976b63 100644 --- a/website/versioned_docs/version-0.29.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.29.0/configuration/user-permissions.mdx @@ -123,7 +123,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -167,7 +168,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.29.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.29.0/enterprise/getting-started/install-enterprise-airgap.mdx index 2fc25470cf..1d51c9cd70 100644 --- a/website/versioned_docs/version-0.29.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.29.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.29.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.29.0/enterprise/getting-started/install-enterprise.mdx index 8559bbaa9a..7dab81f61c 100644 --- a/website/versioned_docs/version-0.29.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.29.0/enterprise/getting-started/install-enterprise.mdx @@ -302,7 +302,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.29.0/gitops-run/gitops-run-get-started.mdx b/website/versioned_docs/version-0.29.0/gitops-run/gitops-run-get-started.mdx index 360ac8f1e5..6c1e400a03 100644 --- a/website/versioned_docs/version-0.29.0/gitops-run/gitops-run-get-started.mdx +++ b/website/versioned_docs/version-0.29.0/gitops-run/gitops-run-get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.29.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.29.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.29.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.29.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.29.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.29.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.29.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.29.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.29.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.29.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.29.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.29.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.29.0/guides/cert-manager.md b/website/versioned_docs/version-0.29.0/guides/cert-manager.md index af4764423b..56837e0dee 100644 --- a/website/versioned_docs/version-0.29.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.29.0/guides/cert-manager.md @@ -25,7 +25,8 @@ simply create a `HelmRepository` and a `HelmRelease` to have Flux install everyt Commit the following to a location being reconciled by Flux. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -74,7 +75,8 @@ Now that `cert-manager` is running, we can create a `ClusterIssuer` to represent from which we will obtain signed certificates, in this example we are using Let's Encrypt. After changing the email address, commit this to the same location as above. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- diff --git a/website/versioned_docs/version-0.29.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.29.0/guides/fluxga-upgrade.mdx index d4bd8e044b..5f905812b9 100644 --- a/website/versioned_docs/version-0.29.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.29.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.29.0/guides/setting-up-dex.md b/website/versioned_docs/version-0.29.0/guides/setting-up-dex.md index b2fcaf2258..9a890c9f2b 100644 --- a/website/versioned_docs/version-0.29.0/guides/setting-up-dex.md +++ b/website/versioned_docs/version-0.29.0/guides/setting-up-dex.md @@ -60,7 +60,8 @@ kubectl create secret generic github-client \ As we did before, we can use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -180,7 +181,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -228,7 +230,8 @@ rules: The same way we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.29.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.29.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.29.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.29.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.29.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.29.0/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.29.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.29.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.29.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.29.0/pipelines/pipelines-getting-started.mdx index 4c4197a9b9..15459b41fe 100644 --- a/website/versioned_docs/version-0.29.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.29.0/pipelines/pipelines-getting-started.mdx @@ -29,7 +29,8 @@ There are three main concepts playing in a pipeline: You can define a delivery pipeline using a `Pipeline` custom resource. An example of how it looks for an application `podinfo` is shown below. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.29.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.29.0/pipelines/pipelines-templates.mdx index b7962baa13..24386e0d92 100644 --- a/website/versioned_docs/version-0.29.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.29.0/pipelines/pipelines-templates.mdx @@ -47,7 +47,8 @@ This template is shipped by default with Weave GitOps Enterprise to help you get For flexibility, this allows the user of the template to specify the names of the Clusters where the application is deployed, and to vary the namespace per cluster. This means it would even work in a tenancy model where environments co-exist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -121,7 +122,8 @@ spec: This example extends the above to add a promotion strategy, in this case it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -231,7 +233,8 @@ For the `Alert`, this template is filtering events to detect when an update has For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret will need to be present on both the management cluster and leaf cluster(s). For simplicity, a `generic` provider could be used instead - which would not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.29.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.29.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.29.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.29.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.29.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.29.0/pipelines/promoting-applications.mdx index 658be2f928..c551e2b82a 100644 --- a/website/versioned_docs/version-0.29.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.29.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.29.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.29.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.29.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.29.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.29.0/policy/getting-started.mdx b/website/versioned_docs/version-0.29.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.29.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.29.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.29.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.29.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.29.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.29.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.29.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.29.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.29.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.29.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.29.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.29.0/progressive-delivery/progressive-delivery-flagger-install.mdx index b0998cd0e7..44b249c215 100644 --- a/website/versioned_docs/version-0.29.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.29.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -77,7 +77,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -167,7 +168,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -260,7 +262,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -325,7 +328,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -382,7 +386,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -566,7 +571,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.29.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.29.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.29.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.29.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.29.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.29.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.29.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.29.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.29.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.29.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.29.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.29.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.29.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.29.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.29.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.29.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.29.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.29.0/terraform/using-terraform-templates.mdx index 2a370d9fe2..ed96296f05 100644 --- a/website/versioned_docs/version-0.29.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.29.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.29.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.29.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.29.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.29.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.30.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.30.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.30.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.30.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.30.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.30.0/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.30.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.30.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.30.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.30.0/enterprise/getting-started/install-enterprise.mdx index 6d0a59324d..c0812abd81 100644 --- a/website/versioned_docs/version-0.30.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.30.0/enterprise/getting-started/install-enterprise.mdx @@ -243,7 +243,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -357,7 +358,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -405,7 +407,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -781,7 +784,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1046,7 +1050,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.30.0/gitops-run/gitops-run-get-started.mdx b/website/versioned_docs/version-0.30.0/gitops-run/gitops-run-get-started.mdx index e2020d2a68..a5245acdc3 100644 --- a/website/versioned_docs/version-0.30.0/gitops-run/gitops-run-get-started.mdx +++ b/website/versioned_docs/version-0.30.0/gitops-run/gitops-run-get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.30.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.30.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.30.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.30.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.30.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.30.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.30.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.30.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.30.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.30.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.30.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.30.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.30.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.30.0/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.30.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.30.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.30.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.30.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.30.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.30.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.30.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.30.0/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.30.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.30.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.30.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.30.0/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.30.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.30.0/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.30.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.30.0/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.30.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.30.0/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.30.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.30.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.30.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.30.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.30.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.30.0/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.30.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.30.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.30.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.30.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.30.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.30.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.30.0/policy/getting-started.mdx b/website/versioned_docs/version-0.30.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.30.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.30.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.30.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.30.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.30.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.30.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.30.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.30.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.30.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.30.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.30.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.30.0/progressive-delivery/progressive-delivery-flagger-install.mdx index b0998cd0e7..44b249c215 100644 --- a/website/versioned_docs/version-0.30.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.30.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -77,7 +77,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -167,7 +168,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -260,7 +262,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -325,7 +328,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -382,7 +386,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -566,7 +571,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.30.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.30.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.30.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.30.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.30.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.30.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.30.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.30.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.30.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.30.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.30.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.30.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.30.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.30.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.30.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.30.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.30.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.30.0/terraform/using-terraform-templates.mdx index c35ecd6092..43b0d036d9 100644 --- a/website/versioned_docs/version-0.30.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.30.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.30.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.30.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.30.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.30.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.31.2/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.31.2/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.31.2/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.31.2/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise.mdx index 6d0a59324d..c0812abd81 100644 --- a/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise.mdx @@ -243,7 +243,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -357,7 +358,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -405,7 +407,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -781,7 +784,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1046,7 +1050,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/versioned_docs/version-0.31.2/explorer/configuration.mdx b/website/versioned_docs/version-0.31.2/explorer/configuration.mdx index 2c041f1650..4aa53ed750 100644 --- a/website/versioned_docs/version-0.31.2/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.31.2/explorer/configuration.mdx @@ -109,7 +109,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.31.2/gitops-run/gitops-run-get-started.mdx b/website/versioned_docs/version-0.31.2/gitops-run/gitops-run-get-started.mdx index e2020d2a68..a5245acdc3 100644 --- a/website/versioned_docs/version-0.31.2/gitops-run/gitops-run-get-started.mdx +++ b/website/versioned_docs/version-0.31.2/gitops-run/gitops-run-get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.31.2/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.31.2/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.31.2/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.31.2/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.31.2/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.31.2/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.31.2/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.31.2/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.31.2/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.31.2/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.31.2/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.31.2/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.31.2/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.31.2/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.31.2/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.31.2/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.31.2/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.31.2/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.31.2/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.31.2/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.31.2/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.31.2/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.31.2/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.31.2/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.31.2/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.31.2/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.31.2/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.31.2/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.31.2/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.31.2/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.31.2/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.31.2/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.31.2/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.31.2/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.31.2/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.31.2/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.31.2/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.31.2/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.31.2/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.31.2/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.31.2/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.31.2/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.31.2/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.31.2/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.31.2/policy/getting-started.mdx b/website/versioned_docs/version-0.31.2/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.31.2/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.31.2/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.31.2/policy/policy-configuration.mdx b/website/versioned_docs/version-0.31.2/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.31.2/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.31.2/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.31.2/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.31.2/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.31.2/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.31.2/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.31.2/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.31.2/progressive-delivery/progressive-delivery-flagger-install.mdx index b0998cd0e7..44b249c215 100644 --- a/website/versioned_docs/version-0.31.2/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.31.2/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -77,7 +77,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -167,7 +168,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -260,7 +262,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -325,7 +328,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -382,7 +386,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -566,7 +571,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.31.2/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.31.2/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.31.2/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.31.2/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.31.2/secrets/getting-started.mdx b/website/versioned_docs/version-0.31.2/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.31.2/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.31.2/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.31.2/secrets/setup-eso.mdx b/website/versioned_docs/version-0.31.2/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.31.2/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.31.2/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.31.2/secrets/setup-sops.mdx b/website/versioned_docs/version-0.31.2/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.31.2/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.31.2/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.31.2/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.31.2/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/versioned_docs/version-0.31.2/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.31.2/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.31.2/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.31.2/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.31.2/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.31.2/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.32.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.32.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.32.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.32.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise.mdx index 6d0a59324d..c0812abd81 100644 --- a/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise.mdx @@ -243,7 +243,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -357,7 +358,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -405,7 +407,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -781,7 +784,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1046,7 +1050,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/versioned_docs/version-0.32.0/explorer/configuration.mdx b/website/versioned_docs/version-0.32.0/explorer/configuration.mdx index 2c041f1650..4aa53ed750 100644 --- a/website/versioned_docs/version-0.32.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.32.0/explorer/configuration.mdx @@ -109,7 +109,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -124,7 +125,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -150,7 +152,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -173,7 +176,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.32.0/gitops-run/gitops-run-get-started.mdx b/website/versioned_docs/version-0.32.0/gitops-run/gitops-run-get-started.mdx index f3398b4ba0..11c61d18f7 100644 --- a/website/versioned_docs/version-0.32.0/gitops-run/gitops-run-get-started.mdx +++ b/website/versioned_docs/version-0.32.0/gitops-run/gitops-run-get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.32.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.32.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.32.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.32.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.32.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.32.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.32.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.32.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.32.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.32.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.32.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.32.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.32.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.32.0/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.32.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.32.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.32.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.32.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.32.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.32.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.32.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.32.0/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.32.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.32.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.32.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.32.0/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.32.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.32.0/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.32.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.32.0/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.32.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.32.0/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.32.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.32.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.32.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.32.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.32.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.32.0/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.32.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.32.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.32.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.32.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.32.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.32.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.32.0/policy/getting-started.mdx b/website/versioned_docs/version-0.32.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.32.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.32.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.32.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.32.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.32.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.32.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.32.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.32.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.32.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.32.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.32.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.32.0/progressive-delivery/progressive-delivery-flagger-install.mdx index fec02a889c..2e32383c10 100644 --- a/website/versioned_docs/version-0.32.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.32.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -83,7 +83,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -173,7 +174,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -266,7 +268,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -331,7 +334,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -395,7 +399,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -439,7 +444,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -534,7 +540,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -718,7 +725,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.32.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.32.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.32.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.32.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.32.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.32.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.32.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.32.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.32.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.32.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.32.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.32.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.32.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.32.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.32.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.32.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.32.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.32.0/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/versioned_docs/version-0.32.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.32.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.32.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.32.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.32.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.32.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.33.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.33.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.33.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.33.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise.mdx index 638c265397..c8cfc41522 100644 --- a/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise.mdx @@ -248,7 +248,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -362,7 +363,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -410,7 +412,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -786,7 +789,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1051,7 +1055,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/versioned_docs/version-0.33.0/explorer/configuration.mdx b/website/versioned_docs/version-0.33.0/explorer/configuration.mdx index d85b49d2a5..58801fb387 100644 --- a/website/versioned_docs/version-0.33.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.33.0/explorer/configuration.mdx @@ -114,7 +114,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -129,7 +130,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -155,7 +157,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -178,7 +181,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.33.0/gitops-run/gitops-run-get-started.mdx b/website/versioned_docs/version-0.33.0/gitops-run/gitops-run-get-started.mdx index f3398b4ba0..11c61d18f7 100644 --- a/website/versioned_docs/version-0.33.0/gitops-run/gitops-run-get-started.mdx +++ b/website/versioned_docs/version-0.33.0/gitops-run/gitops-run-get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.33.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.33.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.33.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.33.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.33.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.33.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.33.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.33.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.33.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.33.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.33.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.33.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.33.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.33.0/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.33.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.33.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.33.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.33.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.33.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.33.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.33.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.33.0/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.33.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.33.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.33.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.33.0/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.33.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.33.0/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.33.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.33.0/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.33.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.33.0/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.33.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.33.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.33.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.33.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.33.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.33.0/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.33.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.33.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.33.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.33.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.33.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.33.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.33.0/policy/getting-started.mdx b/website/versioned_docs/version-0.33.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.33.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.33.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.33.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.33.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.33.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.33.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.33.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.33.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.33.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.33.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.33.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.33.0/progressive-delivery/progressive-delivery-flagger-install.mdx index f0b866be90..5f80d3413d 100644 --- a/website/versioned_docs/version-0.33.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.33.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -82,7 +82,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -172,7 +173,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -265,7 +267,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -330,7 +333,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -394,7 +398,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -438,7 +443,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -533,7 +539,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -717,7 +724,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.33.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.33.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.33.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.33.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.33.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.33.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.33.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.33.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.33.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.33.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.33.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.33.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.33.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.33.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.33.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.33.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.33.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.33.0/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/versioned_docs/version-0.33.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.33.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.33.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.33.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.33.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.33.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.34.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.34.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.34.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.34.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise.mdx index 3cd6fd974d..14587e04a2 100644 --- a/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise.mdx @@ -248,7 +248,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -360,7 +361,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -408,7 +410,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -784,7 +787,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1049,7 +1053,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/versioned_docs/version-0.34.0/explorer/configuration.mdx b/website/versioned_docs/version-0.34.0/explorer/configuration.mdx index d85b49d2a5..58801fb387 100644 --- a/website/versioned_docs/version-0.34.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.34.0/explorer/configuration.mdx @@ -114,7 +114,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -129,7 +130,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -155,7 +157,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -178,7 +181,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.34.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.34.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.34.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.34.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.34.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.34.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.34.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.34.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.34.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.34.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.34.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.34.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.34.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.34.0/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.34.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.34.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.34.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.34.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.34.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.34.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.34.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.34.0/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.34.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.34.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.34.0/operations/monitoring.mdx b/website/versioned_docs/version-0.34.0/operations/monitoring.mdx index aea0e70107..4e24ce43ab 100644 --- a/website/versioned_docs/version-0.34.0/operations/monitoring.mdx +++ b/website/versioned_docs/version-0.34.0/operations/monitoring.mdx @@ -24,7 +24,8 @@ This setup follows [Flux Monitoring](https://fluxcd.io/flux/monitoring/metrics/) 1. Install [Kube Prometheus Stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack). -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1 @@ -64,7 +65,8 @@ spec: 2. Enable Prometheus Metrics Configuration happens during releasing as shown below. -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml --- @@ -85,7 +87,8 @@ spec: 3. Deploy Weave GitOps Monitoring Config -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1 diff --git a/website/versioned_docs/version-0.34.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.34.0/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.34.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.34.0/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.34.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.34.0/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.34.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.34.0/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.34.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.34.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.34.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.34.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.34.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.34.0/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.34.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.34.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.34.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.34.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.34.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.34.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.34.0/policy/getting-started.mdx b/website/versioned_docs/version-0.34.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.34.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.34.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.34.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.34.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.34.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.34.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.34.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.34.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.34.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.34.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.34.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.34.0/progressive-delivery/progressive-delivery-flagger-install.mdx index f0b866be90..5f80d3413d 100644 --- a/website/versioned_docs/version-0.34.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.34.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -82,7 +82,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -172,7 +173,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -265,7 +267,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -330,7 +333,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -394,7 +398,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -438,7 +443,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -533,7 +539,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -717,7 +724,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.34.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.34.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.34.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.34.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.34.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.34.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.34.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.34.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.34.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.34.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.34.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.34.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.34.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.34.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.34.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.34.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.34.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.34.0/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/versioned_docs/version-0.34.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.34.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.34.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.34.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.34.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.34.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.35.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.35.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.35.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.35.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise.mdx index 3cd6fd974d..14587e04a2 100644 --- a/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise.mdx @@ -248,7 +248,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -360,7 +361,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -408,7 +410,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -784,7 +787,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1049,7 +1053,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/versioned_docs/version-0.35.0/explorer/configuration.mdx b/website/versioned_docs/version-0.35.0/explorer/configuration.mdx index d85b49d2a5..58801fb387 100644 --- a/website/versioned_docs/version-0.35.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.35.0/explorer/configuration.mdx @@ -114,7 +114,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -129,7 +130,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -155,7 +157,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -178,7 +181,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.35.0/gitops-run/gitops-run-get-started.mdx b/website/versioned_docs/version-0.35.0/gitops-run/gitops-run-get-started.mdx index f3398b4ba0..11c61d18f7 100644 --- a/website/versioned_docs/version-0.35.0/gitops-run/gitops-run-get-started.mdx +++ b/website/versioned_docs/version-0.35.0/gitops-run/gitops-run-get-started.mdx @@ -166,7 +166,8 @@ You should see three files now exist in your `./podinfo` directory. Save the contents of the following files to the `./podinfo` directory. -
./podinfo/namespace.yaml +
+./podinfo/namespace.yaml ```yaml --- @@ -178,7 +179,8 @@ metadata:
-
./podinfo/podinfo-source.yaml +
+./podinfo/podinfo-source.yaml ```yaml --- @@ -194,7 +196,8 @@ spec:
-
./podinfo/podinfo-helmrelease.yaml +
+./podinfo/podinfo-helmrelease.yaml ```yaml --- diff --git a/website/versioned_docs/version-0.35.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.35.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.35.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.35.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.35.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.35.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.35.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.35.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.35.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.35.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.35.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.35.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.35.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.35.0/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.35.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.35.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.35.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.35.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.35.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.35.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.35.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.35.0/open-source/getting-started/deploy-OSS.mdx index 080ddcdef2..1fffede10d 100644 --- a/website/versioned_docs/version-0.35.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.35.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.35.0/operations/monitoring.mdx b/website/versioned_docs/version-0.35.0/operations/monitoring.mdx index 095619b8b6..95b328da62 100644 --- a/website/versioned_docs/version-0.35.0/operations/monitoring.mdx +++ b/website/versioned_docs/version-0.35.0/operations/monitoring.mdx @@ -55,7 +55,8 @@ This setup follows [Flux Monitoring](https://fluxcd.io/flux/monitoring/metrics/) 1. You have [enabled](#setup) the monitoring server with the metrics endpoint. 2. Install [Kube Prometheus Stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack). -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1 @@ -94,7 +95,8 @@ spec: 3. Deploy Weave GitOps Monitoring Config -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1 diff --git a/website/versioned_docs/version-0.35.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.35.0/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.35.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.35.0/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.35.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.35.0/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.35.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.35.0/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.35.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.35.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.35.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.35.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.35.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.35.0/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.35.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.35.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.35.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.35.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.35.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.35.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.35.0/policy/getting-started.mdx b/website/versioned_docs/version-0.35.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.35.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.35.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.35.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.35.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.35.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.35.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.35.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.35.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.35.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.35.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.35.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.35.0/progressive-delivery/progressive-delivery-flagger-install.mdx index f0b866be90..5f80d3413d 100644 --- a/website/versioned_docs/version-0.35.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.35.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -82,7 +82,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -172,7 +173,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -265,7 +267,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -330,7 +333,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -394,7 +398,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -438,7 +443,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -533,7 +539,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -717,7 +724,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.35.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.35.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.35.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.35.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.35.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.35.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.35.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.35.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.35.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.35.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.35.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.35.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.35.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.35.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.35.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.35.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.35.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.35.0/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/versioned_docs/version-0.35.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.35.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.35.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.35.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.35.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.35.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.36.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.36.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.36.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.36.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise.mdx index 3cd6fd974d..14587e04a2 100644 --- a/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise.mdx @@ -248,7 +248,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -360,7 +361,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -408,7 +410,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -784,7 +787,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1049,7 +1053,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/versioned_docs/version-0.36.0/explorer/configuration.mdx b/website/versioned_docs/version-0.36.0/explorer/configuration.mdx index d85b49d2a5..58801fb387 100644 --- a/website/versioned_docs/version-0.36.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.36.0/explorer/configuration.mdx @@ -114,7 +114,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -129,7 +130,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -155,7 +157,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -178,7 +181,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.36.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.36.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.36.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.36.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.36.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.36.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.36.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.36.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.36.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.36.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.36.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.36.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.36.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.36.0/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.36.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.36.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.36.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.36.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.36.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.36.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.36.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.36.0/open-source/getting-started/deploy-OSS.mdx index 8997f2a22b..6f6acf2771 100644 --- a/website/versioned_docs/version-0.36.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.36.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.36.0/operations/monitoring.mdx b/website/versioned_docs/version-0.36.0/operations/monitoring.mdx index 5275110618..87a1d0b273 100644 --- a/website/versioned_docs/version-0.36.0/operations/monitoring.mdx +++ b/website/versioned_docs/version-0.36.0/operations/monitoring.mdx @@ -46,7 +46,8 @@ This setup follows the same [monitoring approach as Flux](https://fluxcd.io/flux 1. [Enable](#setup) the monitoring server with the metrics endpoint. 2. Install [Kube Prometheus Stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack). -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1 @@ -85,7 +86,8 @@ spec: 3. Deploy Weave GitOps Monitoring Config -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1 diff --git a/website/versioned_docs/version-0.36.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.36.0/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.36.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.36.0/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.36.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.36.0/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.36.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.36.0/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.36.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.36.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.36.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.36.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.36.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.36.0/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.36.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.36.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.36.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.36.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.36.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.36.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.36.0/policy/getting-started.mdx b/website/versioned_docs/version-0.36.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.36.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.36.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.36.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.36.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.36.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.36.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.36.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.36.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.36.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.36.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.36.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.36.0/progressive-delivery/progressive-delivery-flagger-install.mdx index f0b866be90..5f80d3413d 100644 --- a/website/versioned_docs/version-0.36.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.36.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -82,7 +82,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -172,7 +173,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -265,7 +267,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -330,7 +333,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -394,7 +398,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -438,7 +443,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -533,7 +539,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -717,7 +724,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.36.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.36.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.36.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.36.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.36.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.36.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.36.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.36.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.36.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.36.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.36.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.36.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.36.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.36.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.36.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.36.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.36.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.36.0/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/versioned_docs/version-0.36.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.36.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.36.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.36.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.36.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.36.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.37.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.37.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.37.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.37.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise.mdx index a1b62b9211..64e518284e 100644 --- a/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise.mdx @@ -254,7 +254,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -366,7 +367,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -414,7 +416,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -790,7 +793,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1055,7 +1059,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/versioned_docs/version-0.37.0/explorer/configuration.mdx b/website/versioned_docs/version-0.37.0/explorer/configuration.mdx index d85b49d2a5..58801fb387 100644 --- a/website/versioned_docs/version-0.37.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.37.0/explorer/configuration.mdx @@ -114,7 +114,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -129,7 +130,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -155,7 +157,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -178,7 +181,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.37.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.37.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.37.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.37.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.37.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.37.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.37.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.37.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.37.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.37.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.37.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.37.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.37.0/guides/configuring-oidc-with-keycloak.mdx b/website/versioned_docs/version-0.37.0/guides/configuring-oidc-with-keycloak.mdx index b3ba33f739..afddb7cacb 100644 --- a/website/versioned_docs/version-0.37.0/guides/configuring-oidc-with-keycloak.mdx +++ b/website/versioned_docs/version-0.37.0/guides/configuring-oidc-with-keycloak.mdx @@ -193,7 +193,8 @@ To configure Weave GitOps for OIDC authentication via Keycloak, we need to confi - the `claimGroups` to `groups` to work with our mapper, mapping from roles->groups - the `claimUsername` to `sub` -
Expand to see secret definition +
+Expand to see secret definition ```yaml apiVersion: v1 @@ -221,7 +222,8 @@ The following example assumes that the ClusterRole `wego-admin-cluster-role` and in the `wego-admin` group within Keycloak admin access. See the [recommendations on setting up RBAC](../../enterprise/getting-started/install-enterprise/#recommended-rbac-configuration) for details. -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.37.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.37.0/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.37.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.37.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.37.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.37.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.37.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.37.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.37.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.37.0/open-source/getting-started/deploy-OSS.mdx index 8997f2a22b..6f6acf2771 100644 --- a/website/versioned_docs/version-0.37.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.37.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.37.0/operations/monitoring.mdx b/website/versioned_docs/version-0.37.0/operations/monitoring.mdx index 5275110618..87a1d0b273 100644 --- a/website/versioned_docs/version-0.37.0/operations/monitoring.mdx +++ b/website/versioned_docs/version-0.37.0/operations/monitoring.mdx @@ -46,7 +46,8 @@ This setup follows the same [monitoring approach as Flux](https://fluxcd.io/flux 1. [Enable](#setup) the monitoring server with the metrics endpoint. 2. Install [Kube Prometheus Stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack). -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1 @@ -85,7 +86,8 @@ spec: 3. Deploy Weave GitOps Monitoring Config -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1 diff --git a/website/versioned_docs/version-0.37.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.37.0/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.37.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.37.0/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.37.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.37.0/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.37.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.37.0/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.37.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.37.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.37.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.37.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.37.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.37.0/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.37.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.37.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.37.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.37.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.37.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.37.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.37.0/policy/getting-started.mdx b/website/versioned_docs/version-0.37.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.37.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.37.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.37.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.37.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.37.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.37.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.37.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.37.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.37.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.37.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.37.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.37.0/progressive-delivery/progressive-delivery-flagger-install.mdx index f0b866be90..5f80d3413d 100644 --- a/website/versioned_docs/version-0.37.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.37.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -82,7 +82,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -172,7 +173,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -265,7 +267,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -330,7 +333,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -394,7 +398,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -438,7 +443,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -533,7 +539,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -717,7 +724,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.37.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.37.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.37.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.37.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.37.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.37.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.37.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.37.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.37.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.37.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.37.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.37.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.37.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.37.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.37.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.37.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.37.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.37.0/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/versioned_docs/version-0.37.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.37.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.37.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.37.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.37.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.37.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 diff --git a/website/versioned_docs/version-0.38.0/cluster-management/deploying-capa-eks.mdx b/website/versioned_docs/version-0.38.0/cluster-management/deploying-capa-eks.mdx index 83015e1a25..4e55226de1 100644 --- a/website/versioned_docs/version-0.38.0/cluster-management/deploying-capa-eks.mdx +++ b/website/versioned_docs/version-0.38.0/cluster-management/deploying-capa-eks.mdx @@ -60,7 +60,8 @@ import WegoAdmin from "!!raw-loader!./assets/rbac/wego-admin.yaml"; )} -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see full yaml +
+Expand to see full yaml Expand to see role manifests +
+ Expand to see role manifests ```yaml --- @@ -104,7 +105,8 @@ Here's how to create a kubeconfig secret. 4. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash @@ -216,7 +218,8 @@ Download the config with: Then update the `GITHUB_USER` variable to point to your repository -
Expand to see full yaml +
+Expand to see full yaml -
Expand to see full template yaml +
+Expand to see full template yaml Expand to see manifest +
+Expand to see manifest ```yaml --- diff --git a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-airgap.mdx b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-airgap.mdx index 62942d9b1f..08f36e16d2 100644 --- a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-airgap.mdx +++ b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-airgap.mdx @@ -80,7 +80,8 @@ We are going to install [ChartMuseum](https://chartmuseum.com/) via Flux. Remember to also install helm plugin [cm-push](https://github.com/chartmuseum/helm-push). -
Expand to see installation yaml +
+Expand to see installation yaml ```yaml --- @@ -190,7 +191,8 @@ EOF ``` Execute `make` using the following makefile to intialise CAPI in your cluster: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile .PHONY := capi @@ -237,7 +239,8 @@ capi-cluster: Apply the following example manifest to deploy the Terraform Controller: -
Expand to see file contents +
+Expand to see file contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1beta2 @@ -278,7 +281,8 @@ spec: Update the following manifest to your context. -
Expand to see file contents +
+Expand to see file contents ```yaml {4-7,19-20} --- @@ -422,7 +426,8 @@ ghcr.io/fluxcd/notification-controller:v0.25.2 This section guides you to push installed artifacts to your private registry. Here's a Makefile to help you with each stage: -
Expand to see Makefile contents +
+Expand to see Makefile contents ```makefile {4-6} .PHONY := all @@ -493,7 +498,8 @@ Follow the instructions to install WGE with the following considerations: An example of how it would look for Weave GitOps Enterprise is shown below. -
Expand to view example WGE manifest +
+Expand to view example WGE manifest ```yaml title="weave-gitops-enterprise.yaml" {21-24,32} --- diff --git a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise.mdx index e0130f121a..4bbb072598 100644 --- a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise.mdx @@ -256,7 +256,8 @@ kubectl create secret generic github-client \ Use `HelmRepository` and `HelmRelease` objects to let Flux deploy everything. -
Expand to see resource manifests +
+Expand to see resource manifests ```yaml --- @@ -368,7 +369,8 @@ the user. Based on these groups, we can bind roles to groups: -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- @@ -416,7 +418,8 @@ rules: In the same way, we can bind cluster roles to a group: -
Expand to see group cluster role bindings +
+Expand to see group cluster role bindings ```yaml --- @@ -792,7 +795,8 @@ cluster client (and vice versa). The yaml to configure these permissions would look roughly like: -
Expand to see example RBAC +
+Expand to see example RBAC ```yaml # Admin cluster role @@ -1057,7 +1061,8 @@ Download the helm-release to `clusters/management/weave-gitops-enterprise.yaml`. import ExampleWGE from "../../assets/example-enterprise-helm.yaml"; import ExampleWGEContent from "!!raw-loader!../../assets/example-enterprise-helm.yaml"; -
Expand to see file contents +
+Expand to see file contents Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: v1 @@ -77,7 +78,8 @@ metadata: 2. Create a roles file: -
Expand to see role manifests +
+Expand to see role manifests ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -124,7 +126,8 @@ Kubernetes 1.24+ [will not create secrets for Service Accounts for you](https:// 6. Create a kubeconfig secret. We'll use a helper script to generate the kubeconfig, and then save it into `static-kubeconfig.sh`: -
Expand to see script +
+ Expand to see script ```bash title="static-kubeconfig.sh" #!/bin/bash diff --git a/website/versioned_docs/version-0.38.0/explorer/configuration.mdx b/website/versioned_docs/version-0.38.0/explorer/configuration.mdx index d85b49d2a5..58801fb387 100644 --- a/website/versioned_docs/version-0.38.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.38.0/explorer/configuration.mdx @@ -114,7 +114,8 @@ To configure collection, you would need to extend this configuration with the fo 1. Create a ServiceAccount for the one that you specified in your [setup](#setup) `.spec.values.explorer.collector.serviceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: v1 @@ -129,7 +130,8 @@ metadata: 2. Create a ClusterRole with the permissions to watch the supported resources. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -155,7 +157,8 @@ rules: 3. Create a ClusterRolebinding to assign previous ClusterRole to the created collector `ServiceAccount`. -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 @@ -178,7 +181,8 @@ If you want the collector to watch a particular namespace use a RoleBinding inst 4. Extend impersonation rules to allow service account impersonation for ServiceAccount `collector` -
Expand to see an example +
+Expand to see an example ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.38.0/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.38.0/gitops-templates/profiles.mdx index 77a4e6d06d..640f91702e 100644 --- a/website/versioned_docs/version-0.38.0/gitops-templates/profiles.mdx +++ b/website/versioned_docs/version-0.38.0/gitops-templates/profiles.mdx @@ -51,7 +51,8 @@ Keys available in the `spec.charts.items` entries and the template variables ava | `required` | (default=false) Allow the user to de-select this profile | | `editable` | (default=false) Allow the user to edit the values.yaml of this profile | -
Expand for a complete yaml example +
+Expand for a complete yaml example ```yaml spec: diff --git a/website/versioned_docs/version-0.38.0/gitops-templates/quickstart-templates.mdx b/website/versioned_docs/version-0.38.0/gitops-templates/quickstart-templates.mdx index c868465162..296f60c49f 100644 --- a/website/versioned_docs/version-0.38.0/gitops-templates/quickstart-templates.mdx +++ b/website/versioned_docs/version-0.38.0/gitops-templates/quickstart-templates.mdx @@ -20,7 +20,8 @@ github repo. To get started, add the following `HelmRelease` object to your Weave GitOps Enterprise configuration repo for your management cluster. -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.38.0/gitops-templates/repo-rendered-paths.mdx b/website/versioned_docs/version-0.38.0/gitops-templates/repo-rendered-paths.mdx index cb3f3d7866..99292bad21 100644 --- a/website/versioned_docs/version-0.38.0/gitops-templates/repo-rendered-paths.mdx +++ b/website/versioned_docs/version-0.38.0/gitops-templates/repo-rendered-paths.mdx @@ -22,7 +22,8 @@ The path for rendered resources is configured via the - The path can be templated using params ::: -
Expand to see example +
+Expand to see example ```yaml spec: diff --git a/website/versioned_docs/version-0.38.0/guides/configuring-oidc-with-keycloak.mdx b/website/versioned_docs/version-0.38.0/guides/configuring-oidc-with-keycloak.mdx index b3ba33f739..afddb7cacb 100644 --- a/website/versioned_docs/version-0.38.0/guides/configuring-oidc-with-keycloak.mdx +++ b/website/versioned_docs/version-0.38.0/guides/configuring-oidc-with-keycloak.mdx @@ -193,7 +193,8 @@ To configure Weave GitOps for OIDC authentication via Keycloak, we need to confi - the `claimGroups` to `groups` to work with our mapper, mapping from roles->groups - the `claimUsername` to `sub` -
Expand to see secret definition +
+Expand to see secret definition ```yaml apiVersion: v1 @@ -221,7 +222,8 @@ The following example assumes that the ClusterRole `wego-admin-cluster-role` and in the `wego-admin` group within Keycloak admin access. See the [recommendations on setting up RBAC](../../enterprise/getting-started/install-enterprise/#recommended-rbac-configuration) for details. -
Expand to see group role bindings +
+Expand to see group role bindings ```yaml --- diff --git a/website/versioned_docs/version-0.38.0/guides/fluxga-upgrade.mdx b/website/versioned_docs/version-0.38.0/guides/fluxga-upgrade.mdx index 7969cb4228..6ff966b3af 100644 --- a/website/versioned_docs/version-0.38.0/guides/fluxga-upgrade.mdx +++ b/website/versioned_docs/version-0.38.0/guides/fluxga-upgrade.mdx @@ -99,7 +99,8 @@ First, we ensure any new clusters are bootstrapped with Flux GA. Then we'll upgr `ClusterBootstrapConfig` will most often contain an invocation of `flux bootstrap`. Make sure the image is using `v2`. -
Expand to see an example +
+Expand to see an example ```patch diff --git a/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml b/tools/dev-resources/user-guide/cluster-bootstrap-config.yaml diff --git a/website/versioned_docs/version-0.38.0/open-source/getting-started/aws-marketplace.mdx b/website/versioned_docs/version-0.38.0/open-source/getting-started/aws-marketplace.mdx index bbb9c98422..da83a323f4 100644 --- a/website/versioned_docs/version-0.38.0/open-source/getting-started/aws-marketplace.mdx +++ b/website/versioned_docs/version-0.38.0/open-source/getting-started/aws-marketplace.mdx @@ -31,7 +31,8 @@ If you do not have a cluster on EKS, you can use [`eksctl`](https://github.com/w Copy the contents of the sample file below into `cluster-config.yaml` and replace the placeholder values with your settings. See the [`eksctl` documentation](https://eksctl.io/) for more configuration options. -
Expand for file contents +
+Expand for file contents ```yaml title="cluster-config.yaml" --- @@ -87,7 +88,8 @@ Use this `eksctl` configuration below (replacing the placeholder values) to: Save the example below as `oidc-config.yaml` -
Expand for file contents +
+Expand for file contents ```yaml title="oidc-config.yaml" --- diff --git a/website/versioned_docs/version-0.38.0/open-source/getting-started/deploy-OSS.mdx b/website/versioned_docs/version-0.38.0/open-source/getting-started/deploy-OSS.mdx index 8997f2a22b..6f6acf2771 100644 --- a/website/versioned_docs/version-0.38.0/open-source/getting-started/deploy-OSS.mdx +++ b/website/versioned_docs/version-0.38.0/open-source/getting-started/deploy-OSS.mdx @@ -78,7 +78,8 @@ To customize a deployment from a repository you don’t control, you can use Flu 1. Add the `patches` section as shown below to the field spec of your `podinfo-kustomization.yaml` file so it looks like this: -
Expand to see Kustomization patches +
+ Expand to see Kustomization patches ```yaml title="./clusters/management/podinfo-kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.38.0/operations/monitoring.mdx b/website/versioned_docs/version-0.38.0/operations/monitoring.mdx index 5275110618..87a1d0b273 100644 --- a/website/versioned_docs/version-0.38.0/operations/monitoring.mdx +++ b/website/versioned_docs/version-0.38.0/operations/monitoring.mdx @@ -46,7 +46,8 @@ This setup follows the same [monitoring approach as Flux](https://fluxcd.io/flux 1. [Enable](#setup) the monitoring server with the metrics endpoint. 2. Install [Kube Prometheus Stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack). -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: source.toolkit.fluxcd.io/v1 @@ -85,7 +86,8 @@ spec: 3. Deploy Weave GitOps Monitoring Config -
Expand to see manifest contents +
+Expand to see manifest contents ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1 diff --git a/website/versioned_docs/version-0.38.0/pipelines/pipelines-getting-started.mdx b/website/versioned_docs/version-0.38.0/pipelines/pipelines-getting-started.mdx index 1b11987d2a..eabdf0b6f4 100644 --- a/website/versioned_docs/version-0.38.0/pipelines/pipelines-getting-started.mdx +++ b/website/versioned_docs/version-0.38.0/pipelines/pipelines-getting-started.mdx @@ -28,7 +28,8 @@ A pipeline allows you to define the route your application is taking, so that yo You can define a delivery pipeline using a `Pipeline` custom resource. An example of such a CR is shown here: -
Expand to view +
+Expand to view ```yaml --- diff --git a/website/versioned_docs/version-0.38.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.38.0/pipelines/pipelines-templates.mdx index 1220e801c7..4d7f32c7a3 100644 --- a/website/versioned_docs/version-0.38.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.38.0/pipelines/pipelines-templates.mdx @@ -48,7 +48,8 @@ This default template is shipped with Weave GitOps Enterprise to help you get st For flexibility, this allows the template user to specify the names of the clusters where the application is deployed, and to vary the namespace per cluster. This works even in a tenancy model where environments coexist on the same cluster and use namespaces for isolation. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -122,7 +123,8 @@ spec: This example extends the above to add a promotion strategy. In this case, it will raise a pull request to update the application version in subsequent environments. -
Expand to view example template +
+Expand to view example template ```yaml --- @@ -233,7 +235,8 @@ For the `Alert`, this template filters events to detect when an update has occur For the `Provider`, this template uses authenticated (HMAC) communication to the promotion endpoint, where a secret must be present on both the management cluster and the leaf cluster(s). For simplicity's sake, you can use a `generic` provider instead; this will not require the secret. -
Expand to view example template +
+Expand to view example template ```yaml --- diff --git a/website/versioned_docs/version-0.38.0/pipelines/pipelines-with-jenkins.mdx b/website/versioned_docs/version-0.38.0/pipelines/pipelines-with-jenkins.mdx index 07d97f4092..893ba403e6 100644 --- a/website/versioned_docs/version-0.38.0/pipelines/pipelines-with-jenkins.mdx +++ b/website/versioned_docs/version-0.38.0/pipelines/pipelines-with-jenkins.mdx @@ -36,7 +36,8 @@ as a "Post content parameters". ![extract reason from the post content](img/pipelines-jenkins/post-content-param.png) -
Expand to see an example Promotion Event payload +
+ Expand to see an example Promotion Event payload ```json { diff --git a/website/versioned_docs/version-0.38.0/pipelines/promoting-applications.mdx b/website/versioned_docs/version-0.38.0/pipelines/promoting-applications.mdx index fc5a87180c..535c94b386 100644 --- a/website/versioned_docs/version-0.38.0/pipelines/promoting-applications.mdx +++ b/website/versioned_docs/version-0.38.0/pipelines/promoting-applications.mdx @@ -371,21 +371,24 @@ app-promotion-credentials Opaque 1 21m 1. **Create a user account for pull request changes**: this user context would be used to do any git provider operation, and from the security and auditing perspectives, you don't want to impersonate a real user for it. -
Expand to see example +
+Expand to see example ![using bot account](img/bot-account.png)
2. **Do not use long-live tokens**: set an expiration date and rotate them according to your security policy. -
Expand to see example +
+Expand to see example ![create token with expiration](img/create-token-with-expiration.png)
3. **Honour the least privilege principle**: avoid having high privilege tokens. Restrict the token to your just your repo and to just the operations required. -
Expand to see example +
+Expand to see example For example, if the case of GitHub, use [fine-grained tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) to only allow access to the single repo that your configuration manifests exist. @@ -397,7 +400,8 @@ allow access to the single repo that your configuration manifests exist. - Only the ones that are required are present. - Tokens close to their expiration date are cycled. -
Expand to see example +
+Expand to see example For example, using github and fine-grained tokens you [could do so](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/#approving-and-auditing-personal-access-tokens). @@ -463,7 +467,8 @@ In the journey of creating a pull request, there are different secrets involved: Create a Kubernetes secret with the previous data. -
Expand to see example +
+Expand to see example ```shell # example to use git over https with basic auth and pat @@ -582,7 +587,8 @@ Promotion notifications from leaf clusters should now be forwarded via the notif The supported strategies mentioned above, do not require any user interaction when handling promotions. However, there is often a need for a human operator to manually approve a promotion to the next environment. To achieve that, set the `spec.promotion.manual` key to `true`. -
Expand to see example +
+Expand to see example ```yaml {8} apiVersion: pipelines.weave.works/v1alpha1 diff --git a/website/versioned_docs/version-0.38.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.38.0/policy/commit-time-checks.mdx index 207920ea08..9883645d8e 100644 --- a/website/versioned_docs/version-0.38.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.38.0/policy/commit-time-checks.mdx @@ -12,7 +12,8 @@ Weave GitOps Enterprise enables developers and operators to check policy violati Weave GitOps Enterprise offer a policy engine image that can be used to perform commit/build time checks.The image can be found on Docker Hub under the name: `weaveworks/weave-iac-validator:v1.1`. -
Expand to view of the usage options +
+Expand to view of the usage options ```bash USAGE: diff --git a/website/versioned_docs/version-0.38.0/policy/getting-started.mdx b/website/versioned_docs/version-0.38.0/policy/getting-started.mdx index 7bb944f16f..1dab6a1229 100644 --- a/website/versioned_docs/version-0.38.0/policy/getting-started.mdx +++ b/website/versioned_docs/version-0.38.0/policy/getting-started.mdx @@ -34,7 +34,8 @@ To install the policy agent on a leaf cluster, you should select the `weave-poli You should then configure the `values.yaml` to pull the policies from your repo into the cluster. This is done by configuring the `policySource` section. If your policy library repo is private, you will also need to reference the `Secret` that contains the repo credentials. This is usually the secret you created while bootstrapping Flux on the management cluster and is copied to your leaf cluster during creation. -
Expand to see an example that creates a new git source +
+Expand to see an example that creates a new git source ```yaml policySource: @@ -46,7 +47,8 @@ policySource: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml policySource: @@ -73,7 +75,8 @@ Now you have a provisioned cluster with these policies enforced by the policy ag Now let's try to deploy a Kubernetes deployment that violates the `Container Image Pull Policy` which is one of the enforced policies. This policy is violated when the container's `imagePullPolicy` is not set to `Always`. -
Expand for an example of a violating deployment +
+Expand for an example of a violating deployment ```yaml apiVersion: apps/v1 diff --git a/website/versioned_docs/version-0.38.0/policy/policy-configuration.mdx b/website/versioned_docs/version-0.38.0/policy/policy-configuration.mdx index 522e089e8c..b753321c12 100644 --- a/website/versioned_docs/version-0.38.0/policy/policy-configuration.mdx +++ b/website/versioned_docs/version-0.38.0/policy/policy-configuration.mdx @@ -16,7 +16,8 @@ The `PolicyConfig` CRD allows us to do that without duplicating policies by over The PolicyConfig CRD consists of two sections 1) `match` used to specify the target of this PolicyConfig and 2) `config` used to specify the policy parameters that will override the orginal policy parameters. -
Expand to see a PolicyConfig example +
+Expand to see a PolicyConfig example ```yaml apiVersion: pac.weave.works/v2beta2 @@ -111,7 +112,8 @@ Those are the possible targets from lowest to highest precendence: We have a Kustomization application `app-a` and deployment `deployment-1` which is part of this application. -
Expand to see manifests +
+Expand to see manifests ```yaml apiVersion: pac.weave.works/v2beta2 diff --git a/website/versioned_docs/version-0.38.0/policy/weave-policy-profile.mdx b/website/versioned_docs/version-0.38.0/policy/weave-policy-profile.mdx index 7a9a911751..6cf069a267 100644 --- a/website/versioned_docs/version-0.38.0/policy/weave-policy-profile.mdx +++ b/website/versioned_docs/version-0.38.0/policy/weave-policy-profile.mdx @@ -16,7 +16,8 @@ Weave policy profile provides policies to automate the enforcement of best pract The profile configuration contains two main sections `policySource` to configure the source for deploying policies and `policy-agent` to configure the policy agent. -
Expand for an example of the profile values file +
+Expand for an example of the profile values file ```yaml policy-agent: diff --git a/website/versioned_docs/version-0.38.0/progressive-delivery/progressive-delivery-flagger-install.mdx b/website/versioned_docs/version-0.38.0/progressive-delivery/progressive-delivery-flagger-install.mdx index f0b866be90..5f80d3413d 100644 --- a/website/versioned_docs/version-0.38.0/progressive-delivery/progressive-delivery-flagger-install.mdx +++ b/website/versioned_docs/version-0.38.0/progressive-delivery/progressive-delivery-flagger-install.mdx @@ -82,7 +82,8 @@ Let's add the three manifests for Linkerd components under the `./linkerd` direc - A `HelmRelease` resource to install the latest version of Linkerd from the `HelmRepository` -
Expand to see and copy-paste the three Linkerd manifests to add +
+Expand to see and copy-paste the three Linkerd manifests to add ```yaml title="linkerd/namespace.yaml" --- @@ -172,7 +173,8 @@ Next, add the following manifests. The first file instructs Kustomize to patch a `HelmRelease` manifests. The second file is a `Kustomization` that references all the other `linkerd` resource files. -
Expand to see the Linkerd Kustomization manifests +
+Expand to see the Linkerd Kustomization manifests ```yaml title="linkerd/kustomizeconfig.yaml" nameReference: @@ -265,7 +267,8 @@ Now add under this directory the three resource manifests for Flagger: tester app (which generates synthetic traffic during the analysis phase), from that `HelmRepository` -
Expand to see the three Flagger resource manifests +
+Expand to see the three Flagger resource manifests ```yaml title="flagger/namespace.yaml" --- @@ -330,7 +333,8 @@ spec: Now add the following Kustomization file. It references all of the previous files that you've added: -
Expand to see the Flagger Kustomization manifest +
+Expand to see the Flagger Kustomization manifest ```yaml title="flagger/kustomization.yaml" --- @@ -394,7 +398,8 @@ The following table provides a list of all the custom resources that Flagger gen For example, the following manifest shows how `gitops-canaries-reader` has been extended to allow the user for viewing TrafficSplit resources when Linkerd is used: -
Expand to see example canary reader RBAC +
+Expand to see example canary reader RBAC ```yaml title="gitops-canaries-reader.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -438,7 +443,8 @@ In order to view canaries in a remote cluster from the management cluster, you n For example, applying the following manifest on remote clusters, ensures that the `wego-admin` user will be able to view canary information from within the Weave GitOps Enterprise UI on the management cluster: -
Expand to see example of remote cluster canary reader +
+Expand to see example of remote cluster canary reader ```yaml title="remote-cluster-service-user-rbac.yaml" apiVersion: rbac.authorization.k8s.io/v1 @@ -533,7 +539,8 @@ Create a new `test` directory and add these three canary resource manifests unde We don't need to define a service resource. This is specified within the canary definition and created by Flagger. -
Expand to see the three canary resource manifests +
+Expand to see the three canary resource manifests ```yaml title="test/namespace.yaml" --- @@ -717,7 +724,8 @@ spec: Add a Kustomization file to apply all resources to the `test` namespace: -
Expand to see the Canary Kustomization manifest +
+Expand to see the Canary Kustomization manifest ```yaml title="test/kustomization.yaml" --- diff --git a/website/versioned_docs/version-0.38.0/secrets/bootstrapping-secrets.mdx b/website/versioned_docs/version-0.38.0/secrets/bootstrapping-secrets.mdx index 99d8c59496..3445abd5d0 100644 --- a/website/versioned_docs/version-0.38.0/secrets/bootstrapping-secrets.mdx +++ b/website/versioned_docs/version-0.38.0/secrets/bootstrapping-secrets.mdx @@ -80,7 +80,8 @@ More info about the CRD spec [here](./spec/v1alpha1/secretSync.mdx) 1. You are using [Weave Gitops Enterprise version > v0.19.0](../enterprise/getting-started/releases-enterprise.mdx) 2. You have a set of GitopsClusters representing the clusters that you want to sync the secret to. They have a set of labels to allow matching. -
Expand to see example +
+Expand to see example ```yaml apiVersion: gitops.weave.works/v1alpha1 @@ -94,7 +95,8 @@ metadata: 3. You have created a secret that you want to sync from the management cluster. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.38.0/secrets/getting-started.mdx b/website/versioned_docs/version-0.38.0/secrets/getting-started.mdx index a21c3436b8..1d7b87f2ed 100644 --- a/website/versioned_docs/version-0.38.0/secrets/getting-started.mdx +++ b/website/versioned_docs/version-0.38.0/secrets/getting-started.mdx @@ -26,7 +26,8 @@ In order to be able to manage external secrets stores and secrets, add `external Include via `values.yaml` the configuration to deploy the [SecretStore](https://external-secrets.io/v0.8.1/api/secretstore/) connecting to AWS Secrets Manager. -
Expand to see an example +
+Expand to see an example ```yaml values: @@ -94,7 +95,8 @@ See it available in your cluster. At this stage you have everything you need for your application to [consume the secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). Add it to your application as usual. -
Expand to see example +
+Expand to see example ```yaml apiVersion: v1 diff --git a/website/versioned_docs/version-0.38.0/secrets/setup-eso.mdx b/website/versioned_docs/version-0.38.0/secrets/setup-eso.mdx index 98f0568934..953330f695 100644 --- a/website/versioned_docs/version-0.38.0/secrets/setup-eso.mdx +++ b/website/versioned_docs/version-0.38.0/secrets/setup-eso.mdx @@ -49,7 +49,8 @@ To bootstrap the ESO profile on a leaf cluster, select `external-secrets` from t You should then configure the `values.yaml` to install the `SecretStores` on the cluster from a `GitRepository`. This is done by configuring the `secretStores` section. -
Expand to see an example that creates a new git source from a specific tag +
+Expand to see an example that creates a new git source from a specific tag ```yaml secretStores: @@ -61,7 +62,8 @@ secretStores: ```
-
Expand to see an example that uses an existing git source +
+Expand to see an example that uses an existing git source ```yaml secretStores: diff --git a/website/versioned_docs/version-0.38.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.38.0/secrets/setup-sops.mdx index b8f89ed24a..5f2ee6e237 100644 --- a/website/versioned_docs/version-0.38.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.38.0/secrets/setup-sops.mdx @@ -30,7 +30,8 @@ Here are the steps to generate an OpenPGP key and configure your cluster to work 1- Generate a gpg key pairs -
Expand for instructions +
+Expand for instructions ```bash export KEY_NAME="gpg-key" @@ -107,7 +108,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -200,7 +202,8 @@ sops-public-key/namespace=flux-system \ -n flux-system ``` -
Expand to see the expected kustomization object +
+Expand to see the expected kustomization object ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1beta2 @@ -247,7 +250,8 @@ As well as an option to push the public key to the git repository via a PR (to b The following example is using GPG encryption to install SOPS and generate keys when bootstrapping leaf clusters. Create the following `ClusterBootstrapConfig` CR and push it to your fleet repo. -
Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view +
+Expand to view Expand to view the RoleBinding +
+Expand to view the RoleBinding ```yaml apiVersion: rbac.authorization.k8s.io/v1 diff --git a/website/versioned_docs/version-0.38.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.38.0/terraform/using-terraform-templates.mdx index 1637a79125..dee89f89e9 100644 --- a/website/versioned_docs/version-0.38.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.38.0/terraform/using-terraform-templates.mdx @@ -23,7 +23,8 @@ Add the following template to a path in your Git repository that is synced by Fl Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. -
Expand to see ./clusters/management/tf-template.yaml +
+Expand to see ./clusters/management/tf-template.yaml ```yaml title="./clusters/management/tf-template.yaml" --- @@ -176,7 +177,8 @@ Commit and push your changes. You can now store encrypted secrets to your Git re Add the following Terraform manifest to the root of your Git repository. -
Expand to see Terraform manifest +
+Expand to see Terraform manifest ```yaml title="./rds.tf" terraform { @@ -251,7 +253,8 @@ resource "aws_rds_cluster_instance" "cluster_instance" { Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. -
Expand to see Terraform manifest at +
+Expand to see Terraform manifest at ./clusters/management/rds-template.yaml ```yaml title="./clusters/management/rds-template.yaml" diff --git a/website/versioned_docs/version-0.38.0/workspaces/multi-tenancy.mdx b/website/versioned_docs/version-0.38.0/workspaces/multi-tenancy.mdx index 48f6043878..d0355bdfc2 100644 --- a/website/versioned_docs/version-0.38.0/workspaces/multi-tenancy.mdx +++ b/website/versioned_docs/version-0.38.0/workspaces/multi-tenancy.mdx @@ -33,7 +33,8 @@ To make use of the policy features, [policy agent](/policy/intro.mdx) needs to b Below is an example of a tenancy file: -
Expand to view +
+Expand to view ```yaml title="tenancy.yaml" --- @@ -115,7 +116,8 @@ For more control on a specific tenant a tenancy file should be used, the command gitops create tenants --name test-tenant --namespace test-ns1 --namespace test-ns2 ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -144,7 +146,8 @@ tenants: gitops create tenants --from-file tenants.yaml ``` -
Expand to view command output +
+Expand to view command output ```bash namespace/test-ns1 created @@ -164,7 +167,8 @@ To check the resources that would be deployed first use the `export` flag: gitops create tenants --from-file tenants.yaml --export ``` -
Expand to view command output +
+Expand to view command output ```bash apiVersion: v1 From 7c91fbe03e07c0f87f66d059c8ed2bc8d42a3061 Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 10:22:23 +0100 Subject: [PATCH 06/12] docs: fix lt and gt --- website/src/pages/security/index.md | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- website/versioned_docs/version-0.22.0/explorer/querying.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- website/versioned_docs/version-0.23.0/explorer/querying.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- website/versioned_docs/version-0.24.0/explorer/querying.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- website/versioned_docs/version-0.25.0/explorer/querying.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- .../using-terraform-cr/set-variables-for-trraform-resources.mdx | 2 +- 17 files changed, 17 insertions(+), 17 deletions(-) diff --git a/website/src/pages/security/index.md b/website/src/pages/security/index.md index 2b6a48ca71..5c98252a83 100644 --- a/website/src/pages/security/index.md +++ b/website/src/pages/security/index.md @@ -45,7 +45,7 @@ Here is an overview of all our published security advisories. Date | CVE | Security Advisory | Severity | Affected version(s) | ---- | -- |----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| ------------------- | -2022-06-23 | [CVE-2022-31098](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31098)| [Weave GitOps leaked cluster credentials into logs on connection errors](https://github.com/advisories/GHSA-xggc-qprg-x6mw) | Critical | <= 0.8.1-rc.5| +2022-06-23 | [CVE-2022-31098](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31098)| [Weave GitOps leaked cluster credentials into logs on connection errors](https://github.com/advisories/GHSA-xggc-qprg-x6mw) | Critical | \<= 0.8.1-rc.5| ### Weave Gitops Enterprise diff --git a/website/versioned_docs/version-0.16.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.16.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 5ccca48044..6e17e51ec3 100644 --- a/website/versioned_docs/version-0.16.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.16.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true **BREAKING CHANGE**: This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.17.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.17.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index 5ccca48044..6e17e51ec3 100644 --- a/website/versioned_docs/version-0.17.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.17.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true **BREAKING CHANGE**: This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.22.0/explorer/querying.mdx b/website/versioned_docs/version-0.22.0/explorer/querying.mdx index 7d141224ed..3c72167404 100644 --- a/website/versioned_docs/version-0.22.0/explorer/querying.mdx +++ b/website/versioned_docs/version-0.22.0/explorer/querying.mdx @@ -67,7 +67,7 @@ And represented in the UI like Based on the previous schema you have two main modes to discover or filter the data -1. Filter by key and value: when you know the pair that you want to filter from. +1. Filter by key and value: when you know the pair \ that you want to filter from. 2. Filter by value: when you want to filter across keys or does not know the key :::info Matching diff --git a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.23.0/explorer/querying.mdx b/website/versioned_docs/version-0.23.0/explorer/querying.mdx index 7d141224ed..3c72167404 100644 --- a/website/versioned_docs/version-0.23.0/explorer/querying.mdx +++ b/website/versioned_docs/version-0.23.0/explorer/querying.mdx @@ -67,7 +67,7 @@ And represented in the UI like Based on the previous schema you have two main modes to discover or filter the data -1. Filter by key and value: when you know the pair that you want to filter from. +1. Filter by key and value: when you know the pair \ that you want to filter from. 2. Filter by value: when you want to filter across keys or does not know the key :::info Matching diff --git a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.24.0/explorer/querying.mdx b/website/versioned_docs/version-0.24.0/explorer/querying.mdx index 7d141224ed..3c72167404 100644 --- a/website/versioned_docs/version-0.24.0/explorer/querying.mdx +++ b/website/versioned_docs/version-0.24.0/explorer/querying.mdx @@ -67,7 +67,7 @@ And represented in the UI like Based on the previous schema you have two main modes to discover or filter the data -1. Filter by key and value: when you know the pair that you want to filter from. +1. Filter by key and value: when you know the pair \ that you want to filter from. 2. Filter by value: when you want to filter across keys or does not know the key :::info Matching diff --git a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.25.0/explorer/querying.mdx b/website/versioned_docs/version-0.25.0/explorer/querying.mdx index 7d141224ed..3c72167404 100644 --- a/website/versioned_docs/version-0.25.0/explorer/querying.mdx +++ b/website/versioned_docs/version-0.25.0/explorer/querying.mdx @@ -67,7 +67,7 @@ And represented in the UI like Based on the previous schema you have two main modes to discover or filter the data -1. Filter by key and value: when you know the pair that you want to filter from. +1. Filter by key and value: when you know the pair \ that you want to filter from. 2. Filter by value: when you want to filter across keys or does not know the key :::info Matching diff --git a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} diff --git a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx index a27eb22e37..88bded2b03 100644 --- a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx +++ b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/set-variables-for-trraform-resources.mdx @@ -9,7 +9,7 @@ hide_title: true This is a breaking change of the `v1alpha1` API. ::: -Users who are upgrading from TF-controller <= 0.7.0 require updating `varsFrom`, +Users who are upgrading from TF-controller \<= 0.7.0 require updating `varsFrom`, from a single object: ```yaml {2} From a36b43ab1af16dd9668dbfd1a0f5d740663da57d Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 10:40:06 +0100 Subject: [PATCH 07/12] docs: fix h3 and td --- website/docs/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.20.0/gitopssets/_api.mdx | 54 ++++++++++------ .../version-0.21.1/gitopssets/_api.mdx | 54 ++++++++++------ .../version-0.21.2/gitopssets/_api.mdx | 54 ++++++++++------ .../version-0.22.0/gitopssets/_api.mdx | 54 ++++++++++------ .../version-0.23.0/gitopssets/_api.mdx | 54 ++++++++++------ .../version-0.24.0/gitopssets/_api.mdx | 57 +++++++++++------ .../version-0.25.0/gitopssets/_api.mdx | 57 +++++++++++------ .../version-0.26.0/gitopssets/_api.mdx | 57 +++++++++++------ .../version-0.27.0/gitopssets/_api.mdx | 57 +++++++++++------ .../version-0.28.0/gitopssets/_api.mdx | 60 ++++++++++++------ .../version-0.29.0/gitopssets/_api.mdx | 60 ++++++++++++------ .../version-0.30.0/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.31.2/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.32.0/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.33.0/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.34.0/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.35.0/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.36.0/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.37.0/gitopssets/_api.mdx | 63 ++++++++++++------- .../version-0.38.0/gitopssets/_api.mdx | 63 ++++++++++++------- 21 files changed, 832 insertions(+), 416 deletions(-) diff --git a/website/docs/gitopssets/_api.mdx b/website/docs/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/docs/gitopssets/_api.mdx +++ b/website/docs/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types: -

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.20.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.20.0/gitopssets/_api.mdx index 9c646b09b8..90c4989328 100644 --- a/website/versioned_docs/version-0.20.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.20.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -377,7 +382,8 @@ APIClientGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -455,7 +461,8 @@ APIClientGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -525,7 +532,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -599,7 +607,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -642,7 +651,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -698,7 +708,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -736,7 +747,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -764,7 +776,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -804,7 +817,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -834,7 +848,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -865,7 +880,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -972,7 +988,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1002,7 +1019,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.21.1/gitopssets/_api.mdx b/website/versioned_docs/version-0.21.1/gitopssets/_api.mdx index 9c646b09b8..90c4989328 100644 --- a/website/versioned_docs/version-0.21.1/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.21.1/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -377,7 +382,8 @@ APIClientGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -455,7 +461,8 @@ APIClientGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -525,7 +532,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -599,7 +607,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -642,7 +651,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -698,7 +708,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -736,7 +747,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -764,7 +776,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -804,7 +817,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -834,7 +848,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -865,7 +880,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -972,7 +988,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1002,7 +1019,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.21.2/gitopssets/_api.mdx b/website/versioned_docs/version-0.21.2/gitopssets/_api.mdx index 9c646b09b8..90c4989328 100644 --- a/website/versioned_docs/version-0.21.2/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.21.2/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -377,7 +382,8 @@ APIClientGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -455,7 +461,8 @@ APIClientGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -525,7 +532,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -599,7 +607,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -642,7 +651,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -698,7 +708,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -736,7 +747,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -764,7 +776,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -804,7 +817,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -834,7 +848,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -865,7 +880,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -972,7 +988,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1002,7 +1019,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.22.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.22.0/gitopssets/_api.mdx index 9c646b09b8..90c4989328 100644 --- a/website/versioned_docs/version-0.22.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.22.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -377,7 +382,8 @@ APIClientGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -455,7 +461,8 @@ APIClientGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -525,7 +532,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -599,7 +607,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -642,7 +651,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -698,7 +708,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -736,7 +747,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -764,7 +776,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -804,7 +817,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -834,7 +848,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -865,7 +880,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -972,7 +988,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1002,7 +1019,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.23.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.23.0/gitopssets/_api.mdx index 9c646b09b8..90c4989328 100644 --- a/website/versioned_docs/version-0.23.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.23.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -377,7 +382,8 @@ APIClientGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -455,7 +461,8 @@ APIClientGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -525,7 +532,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -599,7 +607,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -642,7 +651,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -698,7 +708,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -736,7 +747,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -764,7 +776,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -804,7 +817,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -834,7 +848,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -865,7 +880,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -972,7 +988,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1002,7 +1019,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.24.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.24.0/gitopssets/_api.mdx index 3b684ec41b..5f9e84cb43 100644 --- a/website/versioned_docs/version-0.24.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.24.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -389,7 +394,8 @@ ImagePolicyGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -493,7 +499,8 @@ ImagePolicyGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -563,7 +570,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -637,7 +645,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -680,7 +689,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -736,7 +746,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -774,7 +785,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -802,7 +814,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -842,7 +855,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -871,7 +885,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -901,7 +916,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -932,7 +948,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1039,7 +1056,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1069,7 +1087,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.25.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.25.0/gitopssets/_api.mdx index 3b684ec41b..5f9e84cb43 100644 --- a/website/versioned_docs/version-0.25.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.25.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -389,7 +394,8 @@ ImagePolicyGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -493,7 +499,8 @@ ImagePolicyGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -563,7 +570,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -637,7 +645,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -680,7 +689,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -736,7 +746,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -774,7 +785,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -802,7 +814,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -842,7 +855,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -871,7 +885,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -901,7 +916,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -932,7 +948,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1039,7 +1056,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1069,7 +1087,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.26.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.26.0/gitopssets/_api.mdx index 3b684ec41b..5f9e84cb43 100644 --- a/website/versioned_docs/version-0.26.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.26.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -389,7 +394,8 @@ ImagePolicyGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -493,7 +499,8 @@ ImagePolicyGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -563,7 +570,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -637,7 +645,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -680,7 +689,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -736,7 +746,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -774,7 +785,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -802,7 +814,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -842,7 +855,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -871,7 +885,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -901,7 +916,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -932,7 +948,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1039,7 +1056,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1069,7 +1087,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.27.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.27.0/gitopssets/_api.mdx index 3b684ec41b..5f9e84cb43 100644 --- a/website/versioned_docs/version-0.27.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.27.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -389,7 +394,8 @@ ImagePolicyGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -493,7 +499,8 @@ ImagePolicyGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -563,7 +570,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -637,7 +645,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -680,7 +689,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -736,7 +746,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -774,7 +785,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -802,7 +814,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -842,7 +855,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -871,7 +885,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -901,7 +916,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -932,7 +948,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1039,7 +1056,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1069,7 +1087,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.28.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.28.0/gitopssets/_api.mdx index d288ebe879..5a70447718 100644 --- a/website/versioned_docs/version-0.28.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.28.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -329,7 +334,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -442,7 +448,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -558,7 +565,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -628,7 +636,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -702,7 +711,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -745,7 +755,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -801,7 +812,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -839,7 +851,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -867,7 +880,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -907,7 +921,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -936,7 +951,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -966,7 +982,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -997,7 +1014,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1104,7 +1122,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1134,7 +1153,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.29.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.29.0/gitopssets/_api.mdx index d288ebe879..5a70447718 100644 --- a/website/versioned_docs/version-0.29.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.29.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -254,7 +257,8 @@ entire object.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -288,7 +292,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -329,7 +334,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -442,7 +448,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -558,7 +565,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -628,7 +636,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -702,7 +711,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -745,7 +755,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -801,7 +812,8 @@ generated.

-

GitRepositoryGeneratorDirectoryItem +

+GitRepositoryGeneratorDirectoryItem

(Appears on: @@ -839,7 +851,8 @@ bool -

GitRepositoryGeneratorFileItem +

+GitRepositoryGeneratorFileItem

(Appears on: @@ -867,7 +880,8 @@ string -

HeadersReference +

+HeadersReference

(Appears on: @@ -907,7 +921,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -936,7 +951,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -966,7 +982,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -997,7 +1014,8 @@ The matrix is a cartesian product of the generators.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1104,7 +1122,8 @@ or to include forks if true

-

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1134,7 +1153,8 @@ or to include forks if true

-

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.30.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.30.0/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.30.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.30.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.31.2/gitopssets/_api.mdx b/website/versioned_docs/version-0.31.2/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.31.2/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.31.2/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.32.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.32.0/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.32.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.32.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.33.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.33.0/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.33.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.33.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.34.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.34.0/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.34.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.34.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.35.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.35.0/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.35.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.35.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.36.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.36.0/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.36.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.36.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.37.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.37.0/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.37.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.37.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: diff --git a/website/versioned_docs/version-0.38.0/gitopssets/_api.mdx b/website/versioned_docs/version-0.38.0/gitopssets/_api.mdx index 2825df7958..32b9be1931 100644 --- a/website/versioned_docs/version-0.38.0/gitopssets/_api.mdx +++ b/website/versioned_docs/version-0.38.0/gitopssets/_api.mdx @@ -10,7 +10,8 @@ Resource Types:

-

GitOpsSet +

+GitOpsSet

GitOpsSet is the Schema for the gitopssets API

@@ -24,7 +25,8 @@ Resource Types: +string + @@ -137,7 +139,8 @@ GitOpsSetStatus
apiVersion
-string		 templates.weave.works/v1alpha1
-

APIClientGenerator +

+APIClientGenerator

(Appears on: @@ -268,7 +271,8 @@ provides the Certificate Authority to trust when making API calls.

-

ClusterGenerator +

+ClusterGenerator

(Appears on: @@ -302,7 +306,8 @@ Kubernetes meta/v1.LabelSelector -

ConfigGenerator +

+ConfigGenerator

(Appears on: @@ -343,7 +348,8 @@ string -

GitOpsSetGenerator +

+GitOpsSetGenerator

(Appears on: @@ -468,7 +474,8 @@ ConfigGenerator -

GitOpsSetNestedGenerator +

+GitOpsSetNestedGenerator

(Appears on: @@ -596,7 +603,8 @@ ConfigGenerator -

GitOpsSetSpec +

+GitOpsSetSpec

(Appears on: @@ -666,7 +674,8 @@ when reconciling this Kustomization.

-

GitOpsSetStatus +

+GitOpsSetStatus

(Appears on: @@ -740,7 +749,8 @@ have been successfully applied

-

GitOpsSetTemplate +

+GitOpsSetTemplate

(Appears on: @@ -783,7 +793,8 @@ k8s.io/apimachinery/pkg/runtime.RawExtension -

GitRepositoryGenerator +

+GitRepositoryGenerator

(Appears on: @@ -839,7 +850,8 @@ generated.

-

HeadersReference +

+HeadersReference

(Appears on: @@ -879,7 +891,8 @@ string -

ImagePolicyGenerator +

+ImagePolicyGenerator

(Appears on: @@ -908,7 +921,8 @@ string -

ListGenerator +

+ListGenerator

(Appears on: @@ -938,7 +952,8 @@ string -

MatrixGenerator +

+MatrixGenerator

(Appears on: @@ -985,7 +1000,8 @@ It’s recommended that you use the Name field to separate out elements.

-

OCIRepositoryGenerator +

+OCIRepositoryGenerator

(Appears on: @@ -1041,7 +1057,8 @@ generated.

-

PullRequestGenerator +

+PullRequestGenerator

(Appears on: @@ -1148,7 +1165,8 @@ or to include forks if true

-

RepositoryGeneratorDirectoryItem +

+RepositoryGeneratorDirectoryItem

(Appears on: @@ -1187,7 +1205,8 @@ bool -

RepositoryGeneratorFileItem +

+RepositoryGeneratorFileItem

(Appears on: @@ -1216,7 +1235,8 @@ string -

ResourceInventory +

+ResourceInventory

(Appears on: @@ -1246,7 +1266,8 @@ string -

ResourceRef +

+ResourceRef

(Appears on: From 78cb9356bd1057c3b9f284c1a5015495e165ac4a Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 15:14:05 +0100 Subject: [PATCH 08/12] docs: fix missing imports --- .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ .../version-0.16.0/configuration/user-permissions.mdx | 2 ++ .../version-0.16.0/pipelines/spec/v1alpha1/pipeline.mdx | 2 ++ .../version-0.17.0/configuration/user-permissions.mdx | 2 ++ website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx | 1 + website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx | 1 + .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ .../enterprise/getting-started/install-enterprise-azure.mdx | 2 ++ 14 files changed, 26 insertions(+) diff --git a/website/docs/enterprise/getting-started/install-enterprise-azure.mdx b/website/docs/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/docs/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/docs/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; diff --git a/website/versioned_docs/version-0.16.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.16.0/configuration/user-permissions.mdx index 5089a0ee4c..80645a28b6 100644 --- a/website/versioned_docs/version-0.16.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.16.0/configuration/user-permissions.mdx @@ -2,6 +2,8 @@ title: User permissions --- +import TierLabel from "../_components/TierLabel"; + This is an explanation of the [kubernetes permissions](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) needed by users of the Weave GitOps application. As covered in [service account permissions](service-account-permissions.mdx) diff --git a/website/versioned_docs/version-0.16.0/pipelines/spec/v1alpha1/pipeline.mdx b/website/versioned_docs/version-0.16.0/pipelines/spec/v1alpha1/pipeline.mdx index 9efc20e116..48c3b2cf14 100644 --- a/website/versioned_docs/version-0.16.0/pipelines/spec/v1alpha1/pipeline.mdx +++ b/website/versioned_docs/version-0.16.0/pipelines/spec/v1alpha1/pipeline.mdx @@ -2,6 +2,8 @@ title: Pipeline hide_title: true --- +import TierLabel from "../../../_components/TierLabel"; + # Pipeline The Pipeline API defines a resource for continuous delivery pipelines. diff --git a/website/versioned_docs/version-0.17.0/configuration/user-permissions.mdx b/website/versioned_docs/version-0.17.0/configuration/user-permissions.mdx index d43dc7c089..a4f33d4099 100644 --- a/website/versioned_docs/version-0.17.0/configuration/user-permissions.mdx +++ b/website/versioned_docs/version-0.17.0/configuration/user-permissions.mdx @@ -2,6 +2,8 @@ title: User permissions --- +import TierLabel from "../_components/TierLabel"; + This is an explanation of the [kubernetes permissions](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) needed by users of the Weave GitOps application. As covered in [service account permissions](service-account-permissions.mdx) diff --git a/website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx b/website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx index f648418732..70e956aab5 100644 --- a/website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.20.0/secrets/setup-sops.mdx @@ -3,6 +3,7 @@ title: Setup SOPS hide_title: true --- +import CodeBlock from "@theme/CodeBlock"; import SopsBootstrapJob from "!!raw-loader!./assets/sops-bootstrap-job.yaml"; import TemplateParams from "!!raw-loader!./assets/template-params.yaml"; import TemplateAnnotations from "!!raw-loader!./assets/template-annotations.yaml"; diff --git a/website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx b/website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx index f648418732..70e956aab5 100644 --- a/website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx +++ b/website/versioned_docs/version-0.21.1/secrets/setup-sops.mdx @@ -3,6 +3,7 @@ title: Setup SOPS hide_title: true --- +import CodeBlock from "@theme/CodeBlock"; import SopsBootstrapJob from "!!raw-loader!./assets/sops-bootstrap-job.yaml"; import TemplateParams from "!!raw-loader!./assets/template-params.yaml"; import TemplateAnnotations from "!!raw-loader!./assets/template-annotations.yaml"; diff --git a/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise-azure.mdx b/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/versioned_docs/version-0.31.2/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; diff --git a/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise-azure.mdx b/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/versioned_docs/version-0.32.0/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; diff --git a/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise-azure.mdx b/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/versioned_docs/version-0.33.0/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; diff --git a/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise-azure.mdx b/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/versioned_docs/version-0.34.0/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; diff --git a/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise-azure.mdx b/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/versioned_docs/version-0.35.0/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; diff --git a/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-azure.mdx b/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; diff --git a/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-azure.mdx b/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; diff --git a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-azure.mdx b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-azure.mdx index 8c017e026e..26618027dc 100644 --- a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-azure.mdx +++ b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-azure.mdx @@ -3,6 +3,8 @@ title: Azure and Weave GitOps Enterprise Installation hide_title: true --- +import Tabs from "@theme/Tabs"; +import TabItem from "@theme/TabItem"; import TierLabel from "@site/docs/_components/TierLabel"; import oauthBitbucket from '/img/oauth-bitbucket.png'; import oauthAzureDevOps from '/img/oauth-azure-devops.png'; From c4b76c06c050cecb84fb68215886ae54f953e6c8 Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 16:54:00 +0100 Subject: [PATCH 09/12] docs: escape { } --- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- .../terraform/using-terraform-cr/custom-backend.mdx | 2 +- 12 files changed, 12 insertions(+), 12 deletions(-) diff --git a/website/versioned_docs/version-0.16.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.16.0/terraform/using-terraform-cr/custom-backend.mdx index 64cf412987..43ee47974f 100644 --- a/website/versioned_docs/version-0.16.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.16.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.17.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.17.0/terraform/using-terraform-cr/custom-backend.mdx index 64cf412987..43ee47974f 100644 --- a/website/versioned_docs/version-0.17.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.17.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.18.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.19.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.20.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.21.1/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.21.2/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.22.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.23.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.24.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.25.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` diff --git a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/custom-backend.mdx b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/custom-backend.mdx index 4cd4641d48..515fcc9a7f 100644 --- a/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/custom-backend.mdx +++ b/website/versioned_docs/version-0.26.0/terraform/using-terraform-cr/custom-backend.mdx @@ -7,7 +7,7 @@ hide_title: true By default, TF-controller will use the [Kubernetes backend](https://www.terraform.io/language/settings/backends/kubernetes) to store the Terraform state file (tfstate) in the cluster. -The tfstate is stored in a `Secret` named "tfstate-${workspace}-${secretSuffix}", +The tfstate is stored in a `Secret` named "tfstate-$\{workspace\}-$\{secretSuffix\}", where the default suffix is the name of the `Terraform` resource. You can override this default suffix by setting `.spec.backendConfig.secretSuffix` From 299eeaa88f05bfd69077de95083dce292dcae97e Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 17:12:13 +0100 Subject: [PATCH 10/12] docs: fix toc --- .../docs/cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-existing-clusters.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- .../cluster-management/managing-clusters-without-capi.mdx | 2 +- 25 files changed, 25 insertions(+), 25 deletions(-) diff --git a/website/docs/cluster-management/managing-clusters-without-capi.mdx b/website/docs/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/docs/cluster-management/managing-clusters-without-capi.mdx +++ b/website/docs/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + diff --git a/website/versioned_docs/version-0.16.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.16.0/cluster-management/managing-existing-clusters.mdx index 79790c77e9..54feaaa1c9 100644 --- a/website/versioned_docs/version-0.16.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.16.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.17.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.17.0/cluster-management/managing-existing-clusters.mdx index fe3a60b9fa..04802e8254 100644 --- a/website/versioned_docs/version-0.17.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.17.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.18.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.19.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.19.0/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.19.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.19.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.20.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.20.0/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.20.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.20.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.21.1/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.21.1/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.21.1/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.21.1/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.21.2/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.21.2/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.21.2/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.21.2/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.22.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.22.0/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.22.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.22.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.23.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.23.0/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.23.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.23.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.24.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.24.0/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.24.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.24.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.25.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.25.0/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.25.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.25.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.26.0/cluster-management/managing-existing-clusters.mdx b/website/versioned_docs/version-0.26.0/cluster-management/managing-existing-clusters.mdx index d284ddd8ed..5e62b24460 100644 --- a/website/versioned_docs/version-0.26.0/cluster-management/managing-existing-clusters.mdx +++ b/website/versioned_docs/version-0.26.0/cluster-management/managing-existing-clusters.mdx @@ -16,7 +16,7 @@ Any kubernetes cluster whether capi or not can be added to Weave Gitops Enterpri import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.27.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.27.0/cluster-management/managing-clusters-without-capi.mdx index 16233d41be..d50d4643d2 100644 --- a/website/versioned_docs/version-0.27.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.27.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave Gitops E import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.28.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.28.0/cluster-management/managing-clusters-without-capi.mdx index 16233d41be..d50d4643d2 100644 --- a/website/versioned_docs/version-0.28.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.28.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave Gitops E import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.29.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.29.0/cluster-management/managing-clusters-without-capi.mdx index 16233d41be..d50d4643d2 100644 --- a/website/versioned_docs/version-0.29.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.29.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave Gitops E import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.30.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.30.0/cluster-management/managing-clusters-without-capi.mdx index ac3f39304f..f492b35b61 100644 --- a/website/versioned_docs/version-0.30.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.30.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; -; + diff --git a/website/versioned_docs/version-0.31.2/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.31.2/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/versioned_docs/version-0.31.2/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.31.2/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + diff --git a/website/versioned_docs/version-0.32.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.32.0/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/versioned_docs/version-0.32.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.32.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + diff --git a/website/versioned_docs/version-0.33.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.33.0/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/versioned_docs/version-0.33.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.33.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + diff --git a/website/versioned_docs/version-0.34.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.34.0/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/versioned_docs/version-0.34.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.34.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + diff --git a/website/versioned_docs/version-0.35.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.35.0/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/versioned_docs/version-0.35.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.35.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + diff --git a/website/versioned_docs/version-0.36.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.36.0/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/versioned_docs/version-0.36.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.36.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + diff --git a/website/versioned_docs/version-0.37.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.37.0/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/versioned_docs/version-0.37.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.37.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + diff --git a/website/versioned_docs/version-0.38.0/cluster-management/managing-clusters-without-capi.mdx b/website/versioned_docs/version-0.38.0/cluster-management/managing-clusters-without-capi.mdx index 9e7c343aaa..081524bf8b 100644 --- a/website/versioned_docs/version-0.38.0/cluster-management/managing-clusters-without-capi.mdx +++ b/website/versioned_docs/version-0.38.0/cluster-management/managing-clusters-without-capi.mdx @@ -16,7 +16,7 @@ You do **not** need Cluster API to add your Kubernetes cluster to Weave GitOps E import TOCInline from "@theme/TOCInline"; - + From 7661a092d786e285f344f84b508c604c3bb21f9a Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Wed, 25 Dec 2024 21:59:17 +0100 Subject: [PATCH 11/12] docs: fix broken links --- .../docs/enterprise/getting-started/releases-enterprise.mdx | 2 +- website/docs/explorer/configuration.mdx | 4 ++-- website/src/pages/security/index.md | 2 +- .../version-0.22.0/cluster-management/getting-started.mdx | 2 +- .../version-0.23.0/cluster-management/getting-started.mdx | 2 +- .../version-0.24.0/cluster-management/getting-started.mdx | 2 +- .../enterprise/getting-started/releases-enterprise.mdx | 4 ++-- .../versioned_docs/version-0.24.0/gitops-templates/cli.mdx | 2 +- .../version-0.25.0/cluster-management/getting-started.mdx | 2 +- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../version-0.26.0/cluster-management/getting-started.mdx | 2 +- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.27.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.28.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.29.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.30.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.31.2/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.32.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.33.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.34.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.35.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.36.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.37.0/explorer/configuration.mdx | 4 ++-- .../enterprise/getting-started/releases-enterprise.mdx | 2 +- .../versioned_docs/version-0.38.0/explorer/configuration.mdx | 4 ++-- 36 files changed, 50 insertions(+), 50 deletions(-) diff --git a/website/docs/enterprise/getting-started/releases-enterprise.mdx b/website/docs/enterprise/getting-started/releases-enterprise.mdx index 9ca6725157..1ed149a413 100644 --- a/website/docs/enterprise/getting-started/releases-enterprise.mdx +++ b/website/docs/enterprise/getting-started/releases-enterprise.mdx @@ -596,7 +596,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/docs/explorer/configuration.mdx b/website/docs/explorer/configuration.mdx index 8cf7706c3e..6980c1f858 100644 --- a/website/docs/explorer/configuration.mdx +++ b/website/docs/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -98,7 +98,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/src/pages/security/index.md b/website/src/pages/security/index.md index 5c98252a83..e815ab72a5 100644 --- a/website/src/pages/security/index.md +++ b/website/src/pages/security/index.md @@ -13,7 +13,7 @@ This document defines security reporting, handling, disclosure, and audit inform ### Report a Vulnerability -- To make a report please email the private security list at [security@weaveworks.org](security@weaveworks.org) with the details. +- To make a report please email the private security list at [security@weaveworks.org](mailto:security@weaveworks.org) with the details. We ask that reporters act in good faith by not disclosing the issue to others. - Reported vulnerabilities are triaged by Weaveworks Security team. - Weaveworks Security team would acknowledge to the reporter for any valid request. diff --git a/website/versioned_docs/version-0.22.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.22.0/cluster-management/getting-started.mdx index f8eba21cd6..05375e3355 100644 --- a/website/versioned_docs/version-0.22.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.22.0/cluster-management/getting-started.mdx @@ -177,7 +177,7 @@ Download the profile repository below to your config repository path then commit {ProfileRepo} -For more information about profiles, see [profiles from private helm repositories](./profiles.mdx/#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). +For more information about profiles, see [profiles from private helm repositories](../profiles#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). #### Add a cluster bootstrap config diff --git a/website/versioned_docs/version-0.23.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.23.0/cluster-management/getting-started.mdx index f8eba21cd6..05375e3355 100644 --- a/website/versioned_docs/version-0.23.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.23.0/cluster-management/getting-started.mdx @@ -177,7 +177,7 @@ Download the profile repository below to your config repository path then commit {ProfileRepo} -For more information about profiles, see [profiles from private helm repositories](./profiles.mdx/#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). +For more information about profiles, see [profiles from private helm repositories](../profiles#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). #### Add a cluster bootstrap config diff --git a/website/versioned_docs/version-0.24.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.24.0/cluster-management/getting-started.mdx index 733ea1dc15..f435904b23 100644 --- a/website/versioned_docs/version-0.24.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.24.0/cluster-management/getting-started.mdx @@ -177,7 +177,7 @@ Download the profile repository below to your config repository path then commit {ProfileRepo} -For more information about profiles, see [profiles from private helm repositories](./profiles.mdx/#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). +For more information about profiles, see [profiles from private helm repositories](../profiles#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). #### Add a cluster bootstrap config diff --git a/website/versioned_docs/version-0.24.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.24.0/enterprise/getting-started/releases-enterprise.mdx index 98cf4416f5..5f38dce668 100644 --- a/website/versioned_docs/version-0.24.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.24.0/enterprise/getting-started/releases-enterprise.mdx @@ -101,7 +101,7 @@ This page details the changes for Weave GitOps Enterprise and its associated com - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets @@ -113,7 +113,7 @@ This page details the changes for Weave GitOps Enterprise and its associated com ### Upgrade Notes (from the previous release) -- Explorer: you should configure [collector service account](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) in your leaf clusters. +- Explorer: you should configure [collector service account](../../../explorer/configuration#authentication-and-authorization-for-collecting) in your leaf clusters. ### Known issues diff --git a/website/versioned_docs/version-0.24.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.24.0/gitops-templates/cli.mdx index 99a97ce496..79cfbe24c7 100644 --- a/website/versioned_docs/version-0.24.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.24.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx/#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.25.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.25.0/cluster-management/getting-started.mdx index 733ea1dc15..f435904b23 100644 --- a/website/versioned_docs/version-0.25.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.25.0/cluster-management/getting-started.mdx @@ -177,7 +177,7 @@ Download the profile repository below to your config repository path then commit {ProfileRepo} -For more information about profiles, see [profiles from private helm repositories](./profiles.mdx/#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). +For more information about profiles, see [profiles from private helm repositories](../profiles#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). #### Add a cluster bootstrap config diff --git a/website/versioned_docs/version-0.25.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.25.0/enterprise/getting-started/releases-enterprise.mdx index 29e465a2c3..55d3d769d1 100644 --- a/website/versioned_docs/version-0.25.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.25.0/enterprise/getting-started/releases-enterprise.mdx @@ -101,7 +101,7 @@ This page details the changes for Weave GitOps Enterprise and its associated com - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.26.0/cluster-management/getting-started.mdx b/website/versioned_docs/version-0.26.0/cluster-management/getting-started.mdx index 733ea1dc15..f435904b23 100644 --- a/website/versioned_docs/version-0.26.0/cluster-management/getting-started.mdx +++ b/website/versioned_docs/version-0.26.0/cluster-management/getting-started.mdx @@ -177,7 +177,7 @@ Download the profile repository below to your config repository path then commit {ProfileRepo} -For more information about profiles, see [profiles from private helm repositories](./profiles.mdx/#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). +For more information about profiles, see [profiles from private helm repositories](../profiles#optional-using-a-helm-chart-from-a-remote-publicprivate-repository), [policy profiles](../policy/weave-policy-profile.mdx), and [eso secrets profiles](../secrets/setup-eso.mdx). #### Add a cluster bootstrap config diff --git a/website/versioned_docs/version-0.26.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.26.0/enterprise/getting-started/releases-enterprise.mdx index 29e465a2c3..55d3d769d1 100644 --- a/website/versioned_docs/version-0.26.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.26.0/enterprise/getting-started/releases-enterprise.mdx @@ -101,7 +101,7 @@ This page details the changes for Weave GitOps Enterprise and its associated com - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.27.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.27.0/enterprise/getting-started/releases-enterprise.mdx index 29e465a2c3..55d3d769d1 100644 --- a/website/versioned_docs/version-0.27.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.27.0/enterprise/getting-started/releases-enterprise.mdx @@ -101,7 +101,7 @@ This page details the changes for Weave GitOps Enterprise and its associated com - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.27.0/explorer/configuration.mdx b/website/versioned_docs/version-0.27.0/explorer/configuration.mdx index 09685ffc23..8cb989e4af 100644 --- a/website/versioned_docs/version-0.27.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.27.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -93,7 +93,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../configuration/service-account-permissions.mdx), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.28.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.28.0/enterprise/getting-started/releases-enterprise.mdx index ae08ad5363..623242d798 100644 --- a/website/versioned_docs/version-0.28.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.28.0/enterprise/getting-started/releases-enterprise.mdx @@ -191,7 +191,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.28.0/explorer/configuration.mdx b/website/versioned_docs/version-0.28.0/explorer/configuration.mdx index 09685ffc23..8cb989e4af 100644 --- a/website/versioned_docs/version-0.28.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.28.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -93,7 +93,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../configuration/service-account-permissions.mdx), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.29.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.29.0/enterprise/getting-started/releases-enterprise.mdx index 40e69f863a..ee82310019 100644 --- a/website/versioned_docs/version-0.29.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.29.0/enterprise/getting-started/releases-enterprise.mdx @@ -267,7 +267,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.29.0/explorer/configuration.mdx b/website/versioned_docs/version-0.29.0/explorer/configuration.mdx index 09685ffc23..8cb989e4af 100644 --- a/website/versioned_docs/version-0.29.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.29.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -93,7 +93,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../configuration/service-account-permissions.mdx), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.30.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.30.0/enterprise/getting-started/releases-enterprise.mdx index a627d101b0..9751146f92 100644 --- a/website/versioned_docs/version-0.30.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.30.0/enterprise/getting-started/releases-enterprise.mdx @@ -301,7 +301,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.30.0/explorer/configuration.mdx b/website/versioned_docs/version-0.30.0/explorer/configuration.mdx index 0e216bda23..72d6fd64c8 100644 --- a/website/versioned_docs/version-0.30.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.30.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -93,7 +93,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for Collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setting up RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.31.2/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.31.2/enterprise/getting-started/releases-enterprise.mdx index e4f767b6b2..1cfc53e7d5 100644 --- a/website/versioned_docs/version-0.31.2/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.31.2/enterprise/getting-started/releases-enterprise.mdx @@ -319,7 +319,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.31.2/explorer/configuration.mdx b/website/versioned_docs/version-0.31.2/explorer/configuration.mdx index 4aa53ed750..2a71b6d457 100644 --- a/website/versioned_docs/version-0.31.2/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.31.2/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -93,7 +93,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.32.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.32.0/enterprise/getting-started/releases-enterprise.mdx index e4f767b6b2..1cfc53e7d5 100644 --- a/website/versioned_docs/version-0.32.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.32.0/enterprise/getting-started/releases-enterprise.mdx @@ -319,7 +319,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.32.0/explorer/configuration.mdx b/website/versioned_docs/version-0.32.0/explorer/configuration.mdx index 4aa53ed750..2a71b6d457 100644 --- a/website/versioned_docs/version-0.32.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.32.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -93,7 +93,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.33.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.33.0/enterprise/getting-started/releases-enterprise.mdx index e4f767b6b2..1cfc53e7d5 100644 --- a/website/versioned_docs/version-0.33.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.33.0/enterprise/getting-started/releases-enterprise.mdx @@ -319,7 +319,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.33.0/explorer/configuration.mdx b/website/versioned_docs/version-0.33.0/explorer/configuration.mdx index 58801fb387..10926ab64e 100644 --- a/website/versioned_docs/version-0.33.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.33.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -98,7 +98,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.34.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.34.0/enterprise/getting-started/releases-enterprise.mdx index e4f767b6b2..1cfc53e7d5 100644 --- a/website/versioned_docs/version-0.34.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.34.0/enterprise/getting-started/releases-enterprise.mdx @@ -319,7 +319,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.34.0/explorer/configuration.mdx b/website/versioned_docs/version-0.34.0/explorer/configuration.mdx index 58801fb387..10926ab64e 100644 --- a/website/versioned_docs/version-0.34.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.34.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -98,7 +98,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.35.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.35.0/enterprise/getting-started/releases-enterprise.mdx index e4f767b6b2..1cfc53e7d5 100644 --- a/website/versioned_docs/version-0.35.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.35.0/enterprise/getting-started/releases-enterprise.mdx @@ -319,7 +319,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.35.0/explorer/configuration.mdx b/website/versioned_docs/version-0.35.0/explorer/configuration.mdx index 58801fb387..10926ab64e 100644 --- a/website/versioned_docs/version-0.35.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.35.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -98,7 +98,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.36.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.36.0/enterprise/getting-started/releases-enterprise.mdx index 2e32d2ad84..8ebbd2d635 100644 --- a/website/versioned_docs/version-0.36.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.36.0/enterprise/getting-started/releases-enterprise.mdx @@ -502,7 +502,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.36.0/explorer/configuration.mdx b/website/versioned_docs/version-0.36.0/explorer/configuration.mdx index 58801fb387..10926ab64e 100644 --- a/website/versioned_docs/version-0.36.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.36.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -98,7 +98,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.37.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.37.0/enterprise/getting-started/releases-enterprise.mdx index 8bd8529390..e1ce643b13 100644 --- a/website/versioned_docs/version-0.37.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.37.0/enterprise/getting-started/releases-enterprise.mdx @@ -539,7 +539,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.37.0/explorer/configuration.mdx b/website/versioned_docs/version-0.37.0/explorer/configuration.mdx index 58801fb387..10926ab64e 100644 --- a/website/versioned_docs/version-0.37.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.37.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -98,7 +98,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. diff --git a/website/versioned_docs/version-0.38.0/enterprise/getting-started/releases-enterprise.mdx b/website/versioned_docs/version-0.38.0/enterprise/getting-started/releases-enterprise.mdx index 9ca6725157..1ed149a413 100644 --- a/website/versioned_docs/version-0.38.0/enterprise/getting-started/releases-enterprise.mdx +++ b/website/versioned_docs/version-0.38.0/enterprise/getting-started/releases-enterprise.mdx @@ -596,7 +596,7 @@ _Bug fixes_ - Explorer supports now Flux sources. - Applications UI and Sources UI could be configured to use Explorer backend to improve UI experience. -- Explorer collector uses impersonation. Ensure you [configure collector](../../explorer/configuration.mdx/#authentication-and-authorization-for-collecting) for your leaf clusters. +- Explorer collector uses impersonation. Ensure you [configure collector](../../../explorer/configuration#authentication-and-authorization-for-collecting) for your leaf clusters. #### GitopsSets diff --git a/website/versioned_docs/version-0.38.0/explorer/configuration.mdx b/website/versioned_docs/version-0.38.0/explorer/configuration.mdx index 58801fb387..10926ab64e 100644 --- a/website/versioned_docs/version-0.38.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.38.0/explorer/configuration.mdx @@ -52,7 +52,7 @@ spec: ### Clusters -Explorer watches the [GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +Explorer watches the [GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) that you have connected to Weave Gitops Enterprise, as well as your Management cluster. ### Kinds @@ -98,7 +98,7 @@ Query results are filtered honouring the access determined via RBAC. ## Authentication and Authorization for collecting -[GitopsClusters](../cluster-management/managing-clusters-without-capi.mdx/#connect-a-cluster) +[GitopsClusters](../../cluster-management/managing-clusters-without-capi#connect-a-cluster) define the connection and security context that Explorer leverages to collect data from leaf clusters. Given that you have followed the indications in [setup RBAC](../enterprise/getting-started/install-enterprise.mdx#gitops-dashboard-service-account-permissions), the GitopsCluster service account is able to impersonate any user or group. From d77670cba8c1a62700984ba0b6e9eaee42285abe Mon Sep 17 00:00:00 2001 From: Amund Tenstad Date: Thu, 26 Dec 2024 10:00:34 +0100 Subject: [PATCH 12/12] docs: fix broken anchors --- .../getting-started/install-enterprise-cli.mdx | 10 +++++----- website/docs/explorer/configuration.mdx | 2 +- website/docs/gitops-templates/cli.mdx | 2 +- website/docs/operations/monitoring.mdx | 2 +- website/docs/pipelines/pipelines-templates.mdx | 2 +- website/docs/policy/commit-time-checks.mdx | 12 ++++++------ website/docs/policy/policy-set.mdx | 2 +- website/docs/workspaces/view-workspaces.mdx | 2 +- .../version-0.16.0/gitops-templates/cli.mdx | 2 +- .../version-0.16.0/gitopssets/features.mdx | 4 ++-- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.16.0/pipelines/intro.mdx | 2 +- .../version-0.16.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.17.0/gitops-run/get-started.mdx | 2 +- .../version-0.17.0/gitopssets/features.mdx | 4 ++-- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.17.0/pipelines/intro.mdx | 2 +- .../version-0.17.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.18.0/gitops-run/get-started.mdx | 2 +- .../version-0.18.0/gitopssets/features.mdx | 4 ++-- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.18.0/pipelines/intro.mdx | 2 +- .../version-0.18.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.18.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.19.0/gitops-run/get-started.mdx | 2 +- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.19.0/pipelines/intro.mdx | 2 +- .../version-0.19.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.19.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.19.0/policy/policy-set.mdx | 2 +- .../version-0.19.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.20.0/gitops-run/get-started.mdx | 2 +- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.20.0/pipelines/intro.mdx | 2 +- .../version-0.20.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.20.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.20.0/policy/policy-set.mdx | 2 +- .../version-0.20.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.21.1/gitops-run/get-started.mdx | 2 +- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.21.1/pipelines/intro.mdx | 2 +- .../version-0.21.1/pipelines/pipeline-templates.mdx | 2 +- .../version-0.21.1/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.21.1/policy/policy-set.mdx | 2 +- .../version-0.21.1/workspaces/view-workspaces.mdx | 2 +- .../version-0.21.2/gitops-run/get-started.mdx | 2 +- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.21.2/pipelines/intro.mdx | 2 +- .../version-0.21.2/pipelines/pipeline-templates.mdx | 2 +- .../version-0.21.2/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.21.2/policy/policy-set.mdx | 2 +- .../version-0.21.2/workspaces/view-workspaces.mdx | 2 +- .../version-0.22.0/gitops-run/get-started.mdx | 2 +- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.22.0/pipelines/intro.mdx | 2 +- .../version-0.22.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.22.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.22.0/policy/policy-set.mdx | 2 +- .../version-0.22.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.23.0/explorer/configuration.mdx | 2 +- .../version-0.23.0/gitops-run/get-started.mdx | 2 +- .../installation/weave-gitops-enterprise/index.mdx | 2 +- .../version-0.23.0/pipelines/intro.mdx | 2 +- .../version-0.23.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.23.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.23.0/policy/policy-set.mdx | 2 +- .../version-0.23.0/workspaces/view-workspaces.mdx | 2 +- .../getting-started/install-enterprise.mdx | 2 +- .../version-0.24.0/explorer/configuration.mdx | 4 ++-- .../guides/using-terraform-templates.mdx | 2 +- .../version-0.24.0/pipelines/intro.mdx | 2 +- .../version-0.24.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.24.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.24.0/policy/policy-set.mdx | 2 +- .../version-0.24.0/workspaces/view-workspaces.mdx | 2 +- .../getting-started/install-enterprise.mdx | 2 +- .../version-0.25.0/explorer/configuration.mdx | 2 +- .../version-0.25.0/gitops-templates/cli.mdx | 2 +- .../version-0.25.0/pipelines/intro.mdx | 2 +- .../version-0.25.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.25.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.25.0/policy/policy-set.mdx | 2 +- .../version-0.25.0/workspaces/view-workspaces.mdx | 2 +- .../getting-started/install-enterprise.mdx | 2 +- .../version-0.26.0/explorer/configuration.mdx | 2 +- .../version-0.26.0/gitops-templates/cli.mdx | 2 +- .../version-0.26.0/pipelines/intro.mdx | 2 +- .../version-0.26.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.26.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.26.0/policy/policy-set.mdx | 2 +- .../version-0.26.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.27.0/explorer/configuration.mdx | 2 +- .../version-0.27.0/gitops-templates/cli.mdx | 2 +- .../version-0.27.0/pipelines/intro.mdx | 2 +- .../version-0.27.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.27.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.27.0/policy/policy-set.mdx | 2 +- .../terraform/using-terraform-templates.mdx | 4 ++-- .../version-0.27.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.28.0/explorer/configuration.mdx | 2 +- .../version-0.28.0/gitops-templates/cli.mdx | 2 +- .../version-0.28.0/pipelines/intro.mdx | 2 +- .../version-0.28.0/pipelines/pipeline-templates.mdx | 2 +- .../version-0.28.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.28.0/policy/policy-set.mdx | 2 +- .../terraform/using-terraform-templates.mdx | 4 ++-- .../version-0.28.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.29.0/explorer/configuration.mdx | 2 +- .../version-0.29.0/gitops-templates/cli.mdx | 2 +- .../version-0.29.0/guides/cert-manager.md | 2 +- .../version-0.29.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.29.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.29.0/policy/policy-set.mdx | 2 +- .../terraform/using-terraform-templates.mdx | 4 ++-- .../version-0.29.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.30.0/explorer/configuration.mdx | 2 +- .../version-0.30.0/gitops-templates/cli.mdx | 2 +- .../version-0.30.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.30.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.30.0/policy/policy-set.mdx | 2 +- .../version-0.30.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.31.2/explorer/configuration.mdx | 2 +- .../version-0.31.2/gitops-templates/cli.mdx | 2 +- .../version-0.31.2/pipelines/pipelines-templates.mdx | 2 +- .../version-0.31.2/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.31.2/policy/policy-set.mdx | 2 +- .../version-0.31.2/workspaces/view-workspaces.mdx | 2 +- .../version-0.32.0/explorer/configuration.mdx | 2 +- .../version-0.32.0/gitops-templates/cli.mdx | 2 +- .../version-0.32.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.32.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.32.0/policy/policy-set.mdx | 2 +- .../version-0.32.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.33.0/explorer/configuration.mdx | 2 +- .../version-0.33.0/gitops-templates/cli.mdx | 2 +- .../version-0.33.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.33.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.33.0/policy/policy-set.mdx | 2 +- .../version-0.33.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.34.0/explorer/configuration.mdx | 2 +- .../version-0.34.0/gitops-templates/cli.mdx | 2 +- .../version-0.34.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.34.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.34.0/policy/policy-set.mdx | 2 +- .../version-0.34.0/workspaces/view-workspaces.mdx | 2 +- .../version-0.35.0/explorer/configuration.mdx | 2 +- .../version-0.35.0/gitops-templates/cli.mdx | 2 +- .../version-0.35.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.35.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.35.0/policy/policy-set.mdx | 2 +- .../version-0.35.0/workspaces/view-workspaces.mdx | 2 +- .../getting-started/install-enterprise-cli.mdx | 8 ++++---- .../version-0.36.0/explorer/configuration.mdx | 2 +- .../version-0.36.0/gitops-templates/cli.mdx | 2 +- .../version-0.36.0/operations/monitoring.mdx | 2 +- .../version-0.36.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.36.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.36.0/policy/policy-set.mdx | 2 +- .../version-0.36.0/workspaces/view-workspaces.mdx | 2 +- .../getting-started/install-enterprise-cli.mdx | 8 ++++---- .../version-0.37.0/explorer/configuration.mdx | 2 +- .../version-0.37.0/gitops-templates/cli.mdx | 2 +- .../version-0.37.0/operations/monitoring.mdx | 2 +- .../version-0.37.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.37.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.37.0/policy/policy-set.mdx | 2 +- .../version-0.37.0/workspaces/view-workspaces.mdx | 2 +- .../getting-started/install-enterprise-cli.mdx | 10 +++++----- .../getting-started/install-enterprise.mdx | 2 +- .../version-0.38.0/explorer/configuration.mdx | 2 +- .../version-0.38.0/gitops-templates/cli.mdx | 2 +- .../version-0.38.0/operations/monitoring.mdx | 2 +- .../version-0.38.0/pipelines/pipelines-templates.mdx | 2 +- .../version-0.38.0/policy/commit-time-checks.mdx | 12 ++++++------ .../version-0.38.0/policy/policy-set.mdx | 2 +- .../version-0.38.0/workspaces/view-workspaces.mdx | 2 +- 176 files changed, 307 insertions(+), 307 deletions(-) diff --git a/website/docs/enterprise/getting-started/install-enterprise-cli.mdx b/website/docs/enterprise/getting-started/install-enterprise-cli.mdx index bb41be6bc8..f49e8d3486 100644 --- a/website/docs/enterprise/getting-started/install-enterprise-cli.mdx +++ b/website/docs/enterprise/getting-started/install-enterprise-cli.mdx @@ -94,15 +94,15 @@ Please use the following command to start the installation wizard of Weave GitOp `gitops-ee bootstrap` is a workflow that will take you through the following stages: -1. [Verify Flux](#verifying-flux): verify Flux installation on the Management cluster. +1. [Verify Flux](#verify-flux): verify Flux installation on the Management cluster. 2. (Optional) [Bootstrap Flux](#bootstrap-flux): bootstrap Flux in case is not found. -3. [Verify Entitlement](#verifying-entitlement): verify the Entitlements secret content (username, password, entitlement). +3. [Verify Entitlement](#verify-entitlement): verify the Entitlements secret content (username, password, entitlement). 4. [Configure Git Access](#configure-git-access): configure the access to your configuration repo. -5. [Select WGE version](#selecting-wge-version): from the latest 3 available releases. +5. [Select WGE version](#select-wge-version): from the latest 3 available releases. 6. [Create Cluster User](#create-cluster-user): create a Secret with the username and password for the emergency cluster user. 7. [Configure Dashboard Access](#configure-dashboard-access): choose between 2 methods to access the dashboard either local or external. -8. (Optional) [Configure OIDC](#configure-oidc): to enable login to dashboard via OIDC providers. -9. (Optional) [Extra Components](#extra-components): to install extra components from (Policy Agent, Terraform Controller). +8. (Optional) [Configure OIDC](#optional-configure-oidc): to enable login to dashboard via OIDC providers. +9. (Optional) [Extra Components](#optional-extra-components): to install extra components from (Policy Agent, Terraform Controller). 10. [Access the dashboard](#access-the-dashboard): via the link from the installation success message. #### Verify Flux diff --git a/website/docs/explorer/configuration.mdx b/website/docs/explorer/configuration.mdx index 6980c1f858..a0025f2b69 100644 --- a/website/docs/explorer/configuration.mdx +++ b/website/docs/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/docs/gitops-templates/cli.mdx b/website/docs/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/docs/gitops-templates/cli.mdx +++ b/website/docs/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/docs/operations/monitoring.mdx b/website/docs/operations/monitoring.mdx index 87a1d0b273..2ca6642586 100644 --- a/website/docs/operations/monitoring.mdx +++ b/website/docs/operations/monitoring.mdx @@ -9,7 +9,7 @@ import TierLabel from "./../_components/TierLabel"; # Monitoring -Weave GitOps Enterprise provides monitoring telemetry and tooling for [metrics](#metrics) and [profiling](#profiling). WGE generates [Prometheus](https://prometheus.io/) metrics for monitoring both performance and business operations. +Weave GitOps Enterprise provides monitoring telemetry and tooling for metrics and [profiling](#profiling). WGE generates [Prometheus](https://prometheus.io/) metrics for monitoring both performance and business operations. ## Setup diff --git a/website/docs/pipelines/pipelines-templates.mdx b/website/docs/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/docs/pipelines/pipelines-templates.mdx +++ b/website/docs/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/docs/policy/commit-time-checks.mdx b/website/docs/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/docs/policy/commit-time-checks.mdx +++ b/website/docs/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/docs/policy/policy-set.mdx b/website/docs/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/docs/policy/policy-set.mdx +++ b/website/docs/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/docs/workspaces/view-workspaces.mdx b/website/docs/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/docs/workspaces/view-workspaces.mdx +++ b/website/docs/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.16.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.16.0/gitops-templates/cli.mdx index 57a5392fc2..57b498fc13 100644 --- a/website/versioned_docs/version-0.16.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.16.0/gitops-templates/cli.mdx @@ -24,7 +24,7 @@ Here we're going to talk about the `gitops create template` command that allows ### Installation -See the Weave Gitops Enterprise [installation instructions](../installation/weave-gitops-enterprise/index.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../installation/weave-gitops-enterprise#install-cli) for details on how to install the EE `gitops` CLI tool. ### Getting started diff --git a/website/versioned_docs/version-0.16.0/gitopssets/features.mdx b/website/versioned_docs/version-0.16.0/gitopssets/features.mdx index 22abec1153..bb9afd84ca 100644 --- a/website/versioned_docs/version-0.16.0/gitopssets/features.mdx +++ b/website/versioned_docs/version-0.16.0/gitopssets/features.mdx @@ -14,7 +14,7 @@ Currently rendering templates operates in two phases: * Generate all template parameters from the configured generators * Render all the templates for each set of template parameters -Please read the [security information](#security) below before using this. +Please read the [security information](../intro#security) below before using this. ## Generation @@ -41,7 +41,7 @@ The elements in there are a set JSON of objects[^yaml], there are three in this Other generators provide different sets of keys and values. -The [generators](#generators) documentation below provides more information on what the other generators output. +The generators documentation below provides more information on what the other generators output. ## Rendering templates diff --git a/website/versioned_docs/version-0.16.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.16.0/installation/weave-gitops-enterprise/index.mdx index a5cea13bae..513499fd61 100644 --- a/website/versioned_docs/version-0.16.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.16.0/installation/weave-gitops-enterprise/index.mdx @@ -307,7 +307,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#install-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.16.0/pipelines/intro.mdx b/website/versioned_docs/version-0.16.0/pipelines/intro.mdx index 6fdf9f771a..c763f9cdcf 100644 --- a/website/versioned_docs/version-0.16.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.16.0/pipelines/intro.mdx @@ -26,6 +26,6 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) that you want you application to follow -- [View a pipeline](../getting-started/#view-pipeline-list) and check the status of your deployments. +- [View a pipeline](../getting-started/#view-the-list-of-pipelines) and check the status of your deployments. Now that you know what delivery pipelines can do for you, follow the [guide to get started](../getting-started). \ No newline at end of file diff --git a/website/versioned_docs/version-0.16.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.16.0/workspaces/view-workspaces.mdx index ca4de4e493..ebb9574614 100644 --- a/website/versioned_docs/version-0.16.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.16.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.17.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.17.0/gitops-run/get-started.mdx index b088d3ff09..4bd0b5dc85 100644 --- a/website/versioned_docs/version-0.17.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.17.0/gitops-run/get-started.mdx @@ -17,7 +17,7 @@ sessions, whereas the direct mode is intended for a local cluster. ### Prerequisites #### Required -- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#gitops-cli) +- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#install-the-gitops-cli) #### Optional - This guide uses [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for demonstrations, but it is not required to use GitOps Run diff --git a/website/versioned_docs/version-0.17.0/gitopssets/features.mdx b/website/versioned_docs/version-0.17.0/gitopssets/features.mdx index 22abec1153..bb9afd84ca 100644 --- a/website/versioned_docs/version-0.17.0/gitopssets/features.mdx +++ b/website/versioned_docs/version-0.17.0/gitopssets/features.mdx @@ -14,7 +14,7 @@ Currently rendering templates operates in two phases: * Generate all template parameters from the configured generators * Render all the templates for each set of template parameters -Please read the [security information](#security) below before using this. +Please read the [security information](../intro#security) below before using this. ## Generation @@ -41,7 +41,7 @@ The elements in there are a set JSON of objects[^yaml], there are three in this Other generators provide different sets of keys and values. -The [generators](#generators) documentation below provides more information on what the other generators output. +The generators documentation below provides more information on what the other generators output. ## Rendering templates diff --git a/website/versioned_docs/version-0.17.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.17.0/installation/weave-gitops-enterprise/index.mdx index 16272eee7b..1cf37a1db7 100644 --- a/website/versioned_docs/version-0.17.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.17.0/installation/weave-gitops-enterprise/index.mdx @@ -305,7 +305,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.17.0/pipelines/intro.mdx b/website/versioned_docs/version-0.17.0/pipelines/intro.mdx index 6fdf9f771a..c763f9cdcf 100644 --- a/website/versioned_docs/version-0.17.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.17.0/pipelines/intro.mdx @@ -26,6 +26,6 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) that you want you application to follow -- [View a pipeline](../getting-started/#view-pipeline-list) and check the status of your deployments. +- [View a pipeline](../getting-started/#view-the-list-of-pipelines) and check the status of your deployments. Now that you know what delivery pipelines can do for you, follow the [guide to get started](../getting-started). \ No newline at end of file diff --git a/website/versioned_docs/version-0.17.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.17.0/workspaces/view-workspaces.mdx index ca4de4e493..ebb9574614 100644 --- a/website/versioned_docs/version-0.17.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.17.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.18.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.18.0/gitops-run/get-started.mdx index 9e04ecc4b4..798b0cd313 100644 --- a/website/versioned_docs/version-0.18.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.18.0/gitops-run/get-started.mdx @@ -19,7 +19,7 @@ cluster. ## Prerequisites ### Required -- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#gitops-cli) +- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#install-the-gitops-cli) ### Optional - This guide uses [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for demonstrations, but it is not required to use GitOps Run diff --git a/website/versioned_docs/version-0.18.0/gitopssets/features.mdx b/website/versioned_docs/version-0.18.0/gitopssets/features.mdx index b2b8d9d146..0e8f6d2a39 100644 --- a/website/versioned_docs/version-0.18.0/gitopssets/features.mdx +++ b/website/versioned_docs/version-0.18.0/gitopssets/features.mdx @@ -14,7 +14,7 @@ Currently rendering templates operates in two phases: * Generate all template parameters from the configured generators * Render all the templates for each set of template parameters -Please read the [security information](#security) below before using this. +Please read the [security information](../intro#security) below before using this. ## Generation @@ -41,7 +41,7 @@ The elements in there are a set JSON of objects[^yaml], there are three in this Other generators provide different sets of keys and values. -The [generators](#generators) documentation below provides more information on what the other generators output. +The generators documentation below provides more information on what the other generators output. ## Rendering templates diff --git a/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx index 1a2a22e0b8..ea03ca71bb 100644 --- a/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.18.0/installation/weave-gitops-enterprise/index.mdx @@ -358,7 +358,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.18.0/pipelines/intro.mdx b/website/versioned_docs/version-0.18.0/pipelines/intro.mdx index 342b112bf8..113922feb2 100644 --- a/website/versioned_docs/version-0.18.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.18.0/pipelines/intro.mdx @@ -25,6 +25,6 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) that you want you application to follow -- [View a pipeline](../getting-started/#view-pipeline-list) and check the status of your deployments. +- [View a pipeline](../getting-started/#view-the-list-of-pipelines) and check the status of your deployments. Now that you know what delivery pipelines can do for you, follow the [guide to get started](../getting-started). \ No newline at end of file diff --git a/website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx index 9fab5a69c8..3d4c52b652 100644 --- a/website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.18.0/pipelines/pipeline-templates.mdx @@ -205,7 +205,7 @@ spec:

#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.18.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.18.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.18.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.18.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.19.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.19.0/gitops-run/get-started.mdx index 9e04ecc4b4..798b0cd313 100644 --- a/website/versioned_docs/version-0.19.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.19.0/gitops-run/get-started.mdx @@ -19,7 +19,7 @@ cluster. ## Prerequisites ### Required -- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#gitops-cli) +- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#install-the-gitops-cli) ### Optional - This guide uses [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for demonstrations, but it is not required to use GitOps Run diff --git a/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx index 3e5bf10e99..1fd3be113d 100644 --- a/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.19.0/installation/weave-gitops-enterprise/index.mdx @@ -358,7 +358,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.19.0/pipelines/intro.mdx b/website/versioned_docs/version-0.19.0/pipelines/intro.mdx index 342b112bf8..113922feb2 100644 --- a/website/versioned_docs/version-0.19.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.19.0/pipelines/intro.mdx @@ -25,6 +25,6 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) that you want you application to follow -- [View a pipeline](../getting-started/#view-pipeline-list) and check the status of your deployments. +- [View a pipeline](../getting-started/#view-the-list-of-pipelines) and check the status of your deployments. Now that you know what delivery pipelines can do for you, follow the [guide to get started](../getting-started). \ No newline at end of file diff --git a/website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx index b86aaa7481..3a2a3aae7c 100644 --- a/website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.19.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.19.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.19.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.19.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.19.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.19.0/policy/policy-set.mdx b/website/versioned_docs/version-0.19.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.19.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.19.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.19.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.19.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.19.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.19.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.20.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.20.0/gitops-run/get-started.mdx index 9e04ecc4b4..798b0cd313 100644 --- a/website/versioned_docs/version-0.20.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.20.0/gitops-run/get-started.mdx @@ -19,7 +19,7 @@ cluster. ## Prerequisites ### Required -- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#gitops-cli) +- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#install-the-gitops-cli) ### Optional - This guide uses [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for demonstrations, but it is not required to use GitOps Run diff --git a/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx index 3e5bf10e99..1fd3be113d 100644 --- a/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.20.0/installation/weave-gitops-enterprise/index.mdx @@ -358,7 +358,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.20.0/pipelines/intro.mdx b/website/versioned_docs/version-0.20.0/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.20.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.20.0/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx index b86aaa7481..3a2a3aae7c 100644 --- a/website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.20.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.20.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.20.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.20.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.20.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.20.0/policy/policy-set.mdx b/website/versioned_docs/version-0.20.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.20.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.20.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.20.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.20.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.20.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.20.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.21.1/gitops-run/get-started.mdx b/website/versioned_docs/version-0.21.1/gitops-run/get-started.mdx index 9e04ecc4b4..798b0cd313 100644 --- a/website/versioned_docs/version-0.21.1/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.21.1/gitops-run/get-started.mdx @@ -19,7 +19,7 @@ cluster. ## Prerequisites ### Required -- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#gitops-cli) +- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#install-the-gitops-cli) ### Optional - This guide uses [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for demonstrations, but it is not required to use GitOps Run diff --git a/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/index.mdx index 1c36fd972f..71cdbfce0e 100644 --- a/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.21.1/installation/weave-gitops-enterprise/index.mdx @@ -389,7 +389,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.21.1/pipelines/intro.mdx b/website/versioned_docs/version-0.21.1/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.21.1/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.21.1/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.21.1/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.21.1/pipelines/pipeline-templates.mdx index b86aaa7481..3a2a3aae7c 100644 --- a/website/versioned_docs/version-0.21.1/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.21.1/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.21.1/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.21.1/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.21.1/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.21.1/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.21.1/policy/policy-set.mdx b/website/versioned_docs/version-0.21.1/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.21.1/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.21.1/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.21.1/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.21.1/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.21.1/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.21.1/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.21.2/gitops-run/get-started.mdx b/website/versioned_docs/version-0.21.2/gitops-run/get-started.mdx index 9e04ecc4b4..798b0cd313 100644 --- a/website/versioned_docs/version-0.21.2/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.21.2/gitops-run/get-started.mdx @@ -19,7 +19,7 @@ cluster. ## Prerequisites ### Required -- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#gitops-cli) +- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#install-the-gitops-cli) ### Optional - This guide uses [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for demonstrations, but it is not required to use GitOps Run diff --git a/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/index.mdx index 1c36fd972f..71cdbfce0e 100644 --- a/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.21.2/installation/weave-gitops-enterprise/index.mdx @@ -389,7 +389,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.21.2/pipelines/intro.mdx b/website/versioned_docs/version-0.21.2/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.21.2/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.21.2/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.21.2/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.21.2/pipelines/pipeline-templates.mdx index b86aaa7481..3a2a3aae7c 100644 --- a/website/versioned_docs/version-0.21.2/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.21.2/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.21.2/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.21.2/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.21.2/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.21.2/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.21.2/policy/policy-set.mdx b/website/versioned_docs/version-0.21.2/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.21.2/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.21.2/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.21.2/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.21.2/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.21.2/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.21.2/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.22.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.22.0/gitops-run/get-started.mdx index 9e04ecc4b4..798b0cd313 100644 --- a/website/versioned_docs/version-0.22.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.22.0/gitops-run/get-started.mdx @@ -19,7 +19,7 @@ cluster. ## Prerequisites ### Required -- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#gitops-cli) +- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#install-the-gitops-cli) ### Optional - This guide uses [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for demonstrations, but it is not required to use GitOps Run diff --git a/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/index.mdx index 28210e18e6..8571c928ff 100644 --- a/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.22.0/installation/weave-gitops-enterprise/index.mdx @@ -389,7 +389,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.22.0/pipelines/intro.mdx b/website/versioned_docs/version-0.22.0/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.22.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.22.0/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.22.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.22.0/pipelines/pipeline-templates.mdx index b86aaa7481..3a2a3aae7c 100644 --- a/website/versioned_docs/version-0.22.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.22.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.22.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.22.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.22.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.22.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.22.0/policy/policy-set.mdx b/website/versioned_docs/version-0.22.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.22.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.22.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.22.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.22.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.22.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.22.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.23.0/explorer/configuration.mdx b/website/versioned_docs/version-0.23.0/explorer/configuration.mdx index db89f26546..7ae55bed03 100644 --- a/website/versioned_docs/version-0.23.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.23.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../../getting-started/ui#applications-view) or [Sources](../../getting-started/ui#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.23.0/gitops-run/get-started.mdx b/website/versioned_docs/version-0.23.0/gitops-run/get-started.mdx index 9e04ecc4b4..798b0cd313 100644 --- a/website/versioned_docs/version-0.23.0/gitops-run/get-started.mdx +++ b/website/versioned_docs/version-0.23.0/gitops-run/get-started.mdx @@ -19,7 +19,7 @@ cluster. ## Prerequisites ### Required -- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#gitops-cli) +- Install the GitOps CLI. See [the installation](../installation/weave-gitops.mdx#install-the-gitops-cli) ### Optional - This guide uses [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for demonstrations, but it is not required to use GitOps Run diff --git a/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/index.mdx b/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/index.mdx index 28210e18e6..8571c928ff 100644 --- a/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/index.mdx +++ b/website/versioned_docs/version-0.23.0/installation/weave-gitops-enterprise/index.mdx @@ -389,7 +389,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.23.0/pipelines/intro.mdx b/website/versioned_docs/version-0.23.0/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.23.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.23.0/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.23.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.23.0/pipelines/pipeline-templates.mdx index b86aaa7481..3a2a3aae7c 100644 --- a/website/versioned_docs/version-0.23.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.23.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.23.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.23.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.23.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.23.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.23.0/policy/policy-set.mdx b/website/versioned_docs/version-0.23.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.23.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.23.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.23.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.23.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.23.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.23.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise.mdx index 7b46ba4fe8..c88113a53a 100644 --- a/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.24.0/enterprise/getting-started/install-enterprise.mdx @@ -386,7 +386,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. In order to login to the WGE UI, you need to generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. There are several different ways to generate a bcrypt hash, this guide uses `gitops get bcrypt-hash` from our CLI, which can be installed by following -the instructions [here](#gitops-cli). +the instructions [here](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.24.0/explorer/configuration.mdx b/website/versioned_docs/version-0.24.0/explorer/configuration.mdx index a03ae188d2..d6eb288f06 100644 --- a/website/versioned_docs/version-0.24.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.24.0/explorer/configuration.mdx @@ -22,9 +22,9 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.enableExplorer`: feature flag to control whether Explorer is enabled. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for -other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) +other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.24.0/guides/using-terraform-templates.mdx b/website/versioned_docs/version-0.24.0/guides/using-terraform-templates.mdx index ed78bca35b..e177939db5 100644 --- a/website/versioned_docs/version-0.24.0/guides/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.24.0/guides/using-terraform-templates.mdx @@ -14,7 +14,7 @@ This guide will show you how to use a template to create a Terraform resource in ## CLI guide ### Pre-requisites -- Install [Weave GitOps Enterprise](../enterprise/getting-started/install-enterprise.mdx) with [TF-Controller installed](../enterprise/getting-started/install-enterprise.mdx#optional-install-the-terraform-controller) and [TLS enabled](../configuration/tls.md). +- Install [Weave GitOps Enterprise](../enterprise/getting-started/install-enterprise.mdx) with [TF-Controller installed](../enterprise/getting-started/install-enterprise.mdx#optional-install-the-tf-controller) and [TLS enabled](../configuration/tls.md). ### 1. Add a template to your cluster diff --git a/website/versioned_docs/version-0.24.0/pipelines/intro.mdx b/website/versioned_docs/version-0.24.0/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.24.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.24.0/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.24.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.24.0/pipelines/pipeline-templates.mdx index b86aaa7481..3a2a3aae7c 100644 --- a/website/versioned_docs/version-0.24.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.24.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.24.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.24.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.24.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.24.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.24.0/policy/policy-set.mdx b/website/versioned_docs/version-0.24.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.24.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.24.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.24.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.24.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.24.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.24.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise.mdx index 38c85a9545..0e58a65ccf 100644 --- a/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.25.0/enterprise/getting-started/install-enterprise.mdx @@ -399,7 +399,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. To login to the WGE UI, generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. -There are several different ways to generate a bcrypt hash. This guide uses `gitops get bcrypt-hash` from our CLI, which you can install with [these instructions](#gitops-cli). +There are several different ways to generate a bcrypt hash. This guide uses `gitops get bcrypt-hash` from our CLI, which you can install with [these instructions](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.25.0/explorer/configuration.mdx b/website/versioned_docs/version-0.25.0/explorer/configuration.mdx index ebded7cb3e..b6f66ae217 100644 --- a/website/versioned_docs/version-0.25.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.25.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.25.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.25.0/gitops-templates/cli.mdx index 03c985081b..79cfbe24c7 100644 --- a/website/versioned_docs/version-0.25.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.25.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.25.0/pipelines/intro.mdx b/website/versioned_docs/version-0.25.0/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.25.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.25.0/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.25.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.25.0/pipelines/pipeline-templates.mdx index 24386e0d92..e512a8586a 100644 --- a/website/versioned_docs/version-0.25.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.25.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.25.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.25.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.25.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.25.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.25.0/policy/policy-set.mdx b/website/versioned_docs/version-0.25.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.25.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.25.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.25.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.25.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.25.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.25.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise.mdx index 38c85a9545..0e58a65ccf 100644 --- a/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.26.0/enterprise/getting-started/install-enterprise.mdx @@ -399,7 +399,7 @@ Flux will reconcile the helm-release and WGE will be deployed into the cluster. To login to the WGE UI, generate a bcrypt hash for your chosen password and store it as a secret in the Kubernetes cluster. -There are several different ways to generate a bcrypt hash. This guide uses `gitops get bcrypt-hash` from our CLI, which you can install with [these instructions](#gitops-cli). +There are several different ways to generate a bcrypt hash. This guide uses `gitops get bcrypt-hash` from our CLI, which you can install with [these instructions](#7-install-the-cli). ```bash PASSWORD="" diff --git a/website/versioned_docs/version-0.26.0/explorer/configuration.mdx b/website/versioned_docs/version-0.26.0/explorer/configuration.mdx index ebded7cb3e..b6f66ae217 100644 --- a/website/versioned_docs/version-0.26.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.26.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.26.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.26.0/gitops-templates/cli.mdx index 03c985081b..79cfbe24c7 100644 --- a/website/versioned_docs/version-0.26.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.26.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.26.0/pipelines/intro.mdx b/website/versioned_docs/version-0.26.0/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.26.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.26.0/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.26.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.26.0/pipelines/pipeline-templates.mdx index 24386e0d92..e512a8586a 100644 --- a/website/versioned_docs/version-0.26.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.26.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.26.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.26.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.26.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.26.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.26.0/policy/policy-set.mdx b/website/versioned_docs/version-0.26.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.26.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.26.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.26.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.26.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.26.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.26.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.27.0/explorer/configuration.mdx b/website/versioned_docs/version-0.27.0/explorer/configuration.mdx index 8cb989e4af..db2bc13135 100644 --- a/website/versioned_docs/version-0.27.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.27.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.27.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.27.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.27.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.27.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.27.0/pipelines/intro.mdx b/website/versioned_docs/version-0.27.0/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.27.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.27.0/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.27.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.27.0/pipelines/pipeline-templates.mdx index 24386e0d92..e512a8586a 100644 --- a/website/versioned_docs/version-0.27.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.27.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.27.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.27.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.27.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.27.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.27.0/policy/policy-set.mdx b/website/versioned_docs/version-0.27.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.27.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.27.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.27.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.27.0/terraform/using-terraform-templates.mdx index ed96296f05..e4f4809271 100644 --- a/website/versioned_docs/version-0.27.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.27.0/terraform/using-terraform-templates.mdx @@ -19,7 +19,7 @@ This guide will show you how to use a template to create a Terraform resource in ### 1. Add a template to your cluster -Add the following template to a path in your Git repository that is synced by Flux. For example, in the [Installation guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set the path that is synced by Flux to `./clusters/management`. +Add the following template to a path in your Git repository that is synced by Flux. For example, in the [Installation guide](../enterprise/getting-started/install-enterprise.mdx#5-install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set the path that is synced by Flux to `./clusters/management`. Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. @@ -251,7 +251,7 @@ resource "aws_rds_cluster_instance" "cluster_instance" {
-Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. +Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#5-install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`.
Expand to see Terraform manifest at diff --git a/website/versioned_docs/version-0.27.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.27.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.27.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.27.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.28.0/explorer/configuration.mdx b/website/versioned_docs/version-0.28.0/explorer/configuration.mdx index 8cb989e4af..db2bc13135 100644 --- a/website/versioned_docs/version-0.28.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.28.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.28.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.28.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.28.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.28.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.28.0/pipelines/intro.mdx b/website/versioned_docs/version-0.28.0/pipelines/intro.mdx index 862e53f414..ceafaf3b50 100644 --- a/website/versioned_docs/version-0.28.0/pipelines/intro.mdx +++ b/website/versioned_docs/version-0.28.0/pipelines/intro.mdx @@ -25,7 +25,7 @@ your gitops applications. As part of Weave GitOps Enterprise, you can - [Define a delivery pipeline](../getting-started/#define-a-pipeline) for an application that is packaged as a Helm chart. -- [Visualise a pipeline](../getting-started/#view-pipeline-list) and check the current status and versions of your deployments. +- [Visualise a pipeline](../getting-started/#view-the-list-of-pipelines) and check the current status and versions of your deployments. - [Promote applications](../promoting-applications) either automatically or manually via the Weave GitOps Enterprise dashboard. - Notify other CI tools such as [Tekton](../pipelines-with-tekton) and [Jenkins](../pipelines-with-jenkins) of an application promotion. diff --git a/website/versioned_docs/version-0.28.0/pipelines/pipeline-templates.mdx b/website/versioned_docs/version-0.28.0/pipelines/pipeline-templates.mdx index 24386e0d92..e512a8586a 100644 --- a/website/versioned_docs/version-0.28.0/pipelines/pipeline-templates.mdx +++ b/website/versioned_docs/version-0.28.0/pipelines/pipeline-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.28.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.28.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.28.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.28.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.28.0/policy/policy-set.mdx b/website/versioned_docs/version-0.28.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.28.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.28.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.28.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.28.0/terraform/using-terraform-templates.mdx index ed96296f05..e4f4809271 100644 --- a/website/versioned_docs/version-0.28.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.28.0/terraform/using-terraform-templates.mdx @@ -19,7 +19,7 @@ This guide will show you how to use a template to create a Terraform resource in ### 1. Add a template to your cluster -Add the following template to a path in your Git repository that is synced by Flux. For example, in the [Installation guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set the path that is synced by Flux to `./clusters/management`. +Add the following template to a path in your Git repository that is synced by Flux. For example, in the [Installation guide](../enterprise/getting-started/install-enterprise.mdx#5-install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set the path that is synced by Flux to `./clusters/management`. Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. @@ -251,7 +251,7 @@ resource "aws_rds_cluster_instance" "cluster_instance" {
-Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. +Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#5-install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`.
Expand to see Terraform manifest at diff --git a/website/versioned_docs/version-0.28.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.28.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.28.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.28.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.29.0/explorer/configuration.mdx b/website/versioned_docs/version-0.29.0/explorer/configuration.mdx index 8cb989e4af..db2bc13135 100644 --- a/website/versioned_docs/version-0.29.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.29.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.29.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.29.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.29.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.29.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.29.0/guides/cert-manager.md b/website/versioned_docs/version-0.29.0/guides/cert-manager.md index 56837e0dee..a8f77d3224 100644 --- a/website/versioned_docs/version-0.29.0/guides/cert-manager.md +++ b/website/versioned_docs/version-0.29.0/guides/cert-manager.md @@ -105,4 +105,4 @@ spec: Once this `ClusterIssuer` resource is installed, the cluster is now configured to request and use certificates generated by cert-manager. -This could be manually requested through the creation of a [Certificate resource](https://cert-manager.io/docs/usage/certificate/#creating-certificate-resources) or configured to be automatic, as shown in our [WGE installation](../enterprise/getting-started/install-enterprise.mdx#securing-access-to-the-dashboard) guide. +This could be manually requested through the creation of a [Certificate resource](https://cert-manager.io/docs/usage/certificate/#creating-certificate-resources) or configured to be automatic, as shown in our [WGE installation](../../enterprise/getting-started/install-enterprise) guide. diff --git a/website/versioned_docs/version-0.29.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.29.0/pipelines/pipelines-templates.mdx index 24386e0d92..e512a8586a 100644 --- a/website/versioned_docs/version-0.29.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.29.0/pipelines/pipelines-templates.mdx @@ -206,7 +206,7 @@ spec:
#### Git credentials -For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials - see instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion marker to be added to HelmRelease in `Second-Environment` A comment would need to be added to the HelmRelease or Kustomization patch where the `spec.chart.spec.version` is defined. diff --git a/website/versioned_docs/version-0.29.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.29.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.29.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.29.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.29.0/policy/policy-set.mdx b/website/versioned_docs/version-0.29.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.29.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.29.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.29.0/terraform/using-terraform-templates.mdx b/website/versioned_docs/version-0.29.0/terraform/using-terraform-templates.mdx index ed96296f05..e4f4809271 100644 --- a/website/versioned_docs/version-0.29.0/terraform/using-terraform-templates.mdx +++ b/website/versioned_docs/version-0.29.0/terraform/using-terraform-templates.mdx @@ -19,7 +19,7 @@ This guide will show you how to use a template to create a Terraform resource in ### 1. Add a template to your cluster -Add the following template to a path in your Git repository that is synced by Flux. For example, in the [Installation guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set the path that is synced by Flux to `./clusters/management`. +Add the following template to a path in your Git repository that is synced by Flux. For example, in the [Installation guide](../enterprise/getting-started/install-enterprise.mdx#5-install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set the path that is synced by Flux to `./clusters/management`. Commit and push these changes. Once a template is available in the cluster, it can be used to create a resource, which will be shown in the next step. @@ -251,7 +251,7 @@ resource "aws_rds_cluster_instance" "cluster_instance" {
-Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`. +Add the following template to a path in your Git repository that is synced by Flux. In the [quickstart guide](../enterprise/getting-started/install-enterprise.mdx#5-install-flux-onto-your-cluster-with-the-flux-bootstrap-command), we set this path to `./clusters/management`.
Expand to see Terraform manifest at diff --git a/website/versioned_docs/version-0.29.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.29.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.29.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.29.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.30.0/explorer/configuration.mdx b/website/versioned_docs/version-0.30.0/explorer/configuration.mdx index 72d6fd64c8..aef35c3666 100644 --- a/website/versioned_docs/version-0.30.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.30.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.30.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.30.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.30.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.30.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.30.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.30.0/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.30.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.30.0/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.30.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.30.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.30.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.30.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.30.0/policy/policy-set.mdx b/website/versioned_docs/version-0.30.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.30.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.30.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.30.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.30.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.30.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.30.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.31.2/explorer/configuration.mdx b/website/versioned_docs/version-0.31.2/explorer/configuration.mdx index 2a71b6d457..3b5a3f6606 100644 --- a/website/versioned_docs/version-0.31.2/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.31.2/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.31.2/gitops-templates/cli.mdx b/website/versioned_docs/version-0.31.2/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.31.2/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.31.2/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.31.2/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.31.2/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.31.2/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.31.2/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.31.2/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.31.2/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.31.2/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.31.2/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.31.2/policy/policy-set.mdx b/website/versioned_docs/version-0.31.2/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.31.2/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.31.2/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.31.2/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.31.2/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.31.2/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.31.2/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.32.0/explorer/configuration.mdx b/website/versioned_docs/version-0.32.0/explorer/configuration.mdx index 2a71b6d457..3b5a3f6606 100644 --- a/website/versioned_docs/version-0.32.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.32.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.32.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.32.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.32.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.32.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.32.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.32.0/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.32.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.32.0/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.32.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.32.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.32.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.32.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.32.0/policy/policy-set.mdx b/website/versioned_docs/version-0.32.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.32.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.32.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.32.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.32.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.32.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.32.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.33.0/explorer/configuration.mdx b/website/versioned_docs/version-0.33.0/explorer/configuration.mdx index 10926ab64e..042eba966a 100644 --- a/website/versioned_docs/version-0.33.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.33.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.33.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.33.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.33.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.33.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.33.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.33.0/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.33.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.33.0/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.33.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.33.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.33.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.33.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.33.0/policy/policy-set.mdx b/website/versioned_docs/version-0.33.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.33.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.33.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.33.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.33.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.33.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.33.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.34.0/explorer/configuration.mdx b/website/versioned_docs/version-0.34.0/explorer/configuration.mdx index 10926ab64e..042eba966a 100644 --- a/website/versioned_docs/version-0.34.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.34.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.34.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.34.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.34.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.34.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.34.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.34.0/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.34.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.34.0/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.34.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.34.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.34.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.34.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.34.0/policy/policy-set.mdx b/website/versioned_docs/version-0.34.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.34.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.34.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.34.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.34.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.34.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.34.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.35.0/explorer/configuration.mdx b/website/versioned_docs/version-0.35.0/explorer/configuration.mdx index 10926ab64e..042eba966a 100644 --- a/website/versioned_docs/version-0.35.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.35.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.35.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.35.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.35.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.35.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.35.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.35.0/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.35.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.35.0/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.35.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.35.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.35.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.35.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.35.0/policy/policy-set.mdx b/website/versioned_docs/version-0.35.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.35.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.35.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.35.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.35.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.35.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.35.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-cli.mdx b/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-cli.mdx index aa7fbe03fd..69b1769040 100644 --- a/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-cli.mdx +++ b/website/versioned_docs/version-0.36.0/enterprise/getting-started/install-enterprise-cli.mdx @@ -90,15 +90,15 @@ Please use the following command to start the installation wizard of Weave GitOp `gitops-ee bootstrap` is a workflow that will take you through the following stages: -1. [Verify Flux](#verifying-flux): verify Flux installation on the Management cluster. +1. [Verify Flux](#verify-flux): verify Flux installation on the Management cluster. 2. (Optional) [Bootstrap Flux](#bootstrap-flux): bootstrap Flux in case is not found. -3. [Verify Entitlement](#verifying-entitlement): verify the Entitlements secret content (username, password, entitlement). +3. [Verify Entitlement](#verify-entitlement): verify the Entitlements secret content (username, password, entitlement). 4. [Configure Git Access](#configure-git-access): configure the access to your configuration repo. -5. [Select WGE version](#selecting-wge-version): from the latest 3 available releases. +5. [Select WGE version](#select-wge-version): from the latest 3 available releases. 6. [Create Cluster User](#create-cluster-user): create a Secret with the username and password for the emergency cluster user. 7. [Configure Dashboard Access](#configure-dashboard-access): choose between 2 methods to access the dashboard either local or external. 8. [Access the dashboard](#access-the-dashboard): via the link from the installation success message. -9. (Optional) [Configure OIDC](#configure-oidc): to enable login to dashboard via OIDC providers. +9. (Optional) [Configure OIDC](#optional-configure-oidc): to enable login to dashboard via OIDC providers. #### Verify Flux diff --git a/website/versioned_docs/version-0.36.0/explorer/configuration.mdx b/website/versioned_docs/version-0.36.0/explorer/configuration.mdx index 10926ab64e..042eba966a 100644 --- a/website/versioned_docs/version-0.36.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.36.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.36.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.36.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.36.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.36.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.36.0/operations/monitoring.mdx b/website/versioned_docs/version-0.36.0/operations/monitoring.mdx index 87a1d0b273..2ca6642586 100644 --- a/website/versioned_docs/version-0.36.0/operations/monitoring.mdx +++ b/website/versioned_docs/version-0.36.0/operations/monitoring.mdx @@ -9,7 +9,7 @@ import TierLabel from "./../_components/TierLabel"; # Monitoring -Weave GitOps Enterprise provides monitoring telemetry and tooling for [metrics](#metrics) and [profiling](#profiling). WGE generates [Prometheus](https://prometheus.io/) metrics for monitoring both performance and business operations. +Weave GitOps Enterprise provides monitoring telemetry and tooling for metrics and [profiling](#profiling). WGE generates [Prometheus](https://prometheus.io/) metrics for monitoring both performance and business operations. ## Setup diff --git a/website/versioned_docs/version-0.36.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.36.0/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.36.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.36.0/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.36.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.36.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.36.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.36.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.36.0/policy/policy-set.mdx b/website/versioned_docs/version-0.36.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.36.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.36.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.36.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.36.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.36.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.36.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-cli.mdx b/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-cli.mdx index aa7fbe03fd..69b1769040 100644 --- a/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-cli.mdx +++ b/website/versioned_docs/version-0.37.0/enterprise/getting-started/install-enterprise-cli.mdx @@ -90,15 +90,15 @@ Please use the following command to start the installation wizard of Weave GitOp `gitops-ee bootstrap` is a workflow that will take you through the following stages: -1. [Verify Flux](#verifying-flux): verify Flux installation on the Management cluster. +1. [Verify Flux](#verify-flux): verify Flux installation on the Management cluster. 2. (Optional) [Bootstrap Flux](#bootstrap-flux): bootstrap Flux in case is not found. -3. [Verify Entitlement](#verifying-entitlement): verify the Entitlements secret content (username, password, entitlement). +3. [Verify Entitlement](#verify-entitlement): verify the Entitlements secret content (username, password, entitlement). 4. [Configure Git Access](#configure-git-access): configure the access to your configuration repo. -5. [Select WGE version](#selecting-wge-version): from the latest 3 available releases. +5. [Select WGE version](#select-wge-version): from the latest 3 available releases. 6. [Create Cluster User](#create-cluster-user): create a Secret with the username and password for the emergency cluster user. 7. [Configure Dashboard Access](#configure-dashboard-access): choose between 2 methods to access the dashboard either local or external. 8. [Access the dashboard](#access-the-dashboard): via the link from the installation success message. -9. (Optional) [Configure OIDC](#configure-oidc): to enable login to dashboard via OIDC providers. +9. (Optional) [Configure OIDC](#optional-configure-oidc): to enable login to dashboard via OIDC providers. #### Verify Flux diff --git a/website/versioned_docs/version-0.37.0/explorer/configuration.mdx b/website/versioned_docs/version-0.37.0/explorer/configuration.mdx index 10926ab64e..042eba966a 100644 --- a/website/versioned_docs/version-0.37.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.37.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.37.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.37.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.37.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.37.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.37.0/operations/monitoring.mdx b/website/versioned_docs/version-0.37.0/operations/monitoring.mdx index 87a1d0b273..2ca6642586 100644 --- a/website/versioned_docs/version-0.37.0/operations/monitoring.mdx +++ b/website/versioned_docs/version-0.37.0/operations/monitoring.mdx @@ -9,7 +9,7 @@ import TierLabel from "./../_components/TierLabel"; # Monitoring -Weave GitOps Enterprise provides monitoring telemetry and tooling for [metrics](#metrics) and [profiling](#profiling). WGE generates [Prometheus](https://prometheus.io/) metrics for monitoring both performance and business operations. +Weave GitOps Enterprise provides monitoring telemetry and tooling for metrics and [profiling](#profiling). WGE generates [Prometheus](https://prometheus.io/) metrics for monitoring both performance and business operations. ## Setup diff --git a/website/versioned_docs/version-0.37.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.37.0/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.37.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.37.0/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.37.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.37.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.37.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.37.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.37.0/policy/policy-set.mdx b/website/versioned_docs/version-0.37.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.37.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.37.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.37.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.37.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.37.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.37.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace. diff --git a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-cli.mdx b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-cli.mdx index 980d41d503..fbb37bb510 100644 --- a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-cli.mdx +++ b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise-cli.mdx @@ -91,15 +91,15 @@ Please use the following command to start the installation wizard of Weave GitOp `gitops-ee bootstrap` is a workflow that will take you through the following stages: -1. [Verify Flux](#verifying-flux): verify Flux installation on the Management cluster. +1. [Verify Flux](#verify-flux): verify Flux installation on the Management cluster. 2. (Optional) [Bootstrap Flux](#bootstrap-flux): bootstrap Flux in case is not found. -3. [Verify Entitlement](#verifying-entitlement): verify the Entitlements secret content (username, password, entitlement). +3. [Verify Entitlement](#verify-entitlement): verify the Entitlements secret content (username, password, entitlement). 4. [Configure Git Access](#configure-git-access): configure the access to your configuration repo. -5. [Select WGE version](#selecting-wge-version): from the latest 3 available releases. +5. [Select WGE version](#select-wge-version): from the latest 3 available releases. 6. [Create Cluster User](#create-cluster-user): create a Secret with the username and password for the emergency cluster user. 7. [Configure Dashboard Access](#configure-dashboard-access): choose between 2 methods to access the dashboard either local or external. -8. (Optional) [Configure OIDC](#configure-oidc): to enable login to dashboard via OIDC providers. -9. (Optional) [Extra Components](#extra-components): to install extra components from (Policy Agent, Terraform Controller). +8. (Optional) [Configure OIDC](#optional-configure-oidc): to enable login to dashboard via OIDC providers. +9. (Optional) [Extra Components](#optional-extra-components): to install extra components from (Policy Agent, Terraform Controller). 10. [Access the dashboard](#access-the-dashboard): via the link from the installation success message. #### Verify Flux diff --git a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise.mdx b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise.mdx index 4bbb072598..cb50cf7518 100644 --- a/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise.mdx +++ b/website/versioned_docs/version-0.38.0/enterprise/getting-started/install-enterprise.mdx @@ -13,7 +13,7 @@ import oauthAzureDevOps from '/img/oauth-azure-devops.png'; import oauthAzureDevOpsSuccess from '/img/oauth-azure-devops-success.png'; # Install Weave GitOps Enterprise - +f :::info To purchase an entitlement to Weave GitOps Enterprise, please contact [info@weaveworks.org](mailto:info@weaveworks.org). ::: diff --git a/website/versioned_docs/version-0.38.0/explorer/configuration.mdx b/website/versioned_docs/version-0.38.0/explorer/configuration.mdx index 10926ab64e..042eba966a 100644 --- a/website/versioned_docs/version-0.38.0/explorer/configuration.mdx +++ b/website/versioned_docs/version-0.38.0/explorer/configuration.mdx @@ -24,7 +24,7 @@ The following configuration options are available for you to setup Explorer. - `.spec.values.useQueryServiceBackend`: feature flag to control whether you want to leverage Explorer backend capabilities for other UI experiences like [Applications](../open-source/getting-started/ui-OSS.mdx#the-applications-view) or [Sources](../open-source/getting-started/ui-OSS.mdx#the-sources-view) - `.spec.values.explorer.collector.serviceAccount`: ServiceAccount `name` and `namespace` that explorer collector will use to impersonate -in leaf clusters. Make sure you read [authz for collector](#Authentication_and_Authorization_for_collecting) before setting it. Default +in leaf clusters. Make sure you read [authz for collector](#authentication-and-authorization-for-collecting) before setting it. Default values are `name: collector`, `namespace: flux-system`. You should specify them in your HelmRelease values: diff --git a/website/versioned_docs/version-0.38.0/gitops-templates/cli.mdx b/website/versioned_docs/version-0.38.0/gitops-templates/cli.mdx index ca9231dc03..b685363d0f 100644 --- a/website/versioned_docs/version-0.38.0/gitops-templates/cli.mdx +++ b/website/versioned_docs/version-0.38.0/gitops-templates/cli.mdx @@ -41,7 +41,7 @@ value of these two annotations: ## Installation -See the Weave Gitops Enterprise [installation instructions](../enterprise/getting-started/install-enterprise.mdx#7-install-the-cli) for details on how to install the EE `gitops` CLI tool. +See the Weave Gitops Enterprise [installation instructions](../../enterprise/getting-started/install-enterprise#install-the-weave-gitops-enterprise-cli-tool) for details on how to install the EE `gitops` CLI tool. ## Getting started diff --git a/website/versioned_docs/version-0.38.0/operations/monitoring.mdx b/website/versioned_docs/version-0.38.0/operations/monitoring.mdx index 87a1d0b273..2ca6642586 100644 --- a/website/versioned_docs/version-0.38.0/operations/monitoring.mdx +++ b/website/versioned_docs/version-0.38.0/operations/monitoring.mdx @@ -9,7 +9,7 @@ import TierLabel from "./../_components/TierLabel"; # Monitoring -Weave GitOps Enterprise provides monitoring telemetry and tooling for [metrics](#metrics) and [profiling](#profiling). WGE generates [Prometheus](https://prometheus.io/) metrics for monitoring both performance and business operations. +Weave GitOps Enterprise provides monitoring telemetry and tooling for metrics and [profiling](#profiling). WGE generates [Prometheus](https://prometheus.io/) metrics for monitoring both performance and business operations. ## Setup diff --git a/website/versioned_docs/version-0.38.0/pipelines/pipelines-templates.mdx b/website/versioned_docs/version-0.38.0/pipelines/pipelines-templates.mdx index 4d7f32c7a3..ee48bcd199 100644 --- a/website/versioned_docs/version-0.38.0/pipelines/pipelines-templates.mdx +++ b/website/versioned_docs/version-0.38.0/pipelines/pipelines-templates.mdx @@ -208,7 +208,7 @@ spec: #### Git Credentials -For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#create-credentials-secret) documentation. +For guidance on configuring credentials, find instructions in the [Promoting Applications](../promoting-applications#credentials-secret) documentation. #### Promotion Marker Added to HelmRelease in `Second-Environment` diff --git a/website/versioned_docs/version-0.38.0/policy/commit-time-checks.mdx b/website/versioned_docs/version-0.38.0/policy/commit-time-checks.mdx index 9883645d8e..9687ece77d 100644 --- a/website/versioned_docs/version-0.38.0/policy/commit-time-checks.mdx +++ b/website/versioned_docs/version-0.38.0/policy/commit-time-checks.mdx @@ -73,12 +73,12 @@ resources: ``` --- ## Supported CI/CD -- [x] [Github](#github) -- [x] [Github Enterprise](#github) -- [x] [Gitlab](#gitlab) -- [x] [Bitbucket](#bitbucket) -- [x] [Circle CI](#circle-ci) -- [x] [Azure Devops](#azure-devops) +- [x] [Github](#usecase-github) +- [x] [Github Enterprise](#usecase-github) +- [x] [Gitlab](#usecase-gitlab) +- [x] [Bitbucket](#usecase-bitbucket) +- [x] [Circle CI](#usecase-circleci) +- [x] [Azure Devops](#usecase-azure-devops) --- ## Auto-Remediation Weave validator supports auto-remediation functionality which creates a pull request with suggested fixes to remediate the reported violations. diff --git a/website/versioned_docs/version-0.38.0/policy/policy-set.mdx b/website/versioned_docs/version-0.38.0/policy/policy-set.mdx index ba40e8ed71..a5b2c5edb4 100644 --- a/website/versioned_docs/version-0.38.0/policy/policy-set.mdx +++ b/website/versioned_docs/version-0.38.0/policy/policy-set.mdx @@ -13,7 +13,7 @@ In each mode, the agent will list all the PolicySets of this mode and check whic If there are no PolicySets found for a certain mode, all policies will be applied during this mode. -> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](#admission) mode, event if it is not selected in the `admission` policysets +> Note: [Tenant Policies](./policy.mdx#tenant-policy) is always active in the [Admission](../weave-policy-profile#admission) mode, event if it is not selected in the `admission` policysets **Example** ```yaml diff --git a/website/versioned_docs/version-0.38.0/workspaces/view-workspaces.mdx b/website/versioned_docs/version-0.38.0/workspaces/view-workspaces.mdx index 43e0bd361f..92fa1243cd 100644 --- a/website/versioned_docs/version-0.38.0/workspaces/view-workspaces.mdx +++ b/website/versioned_docs/version-0.38.0/workspaces/view-workspaces.mdx @@ -19,7 +19,7 @@ This view lists workspaces across all clusters. You can filter workspaces by the ## Workspace Details View -You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#Workspaces-list-view). +You can go to this view by clicking on the name of the workspace in the [Workspaces List View](#workspaces-list-view). In this view you can see all details of the workspace such as its name, namespace, and all resources related to this workspace.