- Sort Score
- Result 10 results
- Languages All
Results 51 - 60 of 430 for Secrets (0.06 sec)
-
.github/workflows/invalid_question.yml
runs-on: ubuntu-latest env: ACTIONS_STEP_DEBUG: true steps: - name: Close Stale Issues uses: actions/stale@v8 with: repo-token: ${{ secrets.GITHUB_TOKEN }}
Registered: Sun Nov 03 09:35:10 UTC 2024 - Last Modified: Tue Apr 11 02:27:05 UTC 2023 - 1.2K bytes - Viewed (0) -
.github/workflows/labeler.yml
steps: - uses: docker://agilepathway/pull-request-label-checker:latest with: one_of: breaking,security,feature,bug,refactor,upgrade,docs,lang-all,internal
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Mon Oct 07 20:11:20 UTC 2024 - 828 bytes - Viewed (0) -
.github/workflows/missing_playground.yml
runs-on: ubuntu-latest env: ACTIONS_STEP_DEBUG: true steps: - name: Close Stale Issues uses: actions/stale@v8 with: repo-token: ${{ secrets.GITHUB_TOKEN }}
Registered: Sun Nov 03 09:35:10 UTC 2024 - Last Modified: Tue Apr 11 02:27:05 UTC 2023 - 1.3K bytes - Viewed (0) -
.github/workflows/issue-on-pr-rollback.yml
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Fri Nov 01 08:40:10 UTC 2024 - 1.5K bytes - Viewed (0) -
helm-releases/minio-3.0.0.tgz
displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 02 01:47:43 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-3.1.3.tgz
displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Sep 18 18:09:59 UTC 2021 - 14.4K bytes - Viewed (0) -
.github/actions/people/action.yml
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Jul 09 15:44:40 UTC 2023 - 333 bytes - Viewed (0) -
.github/workflows/issues.yaml
name: Add issue to project runs-on: ubuntu-latest steps: - uses: actions/add-to-project@v0.5.0 with: project-url: https://github.com/orgs/miniohq/projects/2
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Jan 11 07:02:00 UTC 2024 - 338 bytes - Viewed (0) -
.github/actions/notify-translations/action.yml
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Wed Aug 18 13:07:08 UTC 2021 - 346 bytes - Viewed (0) -
helm-releases/minio-4.0.15.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Sep 21 11:07:01 UTC 2022 - 20K bytes - Viewed (0)