Hey folks, these 2 are ready :raised_hands: : - <h...
# atmos-dev
j
Hey folks, these 2 are ready šŸ™Œ : • github.com/cloudposse/atmos/pull/3048 • github.com/cloudposse/atmos/pull/3047
merged 1
e
Can you share a screenshot example of the PR generated?
want to review aesthetically
j
Certainly.
CleanShot 2026-09-09 at 07.40.33@2x.png
CleanShot 2026-09-09 at 07.40.49@2x.png
This was done with the following vendor config:
Copy code
apiVersion: atmos/v1
kind: AtmosVendorConfig
metadata:
  name: ado-test-project
spec:
  sources:
    - component: "null-label"
      source: "github.com/cloudposse/terraform-null-label.git//?ref={{.Version}}"
      version: "0.24.0"
      targets:
        - "components/terraform/null-label"
      included_paths:
        - "**/*.tf"
        - "**/*.md"
and:
Copy code
vendor:
  ci:
    pull_request:
      provider: azuredevops
      organization: *snip*
      project: *snip*
      repository: temp-atmos-vendor
      base_branch: main
      branch_prefix: atmos/component-updater
      title: "chore(components): update {{ .scope.name }}"
      labels: [component-update]
      reviewers: ["Jorrit Elfferich", "jelfferich@schubergphilis.com"] # either of these 2 work.
The PR itself is suffering a bit from: github.com/cloudposse/atmos/issues/3076, meaning the PR itself only proposes a version bump in the vendor config I might take a stab at that via a separate fix PR though.
Small bump to both of these šŸ˜‡. Anything you folks are waiting on from my side? @Andriy Knysh (Cloud Posse) @Erik Osterman (Cloud Posse)?
e
Was just waiting for the CORS issue to get resolved
šŸ‘ 1
Will take a look today
j
Cool, appreciate it ! LMK if it needs polish.
šŸ‘ 1
I see they got merged šŸ™Œ
I was stacking a change on one of them, so another change is inbound šŸ¤“ šŸ”œ
šŸ™ 1