Skip to content
New issue

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

Run gitops.sh with a team gitops role #24002

Open
dherder opened this issue Nov 21, 2024 · 1 comment
Open

Run gitops.sh with a team gitops role #24002

dherder opened this issue Nov 21, 2024 · 1 comment
Labels
:product Product Design department (shows up on 🦢 Drafting board) prospect-hubble

Comments

@dherder
Copy link
Contributor

dherder commented Nov 21, 2024


@dherder dherder added :product Product Design department (shows up on 🦢 Drafting board) prospect-hubble labels Nov 21, 2024
@noahtalerman
Copy link
Member

Problem

From prospect-hubble:
"we wanted to setup GitOps where the action was only actioning team resources / config."

Right now, when running gitops.sh with a team specific gitops user, the following error is encountered:
fleetctl gitops -f ./default.yml -f ./teams/endpoint-qa.yml -f ./teams/endpoint.yml -f ./teams/no-team.yml --dry-run
Error: GET /api/latest/fleet/config received status 403 forbidden: forbidden
Error: Process completed with exit code 1.

What have you tried?

Defining a global gitops role is the workaround.

Potential solutions

From prospect-hubble:
it (gitops.sh) should determine which one (.yml) is global config by virtue of it being the only yml file with an org_settings top level key. order of -f xxxxx.yml shouldn't really matter. Additionally, if no file with org_settings top-level key is provided, skip configuring global scope and only configure teams. That logic makes more sense to me!

In order to support this, fleetctl would need changes in addition to the gitops actions (github and gitlab) required to not set the global config, only the team config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:product Product Design department (shows up on 🦢 Drafting board) prospect-hubble
Development

No branches or pull requests

2 participants