Conversation
|
@noahtalerman I'm adding the ability for gitops user to read fleet config, so that it can know if Fleet Premium is used. The config access is not documented, so it should not require doc changes. |
@getvictor makes sense.
By config do you mean info included in the If so, I think we document this in several rows in the permissions table here: There might be more rows I'm missing. |
You're right, I saw looking for |
3cc0ad6 to
145b39b
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #17223 +/- ##
==========================================
+ Coverage 65.50% 65.51% +0.01%
==========================================
Files 1192 1192
Lines 107474 107551 +77
Branches 2569 2569
==========================================
+ Hits 70399 70463 +64
- Misses 31702 31710 +8
- Partials 5373 5378 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…itops yml file, they are now set to default values.
ee5a081 to
73eb7e4
Compare
lucasmrod
left a comment
There was a problem hiding this comment.
Really cool integration tests!
Allowing GitOps role to read org configs. Docs for #17223


For fleetctl gitops, when MDM configs are not explicitly defined in gitops yml file, they are now set to default values.
#17209
Gitops role can now read org config/settings. This is used to determine whether license is Premium.
Doc changes for permission access: #17238
Checklist for submitter
If some of the following don't apply, delete the relevant line.
changes/ororbit/changes/.See Changes files for more information.