6 messages
Discussions related to GitHub Actions
Marat Bakeevover 1 year ago
I think there's an issue with github-action-atmos-affected-stacks - if we start using atmos lookups, then the action fails, because there's no terraform in the action 😄
issues/41
issues/41
rssover 1 year ago(edited)
GitHub Actions: GPU hosted runners are now generally available
GitHub Actions: GPU hosted runners are now generally available
The post GitHub Actions: GPU hosted runners are now generally available appeared first on The GitHub Blog.
GitHub Actions: GPU hosted runners are now generally available
The post GitHub Actions: GPU hosted runners are now generally available appeared first on The GitHub Blog.
Marat Bakeevover 1 year ago
I now suddenly have issues with Atmos Terraform Drift Remediation - it fails on authentication to Kubernetes -
getting credentials: exec: executable aws not found. We changed atmos version from 1.80 to 1.83, though. Is it not supported?Marat Bakeevover 1 year ago
Hey @Igor Rodionov @Erik Osterman (Cloud Posse) - we have more issues with github actions.
Atmos Terraform Drift Detection fails to run if we have lookups enabled in atmos. Again, it requires terraform and nodejs to be installed.
It can be fixed by adding that as steps to atmos-terraform-drift-detection.yaml
Another issue is - even with all of this added, lookups do not work from github actions. The lookup returns nothing.
The lookup looks like this:
This same code works fine locally in geodesic shell!
if I run
I can see the output I'm looking up is there:
and local atmos picks it up
Atmos Terraform Drift Detection fails to run if we have lookups enabled in atmos. Again, it requires terraform and nodejs to be installed.
It can be fixed by adding that as steps to atmos-terraform-drift-detection.yaml
- name: Setup Terraform
uses: hashicorp/setup-terraform@v3
with:
terraform_version: 1.5.7
- name: Setup Node
uses: actions/setup-node@v4
with:
node-version: 16Another issue is - even with all of this added, lookups do not work from github actions. The lookup returns nothing.
Error: reading IAM Instance Profile (<no value>): operation error IAM: GetInstanceProfile, https response error StatusCode: 400, RequestID: d0ab23da-fb09-4a7e-a5b8-3a34b24bdc77, api error ValidationError: 1 validation error detected: Value '<no value>' at 'instanceProfileName' failed to satisfy constraint: Member must satisfy regular expression pattern: [\w+=,.@-]+The lookup looks like this:
instance_profile: '{{ (atmos.Component "iam-role/azure-agent" .stack).outputs.role.instance_profile }}'This same code works fine locally in geodesic shell!
if I run
atmos terraform output iam-role/azure-agent --stack core-apse2-autoI can see the output I'm looking up is there:
Terraform has been successfully initialized!
role = {
"arn" = "arn:aws:iam::BOGUS:role/nsp-core-apse2-auto-azure-agent"
"id" = "AROABOGUS6SEEH3A63"
"instance_profile" = "nsp-core-apse2-auto-azure-agent"
"name" = "nsp-core-apse2-auto-azure-agent"
"policy" = ""
}and local atmos picks it up
atmos terraform plan ec2-instance/agent1 --stack core-apse2-autorssover 1 year ago(edited)
Actions Usage Metrics is generally available
Actions Usage Metrics is generally available
The post Actions Usage Metrics is generally available appeared first on The GitHub Blog.
Actions Usage Metrics is generally available
The post Actions Usage Metrics is generally available appeared first on The GitHub Blog.
rssover 1 year ago(edited)
Run workflows set as workflow_dispatch manually
Run workflows set as workflow_dispatch manually
The post Run workflows set as workflow_dispatch manually appeared first on The GitHub Blog.
Run workflows set as workflow_dispatch manually
The post Run workflows set as workflow_dispatch manually appeared first on The GitHub Blog.