We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i've been delaying thing this too long.. werner will be happy...
@igorpecovnik did you have a method already for managing ssh keys on get gethub?
my old plan was crypt and shenangins
jobs: test_secrets_management: name: do secrety things runs-on: [self-hosted] steps: - uses: actions/checkout@v2 with: fetch-depth: 0 path: ci-test clean: true - name: Do some tests shell: bash {0} run: | eval $(ssh-agent) cd ci-test TEST_HOST=testhost.example.com TEST_USER=rsync_user SSH_KEYFILE="secrets/test_ssh_key.cpt" ssh-add <(ccat $PWD/${SSH_KEYFILE} -K ${{secrets.keyword}}) echo "Unique Data $(uuidgen)" > testfile rsync -auv testfile ${TEST_USER}@${TEST_HOST}:
The text was updated successfully, but these errors were encountered:
\o/
Method of grabbing has been changed slightly due to latest pushes. Now it is to grab the latest release instead of latest artifact.
Sorry, something went wrong.
did you have a method already for managing ssh keys on get gethub?
Yes I do. Build artefacts are uploading to NAS in the process. You would want to upload documentation (pdf) somewhere?
lanefu
No branches or pull requests
i've been delaying thing this too long.. werner will be happy...
@igorpecovnik did you have a method already for managing ssh keys on get gethub?
my old plan was crypt and shenangins
The text was updated successfully, but these errors were encountered: