pubfleet 0.2.1__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- pubfleet/__init__.py +23 -0
- pubfleet/board/__init__.py +113 -0
- pubfleet/board/collect.py +255 -0
- pubfleet/board/connectors/__init__.py +7 -0
- pubfleet/board/connectors/actions.py +65 -0
- pubfleet/board/connectors/base.py +193 -0
- pubfleet/board/connectors/github.py +144 -0
- pubfleet/board/connectors/live.py +17 -0
- pubfleet/board/connectors/repos.py +23 -0
- pubfleet/board/connectors/scorecard.py +24 -0
- pubfleet/board/connectors/sonarcloud.py +52 -0
- pubfleet/board/page.py +125 -0
- pubfleet/board/rules.json +37 -0
- pubfleet/board/rules.py +337 -0
- pubfleet/board_publish.py +134 -0
- pubfleet/cli.py +112 -0
- pubfleet/discover.py +110 -0
- pubfleet/freshness.py +88 -0
- pubfleet/state.py +198 -0
- pubfleet/variables.py +200 -0
- pubfleet-0.2.1.dist-info/METADATA +314 -0
- pubfleet-0.2.1.dist-info/RECORD +26 -0
- pubfleet-0.2.1.dist-info/WHEEL +5 -0
- pubfleet-0.2.1.dist-info/entry_points.txt +2 -0
- pubfleet-0.2.1.dist-info/licenses/LICENSE +202 -0
- pubfleet-0.2.1.dist-info/top_level.txt +1 -0
|
@@ -0,0 +1,314 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: pubfleet
|
|
3
|
+
Version: 0.2.1
|
|
4
|
+
Summary: What a control plane runs across many repositories: the board, the state file, their GitHub variables, freshness, and the nightly's loop.
|
|
5
|
+
Author-email: David Schryer <schryer@gmail.com>
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Repository, https://github.com/Sustenaut/pubfleet
|
|
8
|
+
Requires-Python: >=3.11
|
|
9
|
+
Description-Content-Type: text/markdown
|
|
10
|
+
License-File: LICENSE
|
|
11
|
+
Requires-Dist: pubrules>=0.43.0
|
|
12
|
+
Dynamic: license-file
|
|
13
|
+
|
|
14
|
+
# pubfleet
|
|
15
|
+
|
|
16
|
+
What a control plane runs across many repositories at once: it grades them
|
|
17
|
+
(`pubfleet board`), publishes the grades (`pubfleet board-publish`), checks
|
|
18
|
+
and reads the owner's state file (`pubfleet state`), keeps their GitHub
|
|
19
|
+
variables (`pubfleet variables`), reports which pubrules each pins
|
|
20
|
+
(`pubfleet freshness`), and opens their nightly pull requests (the reusable
|
|
21
|
+
`nightly.yml`). Everything that runs inside one repository about itself
|
|
22
|
+
stays in [pubrules](https://github.com/Sustenaut/pubrules): `sync`, `protect`,
|
|
23
|
+
`bump`, and `pubrules nightly`, which makes the nightly's commits in each
|
|
24
|
+
checkout.
|
|
25
|
+
|
|
26
|
+
pubfleet board --out DIR --repos FILE [--rules FILE] [--replay FILE] [--record FILE]
|
|
27
|
+
pubfleet board-publish --url URL --tenant TENANT [--file FILE]
|
|
28
|
+
pubfleet state --check | --repos-for board|govern|deploy | --discover [--body PATH] [FILE]
|
|
29
|
+
pubfleet variables --check|--apply [--state FILE] [--repos FILE | REPO...]
|
|
30
|
+
pubfleet freshness [--json] (DIR... | --repos FILE [DIR])
|
|
31
|
+
pubfleet --version
|
|
32
|
+
|
|
33
|
+
## Installing
|
|
34
|
+
|
|
35
|
+
A control plane lists pubfleet's wheel beside pubrules' in its
|
|
36
|
+
`tests/requirements.txt`, and installs the hash-locked set:
|
|
37
|
+
|
|
38
|
+
pubfleet @ https://github.com/Sustenaut/pubfleet/releases/download/vX.Y.Z/pubfleet-X.Y.Z-py3-none-any.whl
|
|
39
|
+
|
|
40
|
+
`pubrules lock` pins both by sha256. pubfleet declares the oldest pubrules it
|
|
41
|
+
works with (`pubrules>=` in pyproject.toml); its own `tests/requirements.lock`
|
|
42
|
+
pins the pubrules it is tested with.
|
|
43
|
+
|
|
44
|
+
## What pubfleet takes from pubrules
|
|
45
|
+
|
|
46
|
+
pubfleet uses pubrules as a library, and copies none of it: the board grades a
|
|
47
|
+
repository's protection against pubrules' own ruleset, and a copy would drift
|
|
48
|
+
from it. pubrules never imports pubfleet and names nothing of it. pubfleet
|
|
49
|
+
offers no `sustenaut.sync` or `sustenaut.bump` hook, so pubrules never loads it
|
|
50
|
+
into its own process.
|
|
51
|
+
|
|
52
|
+
These are all the names it takes, which `tests/features/pubrules.feature`
|
|
53
|
+
holds it to, and which the installed pubrules must have:
|
|
54
|
+
|
|
55
|
+
- the standard's protection: `pubrules.protect.entry`, `pubrules.protect.ruleset`,
|
|
56
|
+
`pubrules.protect.tag_ruleset`, `pubrules.protect.differences`,
|
|
57
|
+
`pubrules.protect.on_default_branch`, `pubrules.protect.on_release_tags`,
|
|
58
|
+
`pubrules.protect.remote`;
|
|
59
|
+
- the GitHub calls: `pubrules.protect.gh`, `pubrules.protect.gh_set`,
|
|
60
|
+
`pubrules.protect.Api`, `pubrules.protect.ApiError`,
|
|
61
|
+
`pubrules.protect.remote_config`;
|
|
62
|
+
- the repos file: `pubrules.repos.read`, `pubrules.repos.entries`;
|
|
63
|
+
- the variables block's shape: `pubrules.variables.BLOCK`,
|
|
64
|
+
`pubrules.variables.block_problems`, `pubrules.variables.name_problem`;
|
|
65
|
+
- the pins the board and freshness read: `pubrules.refs.ANY_OWNER`,
|
|
66
|
+
`pubrules.refs.AT`, `pubrules.refs.VERSION`, `pubrules.refs.RELEASE_PIN`,
|
|
67
|
+
`pubrules.freshness.PIN`, `pubrules.freshness.pinned`,
|
|
68
|
+
`pubrules.nightly.PUBREL_VERSION`;
|
|
69
|
+
- the standard freshness judges by: `pubrules.conform.run`, `pubrules.__version__`;
|
|
70
|
+
- `pubrules.paths.confined`, for the files a command is given.
|
|
71
|
+
|
|
72
|
+
A name pubfleet wants beyond these is a sign the code belongs on one side or
|
|
73
|
+
the other, not a reason to widen the list.
|
|
74
|
+
|
|
75
|
+
## The release board
|
|
76
|
+
|
|
77
|
+
pubfleet board --out DIR --repos FILE [--rules FILE]
|
|
78
|
+
|
|
79
|
+
grades every repository the repos file (or the two lists) names, public and private, A to E for
|
|
80
|
+
quality, security and delivery, and writes `DIR/board.json` and a static
|
|
81
|
+
`DIR/index.html`: no scripts, rows worst first, each grade a dot in
|
|
82
|
+
SonarQube's colours whose breakdown opens on hover or keyboard focus. It
|
|
83
|
+
only reads, and keeps nothing between builds. `GITHUB_TOKEN` (or
|
|
84
|
+
`GH_TOKEN`) is the token it reads GitHub with; `SONAR_TOKEN`, when set,
|
|
85
|
+
reads private SonarQube Cloud projects.
|
|
86
|
+
|
|
87
|
+
The rules are [`src/pubfleet/board/rules.json`](src/pubfleet/board/rules.json),
|
|
88
|
+
applied by `rules.py`; `--rules FILE` reads others, such as a client's.
|
|
89
|
+
Each grade is a starting letter less one letter per notch, never below E,
|
|
90
|
+
with every notch listed; the overall grade is the worst of the three.
|
|
91
|
+
|
|
92
|
+
- **Quality** starts at SonarQube Cloud's worse rating of reliability and
|
|
93
|
+
maintainability, **Security** at its security rating. With no analysis,
|
|
94
|
+
each starts at A and takes a notch. Then each other tool with findings
|
|
95
|
+
takes one: a CI job on main's last run that failed (format and lint,
|
|
96
|
+
tests, functional and browser tests, MSRV, fuzzing, cross builds and
|
|
97
|
+
toolchains for Quality; the dependency audit, OSV-Scanner and dependency
|
|
98
|
+
review for Security), open Dependabot, code scanning or secret scanning
|
|
99
|
+
alerts, and an OpenSSF Scorecard under 7 for a public repository.
|
|
100
|
+
Alerts that are switched off are listed with no notch.
|
|
101
|
+
- **Delivery** starts at A and takes a notch for each of: a pinned pubrules
|
|
102
|
+
or pubrel behind its latest release; not integrated with pubrules
|
|
103
|
+
(services) or with pubrules and pubrel (packages, which have a
|
|
104
|
+
release.json); for a service, no observability (its health URL does not
|
|
105
|
+
answer) and no continuous live testing (its live-test workflow not green
|
|
106
|
+
in the last 24 hours); no release (a package's tag, a service's
|
|
107
|
+
production deploy) in two months; any open issue (pull requests aside);
|
|
108
|
+
no nightly (not governed, and no `nightly.yml` run in two days);
|
|
109
|
+
protection that differs from what `pubrules protect --check` wants, or no
|
|
110
|
+
ruleset at all on a private repository GitHub's plan gives none; and a
|
|
111
|
+
red last CI run on main. A fact the board could not read takes its
|
|
112
|
+
notch: a board that cannot see does not grade green.
|
|
113
|
+
|
|
114
|
+
A service declares what its observability and live testing are in its
|
|
115
|
+
`pubrules.json`:
|
|
116
|
+
|
|
117
|
+
```json
|
|
118
|
+
"live": { "health": "https://example.eu/health", "test": "live.yml", "deploy": "deploy.yml" }
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
`health` is the URL that must answer, `test` the scheduled workflow that
|
|
122
|
+
tests the live site, and `deploy` the workflow whose successful runs are
|
|
123
|
+
its production deploys (`deploy.yml` by default).
|
|
124
|
+
|
|
125
|
+
Each source has one connector in `src/pubfleet/board/connectors/`, and
|
|
126
|
+
nothing else reads it: `lists` (the two lists), `github` (the REST API:
|
|
127
|
+
visibility, pubrules.json, release.json, the lock and workflow pins,
|
|
128
|
+
rulesets, releases, issues and alerts), `actions` (runs and jobs on main,
|
|
129
|
+
nightly, live-test and deploy runs), `sonarcloud` (project `OWNER_REPO`),
|
|
130
|
+
`scorecard` (public repositories) and `live` (the health URLs). Each
|
|
131
|
+
query is a named method, and each call is recorded with its connector,
|
|
132
|
+
method, endpoint and time: board.json lists every call, and links every
|
|
133
|
+
fact and every notch to the calls it rests on, which the breakdown names.
|
|
134
|
+
`--record FILE` keeps every response, and `--replay FILE` builds from
|
|
135
|
+
such a file instead of the network.
|
|
136
|
+
|
|
137
|
+
[`board.yml`](.github/workflows/board.yml) is the reusable workflow: it
|
|
138
|
+
checks out the caller, installs what its `tests/requirements.lock` pins
|
|
139
|
+
(wheels only, by hash: the caller's own pubfleet and pubrules),
|
|
140
|
+
runs `pubfleet board` with the caller's read-only `token` and its `repos` input
|
|
141
|
+
(the repos file itself, as JSON), and uploads board.json and index.html as the `board` artifact, kept 90 days. It
|
|
142
|
+
deploys nothing.
|
|
143
|
+
|
|
144
|
+
## The repos file
|
|
145
|
+
|
|
146
|
+
Which repositories pubfleet and `pubrules protect` act on comes from outside them, in one file, whose format is pubrules' (`pubrules.repos`):
|
|
147
|
+
|
|
148
|
+
```json
|
|
149
|
+
{ "repositories": [
|
|
150
|
+
{ "repo": "example-org/some-tool", "protect": true, "govern": true, "project": "tools" },
|
|
151
|
+
{ "repo": "example-org/some-site", "protect": true, "govern": false }
|
|
152
|
+
] }
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
`protect` says it should carry pubrules' rulesets, and `govern` that a nightly
|
|
156
|
+
keeps it current; each is false when left out. `project`, optional, labels it on
|
|
157
|
+
the board. How a repository is protected stays in its own `pubrules.json`'s
|
|
158
|
+
protect block. `pubfleet board --repos FILE`, `pubrules protect [--check] --repos
|
|
159
|
+
FILE` and `pubfleet freshness --repos FILE [DIR]` read it (freshness reports the
|
|
160
|
+
governed ones, each checked out at `DIR/<name>`), and the reusable `board.yml`
|
|
161
|
+
and `nightly.yml` take its contents as a `repos` input.
|
|
162
|
+
|
|
163
|
+
pubfleet board-publish --url URL --tenant TENANT [--file FILE]
|
|
164
|
+
|
|
165
|
+
keeps a board (by default `site/board.json`) in a storage tenant, for a job whose
|
|
166
|
+
logs must stay quiet: it prints no repository's name. It uploads only if a fact or a grade
|
|
167
|
+
differs from what the tenant's `board` head names, then moves the head, conditionally, so
|
|
168
|
+
a move by someone else fails the run. It signs in with the GitHub Actions job's OpenID
|
|
169
|
+
Connect token, for the audience that is the URL's host name, so the job needs `id-token:
|
|
170
|
+
write` and no secret, and the tenant must let that job write.
|
|
171
|
+
|
|
172
|
+
### State files
|
|
173
|
+
|
|
174
|
+
pubrules state --check [FILE]
|
|
175
|
+
pubrules state --repos-for board|govern|deploy [FILE]
|
|
176
|
+
pubrules state --discover [--body PATH] [FILE]
|
|
177
|
+
|
|
178
|
+
`--check` checks a state repository's `state.json` (by default in the working directory),
|
|
179
|
+
which a control plane keeps for one GitHub owner, and `--repos-for` prints the repos file
|
|
180
|
+
for one of its roles:
|
|
181
|
+
|
|
182
|
+
```json
|
|
183
|
+
{ "owner": "example-org",
|
|
184
|
+
"repos": {
|
|
185
|
+
"some-tool": { "project": "tools", "board": true, "protect": true, "govern": true },
|
|
186
|
+
"some-service": { "board": true, "protect": true, "govern": true, "deploy": true }
|
|
187
|
+
} }
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
`--discover` adds the owner's repositories the file does not list yet, archived ones
|
|
191
|
+
and forks left out: each on the board, protected when its own `pubrules.json` has a protect
|
|
192
|
+
block (which `--check` requires of protect), and not governed, with no project and no
|
|
193
|
+
deploy. It rewrites the file as state files are kept (two-space JSON, repositories in name
|
|
194
|
+
order), prints how many it added, and with `--body` writes a pull request's description:
|
|
195
|
+
each one added, its visibility and why protect is on or off, and the listed repositories
|
|
196
|
+
that are archived or gone, which it never removes. A state repository's nightly runs it
|
|
197
|
+
and opens that pull request for an operator to merge.
|
|
198
|
+
|
|
199
|
+
`deploy`, optional and false when left out, marks a repository the convergence
|
|
200
|
+
engine walks: the state says whether, and the repository's `pubrules.json` deploy
|
|
201
|
+
block says how.
|
|
202
|
+
|
|
203
|
+
It checks the file's shape, then through `gh` that each repository exists under
|
|
204
|
+
the owner, that each with `protect` has a sound protect block, and that each with
|
|
205
|
+
`deploy` has a deploy block. `gh` needs a
|
|
206
|
+
token that can read every repository named, which a workflow's own
|
|
207
|
+
`GITHUB_TOKEN` can't. It builds nothing, so it suits being a state repository's
|
|
208
|
+
one required check.
|
|
209
|
+
|
|
210
|
+
### Variables from a state file
|
|
211
|
+
|
|
212
|
+
pubfleet variables --check|--apply [--state FILE] [--repos FILE | REPO...]
|
|
213
|
+
|
|
214
|
+
A repository's GitHub variables that aren't secret can live in the state file, so a
|
|
215
|
+
change to one is a reviewed pull request with a history. The repository's own
|
|
216
|
+
`pubrules.json` declares only their names (pubrules' `sync --check` checks that block's shape), and may name the workflow that reads them,
|
|
217
|
+
to run once one changes:
|
|
218
|
+
|
|
219
|
+
```json
|
|
220
|
+
"variables": { "names": ["SOME_SETTING", "SOME_MAP"], "deploy": "deploy.yml" }
|
|
221
|
+
```
|
|
222
|
+
|
|
223
|
+
The state file gives their values, under the repository:
|
|
224
|
+
|
|
225
|
+
```json
|
|
226
|
+
"some-tool": { "board": true, "protect": true, "govern": false,
|
|
227
|
+
"variables": { "SOME_SETTING": "a string", "SOME_MAP": { "some-key": "some-value" } } }
|
|
228
|
+
```
|
|
229
|
+
|
|
230
|
+
A string goes to GitHub as it is; anything else is JSON, kept structured in the state
|
|
231
|
+
so that a diff shows the entry that changed, and sent compact, in the file's order. A
|
|
232
|
+
JSON value matches what GitHub holds if that parses to the same thing. `state --check`
|
|
233
|
+
refuses a name the repository doesn't declare, and an empty value.
|
|
234
|
+
|
|
235
|
+
`--check` changes nothing: it prints how each repository's variables differ, a diff of
|
|
236
|
+
the changed entries for JSON, and fails when one does, which suits a pull request's
|
|
237
|
+
plan and a nightly drift report. `--apply` sets those that differ, each value on
|
|
238
|
+
`gh`'s standard input, and then runs the repository's `deploy` workflow on its default
|
|
239
|
+
branch, once. Both act on every repository the state gives variables, those named, or
|
|
240
|
+
those a repos file lists, and neither touches a variable the state leaves out nor
|
|
241
|
+
removes one. The token needs to read the repositories' contents and variables, and for
|
|
242
|
+
`--apply` to write variables and run workflows (the Variables and Actions permissions,
|
|
243
|
+
for a GitHub App).
|
|
244
|
+
|
|
245
|
+
## Freshness
|
|
246
|
+
|
|
247
|
+
pubfleet freshness [--json] DIR...
|
|
248
|
+
pubfleet freshness [--json] --repos FILE [DIR]
|
|
249
|
+
|
|
250
|
+
reports, for each checked-out repository, the pubrules its lock pins, whether it
|
|
251
|
+
is the installed one, whether it conforms to that pubrules' standard, and its
|
|
252
|
+
open exceptions: one Markdown table, also appended to the GitHub step summary
|
|
253
|
+
when there is one. With `--repos` it reports the repositories the file marks
|
|
254
|
+
to govern, each checked out at `DIR/<name>`, and says which are not checked
|
|
255
|
+
out. It reads; it changes nothing. Moving a repository to a pubrules is `pubrules
|
|
256
|
+
bump`'s, and the nightly's.
|
|
257
|
+
|
|
258
|
+
## The nightly
|
|
259
|
+
|
|
260
|
+
[`nightly.yml`](.github/workflows/nightly.yml) runs over the repositories its
|
|
261
|
+
`repos` input marks to govern, called from a control plane's own schedule. It
|
|
262
|
+
has no schedule of its own. Run by hand, it takes the same `repos` input. A
|
|
263
|
+
caller passes the secrets `app-id`, `app-key`, `notify-token` and
|
|
264
|
+
`notify-user`, and the `pubfleet` input names the repository whose latest
|
|
265
|
+
release supplies the wheel and the scripts in `.github/nightly/`.
|
|
266
|
+
|
|
267
|
+
Its report job checks each governed repository out and runs `pubfleet
|
|
268
|
+
freshness` into the summary. Its update job then keeps one pull request per
|
|
269
|
+
repository, on its `pubrules-nightly` branch (`.github/nightly/update.sh`): it
|
|
270
|
+
runs `pubrules nightly` in the checkout, which commits the moved pub* pins, the
|
|
271
|
+
audited crate updates, the npm updates and the re-locked Python requirements,
|
|
272
|
+
and writes the body. What those commits hold, and the `update` and `security`
|
|
273
|
+
settings a repository's `pubrules.json` gives them, are pubrules' (its README,
|
|
274
|
+
"The nightly"). An open pull request is updated, never a second one opened,
|
|
275
|
+
and left alone when the night brings nothing new. When its CI fails, the pins
|
|
276
|
+
are tested alone: if they pass, the dependency commits are dropped. Nothing
|
|
277
|
+
merges it: the Sustenaut bot sends a Slack DM when it is green or fails.
|
|
278
|
+
|
|
279
|
+
**Which pubrules.** The nightly installs the pubrules that the latest pubfleet
|
|
280
|
+
release's `tests/requirements.lock` pins, by hash
|
|
281
|
+
(`.github/nightly/install.sh`), and `pubrules nightly` moves each repository to
|
|
282
|
+
the pubrules it runs as. So a pubrules release reaches governed repositories
|
|
283
|
+
once pubfleet's own nightly has moved its lock to it and a pubfleet release
|
|
284
|
+
carries it: a night later than pubrules' release, and only once pubfleet's
|
|
285
|
+
suite has passed with it. The `pubrules` input, a pubrules release tag such as
|
|
286
|
+
`v0.33.1`, installs that pubrules instead, with a warning, for a fix that must
|
|
287
|
+
go out at once.
|
|
288
|
+
|
|
289
|
+
It pushes and opens the pull requests as the **Sustenaut nightly** GitHub
|
|
290
|
+
App, which is installed on each owner whose repositories it governs. For each
|
|
291
|
+
repository it mints a token for that repository alone, with contents,
|
|
292
|
+
pull-requests and workflows write and actions read, which expires within the
|
|
293
|
+
hour (`actions/create-github-app-token`). The repository variable
|
|
294
|
+
`NIGHTLY_APP_ID` and secret `NIGHTLY_APP_KEY` (the app's private key) set it
|
|
295
|
+
up when run by hand, and `app-id` and `app-key` when called. Without them it
|
|
296
|
+
falls back, with a warning, to a `PUBRULES_BUMP_TOKEN` secret, and with neither
|
|
297
|
+
it only reports.
|
|
298
|
+
|
|
299
|
+
`.github/nightly/pubrel-version.sh` chooses the pubrel it installs, and pins
|
|
300
|
+
each repository's release workflow to: its latest GitHub release if crates.io
|
|
301
|
+
has that version, else the newest crates.io has, with a warning.
|
|
302
|
+
|
|
303
|
+
## Developing
|
|
304
|
+
|
|
305
|
+
make venv # the hash-locked environment, this checkout installed editable
|
|
306
|
+
make check # what CI runs: ./pubrules sync --check and the suite
|
|
307
|
+
|
|
308
|
+
Releases are pubrel's: a code change records what it changes (`pubrel add`),
|
|
309
|
+
and `pubrel prepare` cuts the release pull request. `wheel.yml` attaches the
|
|
310
|
+
wheel once main has tagged it.
|
|
311
|
+
|
|
312
|
+
## Licence
|
|
313
|
+
|
|
314
|
+
Apache-2.0.
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
pubfleet/__init__.py,sha256=4hoEAxEnl2Rcg4jM1ICblG3UQarSoVTA9jA_vpvVBi0,812
|
|
2
|
+
pubfleet/board_publish.py,sha256=1X0iuNGKxKAP59BpmVdbBzLxAZSLA1nMft6txxl4BrY,5859
|
|
3
|
+
pubfleet/cli.py,sha256=aOeAfu5Kkr_Vzo1U5oWFavNlxr397dsQIULeFCDGG9A,6788
|
|
4
|
+
pubfleet/discover.py,sha256=3fF5CGJStUHO2D406w3gGslO26RUKJbwldUjobqWR6o,4872
|
|
5
|
+
pubfleet/freshness.py,sha256=Xqr5PMHDVkwKFoCeUA-IwFeeno-Cxar1RY3cu6nA_X8,3979
|
|
6
|
+
pubfleet/state.py,sha256=YcsJZmFuf0Ld6VqYGsErb-h3Hh6nHbiKbB0b6r0V_sA,9223
|
|
7
|
+
pubfleet/variables.py,sha256=CIxxg6dmVAoM3eM0fWMiqo83_cJ3NxxqRB04x1fBb70,8443
|
|
8
|
+
pubfleet/board/__init__.py,sha256=TUE3qsVrDK8v0k6GHj2rzKyWVjMDCvlx1DZsDhMOQ44,5077
|
|
9
|
+
pubfleet/board/collect.py,sha256=YnPMduFvvyjAtEqtUH9lhJosbD1Lp3o5GQuzL0r46qo,12411
|
|
10
|
+
pubfleet/board/page.py,sha256=TCgcG79UJ3WAs_aHz3lDjLXdUiaw7LXuFVtnH_8CkoI,6948
|
|
11
|
+
pubfleet/board/rules.json,sha256=XLQ9E64oVPujAPCiuSXRkL_E8Lqw6XkNSjMdOrOTt4Y,3382
|
|
12
|
+
pubfleet/board/rules.py,sha256=x5uWxdsl9cQ-eAvwkRSX2140YK08a4FNR6WQvtM3WLc,14491
|
|
13
|
+
pubfleet/board/connectors/__init__.py,sha256=rdul0x6mdh9KpEbDceSt8LGOkjNApAwJvvxOubHL5Qc,297
|
|
14
|
+
pubfleet/board/connectors/actions.py,sha256=tYbVBaRsPzpuKVY90Wv8bLpo0TCMT18jCLxwyjEEfmg,3150
|
|
15
|
+
pubfleet/board/connectors/base.py,sha256=Pdx_l6EFYTl0Buj7tHW_xSmhCHn-Z6y7ykwexbFD7Tg,7136
|
|
16
|
+
pubfleet/board/connectors/github.py,sha256=gbsKIVAp1KDDuK-8A2kqG7RZ0o1ENkybd9rDIVfJuBo,6808
|
|
17
|
+
pubfleet/board/connectors/live.py,sha256=XqluPoG-E6Idrdcriii5oqlHjcuZxKMaeNxVK3PINtI,585
|
|
18
|
+
pubfleet/board/connectors/repos.py,sha256=uG_ajxytV8h-ZBoVUTZTzJ2uK1kOI546KsSjMPVbulo,714
|
|
19
|
+
pubfleet/board/connectors/scorecard.py,sha256=JiY0asv-UAgavm5VQZUHD5ZDYOcVUOs4K2jq-mH5Ntg,1030
|
|
20
|
+
pubfleet/board/connectors/sonarcloud.py,sha256=ym7C3xZMHOGEWJzqCwo3QP_jBNwcLIH7xc3P1Fa8AVs,2153
|
|
21
|
+
pubfleet-0.2.1.dist-info/licenses/LICENSE,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
|
|
22
|
+
pubfleet-0.2.1.dist-info/METADATA,sha256=wN_IPILzqXETDrawT9RTsuPsLMLNMRdFNjrk9IUAjv0,16311
|
|
23
|
+
pubfleet-0.2.1.dist-info/WHEEL,sha256=mOdXR9C3wMVov7cSY8PY-XCzo3SmmWCHvGQr5csJoao,91
|
|
24
|
+
pubfleet-0.2.1.dist-info/entry_points.txt,sha256=P2JLPy68tLCmUE9DJocUzCiS6MPtHAqwU1eg562-AXM,47
|
|
25
|
+
pubfleet-0.2.1.dist-info/top_level.txt,sha256=mcoAlzKqYPtKXKJEm0_1WgQjoSUepOp4-eWU4FqXNpQ,9
|
|
26
|
+
pubfleet-0.2.1.dist-info/RECORD,,
|
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
pubfleet
|