#github-actions (2023-07)

Discussions related to GitHub Actions

2023-07-03

samuel avatar

Good afternoon, currely I have a issue with my pipeline in self-hosted vm aws linux Warning: Unexpected input(s) ‘maven-version’, valid inputs are [‘java-version’, ‘java-version-file’, ‘distribution’, ‘java-package’, ‘architecture’, ‘jdkFile’, ‘check-latest’, ‘server-id’, ‘server-username’, ‘server-password’, ‘settings-path’, ‘overwrite-settings’, ‘gpg-private-key’, ‘gpg-passphrase’, ‘cache’, ‘job-status’, ‘token’, ‘mvn-toolchain-id’, ‘mvn-toolchain-vendor’] https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"2 Run actions/setup-java@v3 https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"3 with: https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"4 distribution: adopt https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"5 java-version: 11 https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"6 java-package: maven https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"7 maven-version: 3.6.3 https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"8 check-latest: false https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"9 server-id: github https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"10 server-username: GITHUB_ACTOR https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"11 server-password: GITHUB_TOKEN https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"12 overwrite-settings: true https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"13 job-status: success https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"14 token: *** https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"15 Installed distributions https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"16 Trying to resolve the latest version from remote https://github.com/Samuelcloud07/java-tomcat-maven-example/actions/runs/5447723699/jobs/9910063118#step<i class="em em-8"17 Error: Could not find satisfied version for SemVer ‘11’.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

:Please use codeblocks. This is hard to read.

2023-07-05

2023-07-12

2023-07-13

actions Archives | The GitHub Blog avatar
actions Archives | The GitHub Blog
09:15:35 PM

GitHub Actions – OIDC integration with AWS no longer requires pinning of intermediate TLS certificates GitHub Actions – OpenId Connect (OIDC) integration with AWS is now optimized to avoid pinning any intermediary certificate thumbprints. While configuring GitHub as an OIDC IdP (ID Provider), AWS now secures communication by trusting GitHub Actions’s trusted root certificate authorities (CAs) instead of using a certificate thumbprint to verify GitHub’s IdP server certificate. This will […]

GitHub Actions - OIDC integration with AWS no longer requires pinning of intermediate TLS certificates | GitHub Changelogattachment image

GitHub Actions – OpenId Connect (OIDC) integration with AWS is now optimized to avoid pinning any intermediary certificate thumbprints. While configuring GitHub as an OIDC IdP (ID Provider), AWS now secures communication by trusting GitHub Actions’s trusted root certificate authorities (CAs) instead of using a certificate thumbprint to verify GitHub’s IdP server certificate. This will […]

1
Pawel Rein avatar
Pawel Rein

this needs support in terraform provider before I can use it, right?

GitHub Actions - OIDC integration with AWS no longer requires pinning of intermediate TLS certificates | GitHub Changelogattachment image

GitHub Actions – OpenId Connect (OIDC) integration with AWS is now optimized to avoid pinning any intermediary certificate thumbprints. While configuring GitHub as an OIDC IdP (ID Provider), AWS now secures communication by trusting GitHub Actions’s trusted root certificate authorities (CAs) instead of using a certificate thumbprint to verify GitHub’s IdP server certificate. This will […]

Gabriela Campana (Cloud Posse) avatar
Gabriela Campana (Cloud Posse)

@Jeremy G (Cloud Posse) @Ben Smith (Cloud Posse) @Andriy Knysh (Cloud Posse)

Jeremy G (Cloud Posse) avatar
Jeremy G (Cloud Posse)

@Pawel Rein No, you can use the aws_iam_openid_connect_provider Terraform resource. What this means is that you no longer need to provide the thumbprint_list.

1

2023-07-16

2023-07-17

actions Archives | The GitHub Blog avatar
actions Archives | The GitHub Blog
09:55:35 AM

GitHub Actions: Removal of Node12 from the Actions runner GitHub Actions: Removal of Node12 from the Actions runner

GitHub Actions: Removal of Node12 from the Actions runner | GitHub Changelogattachment image

GitHub Actions: Removal of Node12 from the Actions runner

2023-07-18

2023-07-19

2023-07-24

samuel avatar

Hi, good mooning i have question to github action, if anywhere could me help, the I want to protect .yml file with codeowner

actions Archives - The GitHub Blog avatar
actions Archives - The GitHub Blog
06:55:34 PM

GitHub Actions: Update on save-state and set-output commands GitHub Actions: Update on save-state and set-output commands

GitHub Actions: Update on save-state and set-output commands

GitHub Actions: Update on save-state and set-output commands

    keyboard_arrow_up