c2cciutils 1.7.0.dev52__tar.gz → 1.7.0.dev56__tar.gz

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.
Files changed (41) hide show
  1. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/PKG-INFO +1 -1
  2. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/applications_definition.py +2 -2
  3. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/configuration.py +20 -20
  4. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/schema-applications.json +2 -2
  5. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/schema.json +11 -11
  6. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/pyproject.toml +4 -2
  7. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/setup.py +1 -1
  8. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/LICENSE +0 -0
  9. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/README.md +0 -0
  10. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/__init__.py +0 -0
  11. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/applications-versions.yaml +0 -0
  12. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/applications.yaml +0 -0
  13. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/audit.py +0 -0
  14. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/branches.graphql +0 -0
  15. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/commits.graphql +0 -0
  16. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/default_branch.graphql +0 -0
  17. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/env.py +0 -0
  18. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/lib/docker.py +0 -0
  19. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/package-lock.json +0 -0
  20. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/package.json +0 -0
  21. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/pr_checks.py +0 -0
  22. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/publish.py +0 -0
  23. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/__init__.py +0 -0
  24. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/audit.py +0 -0
  25. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/clean.py +0 -0
  26. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/docker_logs.py +0 -0
  27. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/docker_versions_gen.py +0 -0
  28. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/download_applications.py +0 -0
  29. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/env.py +0 -0
  30. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/k8s/__init__.py +0 -0
  31. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/k8s/db.py +0 -0
  32. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/k8s/install.py +0 -0
  33. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/k8s/logs.py +0 -0
  34. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/k8s/wait.py +0 -0
  35. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/main.py +0 -0
  36. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/pin_pipenv.py +0 -0
  37. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/pr_checks.py +0 -0
  38. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/publish.py +0 -0
  39. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/trigger_image_update.py +0 -0
  40. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/scripts/version.py +0 -0
  41. {c2cciutils-1.7.0.dev52 → c2cciutils-1.7.0.dev56}/c2cciutils/security.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: c2cciutils
3
- Version: 1.7.0.dev52
3
+ Version: 1.7.0.dev56
4
4
  Summary: Common utilities for Camptocamp CI
5
5
  Home-page: https://github.com/camptocamp/c2cciutils
6
6
  License: FreeBSD
@@ -21,11 +21,11 @@ ApplicationConfiguration = TypedDict(
21
21
  "type": "TheTypeOfFile",
22
22
  # The filename to get.
23
23
  #
24
- # The filename to get in the GitHub release
24
+ # The name of the file to get in the GitHub release
25
25
  "get-file-name": str,
26
26
  # The created tile name.
27
27
  #
28
- # The name of the final tile name we will create
28
+ # The name of the final tile we will create
29
29
  "to-file-name": str,
30
30
  # The tile name to get in the tar file.
31
31
  "tar-file-name": str,
@@ -10,31 +10,31 @@ AUDIT_DEFAULT = {"snyk": True, "outdated_versions": True}
10
10
 
11
11
 
12
12
  AUDIT_SNYK_FILES_NO_INSTALL_DEFAULT: list[Any] = []
13
- """ Default value of the field path 'Audit snyk config files_no_install' """
13
+ """ Default value of the field path 'Audit Snyk config files_no_install' """
14
14
 
15
15
 
16
16
  AUDIT_SNYK_FIX_ARGUMENTS_DEFAULT = ["--all-projects"]
17
- """ Default value of the field path 'Audit snyk config fix_arguments' """
17
+ """ Default value of the field path 'Audit Snyk config fix_arguments' """
18
18
 
19
19
 
20
20
  AUDIT_SNYK_FIX_PULL_REQUEST_ARGUMENTS_DEFAULT = ["--fill", "--label=dependencies"]
21
- """ Default value of the field path 'Audit snyk config fix_github_create_pull_request_arguments' """
21
+ """ Default value of the field path 'Audit Snyk config fix_github_create_pull_request_arguments' """
22
22
 
23
23
 
24
24
  AUDIT_SNYK_MONITOR_ARGUMENTS_DEFAULT = ["--all-projects"]
25
- """ Default value of the field path 'Audit snyk config monitor_arguments' """
25
+ """ Default value of the field path 'Audit Snyk config monitor_arguments' """
26
26
 
27
27
 
28
28
  AUDIT_SNYK_PIPENV_SYNC_ARGUMENTS_DEFAULT: list[Any] = []
29
- """ Default value of the field path 'Audit snyk config pipenv_sync_arguments' """
29
+ """ Default value of the field path 'Audit Snyk config pipenv_sync_arguments' """
30
30
 
31
31
 
32
32
  AUDIT_SNYK_PIP_INSTALL_ARGUMENTS_DEFAULT = ["--user"]
33
- """ Default value of the field path 'Audit snyk config pip_install_arguments' """
33
+ """ Default value of the field path 'Audit Snyk config pip_install_arguments' """
34
34
 
35
35
 
36
36
  AUDIT_SNYK_TEST_ARGUMENTS_DEFAULT = ["--all-projects", "--fail-on=all", "--severity-threshold=medium"]
37
- """ Default value of the field path 'Audit snyk config test_arguments' """
37
+ """ Default value of the field path 'Audit Snyk config test_arguments' """
38
38
 
39
39
 
40
40
  class Audit(TypedDict, total=False):
@@ -57,9 +57,9 @@ class Audit(TypedDict, total=False):
57
57
 
58
58
  snyk: "AuditWithSnyk"
59
59
  """
60
- Audit with snyk.
60
+ Audit with Snyk.
61
61
 
62
- The audit snyk configuration
62
+ The audit Snyk configuration
63
63
 
64
64
  Aggregation type: oneOf
65
65
  """
@@ -75,7 +75,7 @@ Audit of outdated version
75
75
 
76
76
  class AuditSnykConfig(TypedDict, total=False):
77
77
  """
78
- Audit snyk config.
78
+ Audit Snyk config.
79
79
 
80
80
  The audit Pipfile configuration
81
81
  """
@@ -84,7 +84,7 @@ class AuditSnykConfig(TypedDict, total=False):
84
84
  """
85
85
  audit snyk test arguments.
86
86
 
87
- The snyk test arguments
87
+ The Snyk test arguments
88
88
 
89
89
  default:
90
90
  - --all-projects
@@ -96,7 +96,7 @@ class AuditSnykConfig(TypedDict, total=False):
96
96
  """
97
97
  audit snyk monitor arguments.
98
98
 
99
- The snyk monitor arguments
99
+ The Snyk monitor arguments
100
100
 
101
101
  default:
102
102
  - --all-projects
@@ -106,7 +106,7 @@ class AuditSnykConfig(TypedDict, total=False):
106
106
  """
107
107
  audit snyk fix arguments.
108
108
 
109
- The snyk fix arguments
109
+ The Snyk fix arguments
110
110
 
111
111
  default:
112
112
  - --all-projects
@@ -116,7 +116,7 @@ class AuditSnykConfig(TypedDict, total=False):
116
116
  """
117
117
  audit snyk fix pull request arguments.
118
118
 
119
- The snyk fix pull request extra arguments
119
+ The Snyk fix pull request extra arguments
120
120
 
121
121
  default:
122
122
  - --fill
@@ -127,7 +127,7 @@ class AuditSnykConfig(TypedDict, total=False):
127
127
  """
128
128
  audit snyk pip install arguments.
129
129
 
130
- The snyk pip install arguments
130
+ The Snyk pip install arguments
131
131
 
132
132
  default:
133
133
  - --user
@@ -137,7 +137,7 @@ class AuditSnykConfig(TypedDict, total=False):
137
137
  """
138
138
  audit snyk pipenv sync arguments.
139
139
 
140
- The snyk pipenv sync arguments
140
+ The Snyk pipenv sync arguments
141
141
 
142
142
  default:
143
143
  []
@@ -156,9 +156,9 @@ class AuditSnykConfig(TypedDict, total=False):
156
156
 
157
157
  AuditWithSnyk = Union["AuditSnykConfig", bool]
158
158
  """
159
- Audit with snyk.
159
+ Audit with Snyk.
160
160
 
161
- The audit snyk configuration
161
+ The audit Snyk configuration
162
162
 
163
163
  Aggregation type: oneOf
164
164
  """
@@ -1122,7 +1122,7 @@ class _PublishDockerConfigSnyk(TypedDict, total=False):
1122
1122
 
1123
1123
  monitor_args: Union[list[str], Literal[False]]
1124
1124
  """
1125
- Publish docker snyk monitor args.
1125
+ Publish Docker Snyk monitor args.
1126
1126
 
1127
1127
  The arguments to pass to the Snyk container monitor command
1128
1128
 
@@ -1134,7 +1134,7 @@ class _PublishDockerConfigSnyk(TypedDict, total=False):
1134
1134
 
1135
1135
  test_args: Union[list[str], Literal[False]]
1136
1136
  """
1137
- Publish docker snyk test args.
1137
+ Publish Docker Snyk test args.
1138
1138
 
1139
1139
  The arguments to pass to the Snyk container test command
1140
1140
 
@@ -23,12 +23,12 @@
23
23
  },
24
24
  "get-file-name": {
25
25
  "title": "The filename to get",
26
- "description": "The filename to get in the GitHub release",
26
+ "description": "The name of the file to get in the GitHub release",
27
27
  "type": "string"
28
28
  },
29
29
  "to-file-name": {
30
30
  "title": "The created tile name",
31
- "description": "The name of the final tile name we will create",
31
+ "description": "The name of the final tile we will create",
32
32
  "type": "string"
33
33
  },
34
34
  "tar-file-name": {
@@ -12,51 +12,51 @@
12
12
  "type": "boolean"
13
13
  },
14
14
  "audit_snyk": {
15
- "title": "Audit with snyk",
16
- "description": "The audit snyk configuration",
15
+ "title": "Audit with Snyk",
16
+ "description": "The audit Snyk configuration",
17
17
  "oneOf": [
18
18
  {
19
- "title": "Audit snyk config",
19
+ "title": "Audit Snyk config",
20
20
  "description": "The audit Pipfile configuration",
21
21
  "type": "object",
22
22
  "properties": {
23
23
  "test_arguments": {
24
- "description": "The snyk test arguments",
24
+ "description": "The Snyk test arguments",
25
25
  "title": "audit snyk test arguments",
26
26
  "default": ["--all-projects", "--fail-on=all", "--severity-threshold=medium"],
27
27
  "type": "array",
28
28
  "items": { "type": "string" }
29
29
  },
30
30
  "monitor_arguments": {
31
- "description": "The snyk monitor arguments",
31
+ "description": "The Snyk monitor arguments",
32
32
  "title": "audit snyk monitor arguments",
33
33
  "default": ["--all-projects"],
34
34
  "type": "array",
35
35
  "items": { "type": "string" }
36
36
  },
37
37
  "fix_arguments": {
38
- "description": "The snyk fix arguments",
38
+ "description": "The Snyk fix arguments",
39
39
  "title": "audit snyk fix arguments",
40
40
  "default": ["--all-projects"],
41
41
  "type": "array",
42
42
  "items": { "type": "string" }
43
43
  },
44
44
  "fix_github_create_pull_request_arguments": {
45
- "description": "The snyk fix pull request extra arguments",
45
+ "description": "The Snyk fix pull request extra arguments",
46
46
  "title": "audit snyk fix pull request arguments",
47
47
  "default": ["--fill", "--label=dependencies"],
48
48
  "type": "array",
49
49
  "items": { "type": "string" }
50
50
  },
51
51
  "pip_install_arguments": {
52
- "description": "The snyk pip install arguments",
52
+ "description": "The Snyk pip install arguments",
53
53
  "title": "audit snyk pip install arguments",
54
54
  "default": ["--user"],
55
55
  "type": "array",
56
56
  "items": { "type": "string" }
57
57
  },
58
58
  "pipenv_sync_arguments": {
59
- "description": "The snyk pipenv sync arguments",
59
+ "description": "The Snyk pipenv sync arguments",
60
60
  "title": "audit snyk pipenv sync arguments",
61
61
  "default": [],
62
62
  "type": "array",
@@ -304,7 +304,7 @@
304
304
  "properties": {
305
305
  "monitor_args": {
306
306
  "description": "The arguments to pass to the Snyk container monitor command",
307
- "title": "Publish docker snyk monitor args",
307
+ "title": "Publish Docker Snyk monitor args",
308
308
  "default": ["--app-vulns"],
309
309
  "oneOf": [
310
310
  {
@@ -318,7 +318,7 @@
318
318
  },
319
319
  "test_args": {
320
320
  "description": "The arguments to pass to the Snyk container test command",
321
- "title": "Publish docker snyk test args",
321
+ "title": "Publish Docker Snyk test args",
322
322
  "default": ["--app-vulns", "--severity-threshold=critical"],
323
323
  "oneOf": [
324
324
  {
@@ -19,7 +19,7 @@ strict = true
19
19
 
20
20
  [tool.poetry]
21
21
  name = "c2cciutils"
22
- version = "1.7.0.dev52"
22
+ version = "1.7.0.dev56"
23
23
  description = "Common utilities for Camptocamp CI"
24
24
  readme = "README.md"
25
25
  authors = ["Camptocamp <info@camptocamp.com>"]
@@ -107,6 +107,8 @@ requires = [
107
107
  "poetry-core>=1.0.0",
108
108
  "poetry-dynamic-versioning[plugin]>=0.19.0",
109
109
  "poetry-plugin-tweak-dependencies-version",
110
+ "poetry-dynamic-versioning",
111
+ # "poetry-plugin-drop-python-upper-constraint",
110
112
  ]
111
113
  build-backend = "poetry.core.masonry.api"
112
114
 
@@ -115,7 +117,7 @@ enable = false
115
117
  vcs = "git"
116
118
  pattern = "^(?P<base>\\d+(\\.\\d+)*)"
117
119
  format-jinja = """
118
- {%- if env.get("VERSION_TYPE") in ("version_branch", "feature_branch") -%}
120
+ {%- if env.get("VERSION_TYPE") == "version_branch" -%}
119
121
  {{serialize_pep440(bump_version(base, 1 if env.get("IS_MASTER") == "TRUE" else 2), dev=distance)}}
120
122
  {%- elif distance == 0 -%}
121
123
  {{serialize_pep440(base)}}
@@ -57,7 +57,7 @@ entry_points = \
57
57
 
58
58
  setup_kwargs = {
59
59
  'name': 'c2cciutils',
60
- 'version': '1.7.0.dev52',
60
+ 'version': '1.7.0.dev56',
61
61
  'description': 'Common utilities for Camptocamp CI',
62
62
  'long_description': '# C2C CI utils\n\n## Publishing\n\nThe main goals of C2C CI utils is to offer the commands and the workflows to have the following project structure:\n\nHave stabilization branches named by default `<major>.<minor>`.\nHave the release named by default `<major>.<minor>.<patch>`.\n\nWith C2C CI utils you can publish a python package and a Docker image from the same repository.\n\nThe default publishing are:\n\n- Push on the `<major>.<minor>` branch will publish Docker images.\n- Create the tag `<major>.<minor>.<patch>` will publish the Docker images, and the Python package.\n- Push on a feature branch (whatever other name) will publish the Docker images.\n- Delete a feature branch will delete the Docker images.\n- Push on the `master` branch will publish the Docker images with the master tag (Publishing a python package is also possible).\n- The version at the last line of the `SECURITY.md` of the `master` branch will be also published using the `latest` tag,\n this will respect the `tags` present in the configuration\n- In the `SECURITY.md` file of the `master` branch we can also add a column `Alternate Tag` to publish the Docker images with another tag,\n this will respect the `tags` present in the configuration (only for Docker).\n\nThe Docker images are published on Docker Hub and GitHub Container Registry.\n\nYou can run the publishing locally in dry-run mode:\n\n```bash\nGITHUB_REF=... c2cciutils-publish --dry-run ...\n```\n\n## Changelog\n\nWhen we create a tag by default with the `changelog` workflow a release is created on GitHub, a changelog is\ngenerated and added to the release.\n\n## Security\n\nThe security is managed by the `c2cciutils-audit` command with Snyk, it will audit the dependencies of the project on every\nstabilization branches, if possible a pull request is created automatically to update the dependencies.\n\nWhen we publish a Docker image the generated image is monitored by Snyk, this means that Snyk will search\nfor all the dependencies and send the list to the Snyk web site to be monitored.\nWe also do a test of the image and log the result (This will never cause the build to fail).\n\n## Checks\n\nC2C CI utils will no more provide a tool to do a check of the project, this is replaced by `pre-commit`,\na base configuration is provided in the example project.\n\n## Pull request checks\n\nA workflow is provided to run the checks on the pull requests, it will run the `c2cciutils-pr-checks` command.\n\n- Check that the commit message and the pull request title start with a capital letter.\n- Check that there aren\'t any spelling issue in the commit message and in the pull request title.\n- Add a message to the pull request with a link to the JIRA issue if the pull request branch name starts with\n `[a-zA-Z]+-[0-9]+-` or end with `-[a-zA-Z]+-[0-9]+`.\n\n## Dependencies\n\nIn the example project there is a basic Renovate configuration, it will update the dependencies of the project.\nThere is also a workflow to add a review on the Renovate pull requests to make the auto merge working on\nrepository that required a review.\n\n## Backports\n\nA workflow is provided to backport the pull requests on the stabilization branches, it will be triggered by\nadding a label named `backport <destination_branch>` on the pull request.\n\n## Old workflows\n\nGitHub will retain all the old workflows, so we need to delete them, the `delete-old-workflows-run`\nworkflow will delete the workflows older than 500 days.\n\n## Workflows\n\nC2cciutils make easier to have those workflows in a project:\n\n- `audit.yaml`: Audit the stabilization branches of the application against vulnerabilities in the python and node dependency\n- `auto-review.yaml`: Auto review the Renovate pull requests\n- `backport.yaml`: Trigger the backports (work with labels)\n- `clean.yaml`: Clean the Docker images related on a deleted feature branch\n- `main.yaml`: Main workflow especially with the c2cciutils-checks command\n- `changelog.yaml`: Generate the changelog and create the release on GitHub\n- `delete-old-workflows-run.yaml`: Delete the old workflows\n- `pr-checks.yaml`: Run the checks on the pull requests\n\nAll the provided commands used in the workflow:\n\n- `c2cciutils`: some generic tools.\n- `c2cciutils-version`: Create a new version of the project.\n- `c2cciutils-checks`: Run the checks on the code (those checks don\'t need any project dependencies).\n- `c2cciutils-audit`: Do the audit, the main difference with checks is that it can change between runs on the same code.\n- `c2cciutils-publish`: Publish the project.\n- `c2cciutils-clean`: Delete Docker images on Docker Hub after corresponding branch have been deleted.\n\n## Utilities\n\nThe following utilities are provided:\n\n- `c2cciutils`: some generic tools.\n- `c2cciutils-download-applications`: Download the applications with version managed by Renovate, see below.\n- `c2cciutils-docker-logs`: Display the logs of the application in Docker (compose).\n- `c2cciutils-k8s-install`: Install a k3d / k3s cluster, see below.\n- `c2cciutils-k8s-logs`: Display the logs of the application in the k8s cluster, see below.\n- `c2cciutils-k8s-db`: Create a database in the k8s cluster, see below.\n- `c2cciutils-k8s-wait`: Wait that the application started correctly in the cluster, see below.\n- `c2cciutils-docker-versions-gen`: Generate the Docker package versions file (`ci/dpkg-versions.yaml`), see below.\n- `c2cciutils-pin-pipenv`: Display all the dependencies that\'s in the `Pipenv.lock` but not in the `Pipenv` to be able to pin them.\n- `c2cciutils-trigger-image-update`: Trigger the ArgoCD repository about image update on the CI (automatically done in the publishing).\n- `c2cciutils-google-calendar`: Tool to test the Google credentials for calendar API and refresh them if needed. See `c2cciutils-google-calendar -h` for more information.\n\n## New project\n\nThe content of `example-project` can be a good base for a new project.\n\n## New version\n\nRequirements: the right version (>= 1.6) of `c2cciutils` should be installed with the `version` extra.\n\nTo create a new minor version you just should run `c2cciutils-version --version=<version>`.\n\nYou are welcome to run `c2cciutils-version --help` to see what\'s it\'s done.\n\nNote that it didn\'t create a tag, you should do it manually.\n\nTo create a patch version you should just create tag.\n\n## Secrets\n\nIn the CI we need to have the following secrets::\n\n- `HAS_SECRETS` to be set to \'HAS_SECRETS\', to avoid error errors from external\n pull requests, already set globally on Camptocamp organization.\n- `GOPASS_CI_GITHUB_TOKEN` and `CI_GPG_PRIVATE_KEY` required to initialize the gopass password store,\n the secrets exists in the Camptocamp organization but not shared on all project, then you should add\n your project to the shared list.\n\n## Use locally, in the projects that use c2cciutils\n\nInstall it: `python3 -m pip install --user --requirement ci/requirements.txt`\nDry run publish: `GITHUB_REF=... c2cciutils-publish --dry-run ...`\n\n## Configuration\n\nYou can get the current configuration with `c2cciutils --get-config`, the default configuration depends on your project.\nNote that it didn\'t contain the default defined the schema and visible in the [generated documentation](./config.md).\n\nYou can override the configuration with the file `ci/config.yaml`.\n\nAt the base of the configuration you have:\n\n- `version`: Contains some regular expressions to find the versions branches and tags, and to convert them into application versions.\n- `audit`: The audit configuration, see `c2cciutils/audit.py` for more information.\n- `publish`: The publishing configuration, see `c2cciutils/publish.py` for more information.\n\nMany actions can be disabled by setting the corresponding configuration part to `False`.\n\n## SECURITY.md\n\nThe `SECURITY.md` file should contain the security policy of the repository, especially the end of\nsupport dates.\n\nFor compatibility with `c2cciutils` it should contain an array with at least the columns\n`Version` and `Supported Until`. The `Version` column will contain the concerned version.\nThe `Supported Until` will contain the date of end of support `dd/mm/yyyy`.\nIt can also contain the following sentences:\n\n- `Unsupported`: no longer supported => no audit, no rebuild.\n- `Best effort`: the support is ended, it is still rebuilt and audited, but this can be stopped without any notice.\n- `To be defined`: not yet released or the date will be set related of another project release date (like for GeoMapFish).\n\nSee also [GitHub Documentation](https://docs.github.com/en/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)\n\n## IDE\n\nThe IDE should be configured as:\n\n- using `black` and `isort` without any arguments,\n- using the `editorconfig` configuration.\n\n### VScode\n\n- Recommend extensions to work well with c2cciutils:\n - [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) And use EditorConfig\n - [shell-format](https://marketplace.visualstudio.com/items?itemName=foxundermoon.shell-format) With the configuration\n `"shellformat.flag": "-bn"`.\n - [Better TOML](https://marketplace.visualstudio.com/items?itemName=bodil.prettier-toml)\n- Other recommend extensions:\n - [hadolint](https://marketplace.visualstudio.com/items?itemName=exiasr.hadolint)\n - [Code Spell Checker](https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker)\n\nSelect a formatter:\n\n- `CTRL+MAJ+P`\n- Format document With...\n- Configure Default Formatter...\n- Select the formatter\n\n## Publishing\n\n### To pypi\n\nThe config is like this:\n\n```yaml\nversions:\n # List of kinds of versions you want to publish, that can be:\n # rebuild (specified with --type),\n # version_tag, version_branch, feature_branch, feature_tag (for pull request)\n```\n\nIt we have a `setup.py` file, we will be in legacy mode:\nWhen publishing, the version computed from arguments or `GITHUB_REF` is put in environment variable `VERSION`, thus you should use it in `setup.py`, example:\n\n```python\nVERSION = os.environ.get("VERSION", "1.0.0")\n```\n\nAlso we consider that we use `poetry` with [poetry-dynamic-versioning](https://pypi.org/project/poetry-dynamic-versioning/) to manage the version, and [poetry-plugin-tweak-dependencies-version](https://pypi.org/project/poetry-plugin-tweak-dependencies-version/) to manage the dependencies versions.\n\nExample of configuration:\n\n```toml\n[tool.poetry-dynamic-versioning]\nenable = true\nvcs = "git"\npattern = "^(?P<base>\\\\d+(\\\\.\\\\d+)*)"\nformat-jinja = """\n{%- if env.get("VERSION_TYPE") == "version_branch" -%}\n{{serialize_pep440(bump_version(base, 1 if env.get("IS_MASTER") == "TRUE" else 2), dev=distance)}}\n{%- elif distance == 0 -%}\n{{serialize_pep440(base)}}\n{%- else -%}\n{{serialize_pep440(bump_version(base), dev=distance)}}\n{%- endif -%}\n"""\n\n```\n\nNote that we can access to the environment variables `VERSION`,`VERSION_TYPE` and `IS_MASTER`.\n\nThen by default:\n\n- Tag with `1.2.3` => release `1.2.3`\n- Commit on feature branch just do a validation\n- Commit on `master` branch after the tag 1.3.0 => release `1.4.0.dev1`\n- Commit on `1.3` branch after the tag 1.3.0 => release `1.3.1.dev1`\n\nTo make it working in the `Dockerfile` you should have in the `poetry` stage:\n\n```Dockerfile\nENV POETRY_DYNAMIC_VERSIONING_BYPASS=dev\nRUN poetry export --extras=checks --extras=publish --extras=audit --output=requirements.txt \\\n && poetry export --with=dev --output=requirements-dev.txt\n```\n\nAnd in the `run` stage\n\n```Dockerfile\nARG VERSION=dev\nRUN --mount=type=cache,target=/root/.cache \\\n POETRY_DYNAMIC_VERSIONING_BYPASS=${VERSION} python3 -m pip install --disable-pip-version-check --no-deps --editable=.\n```\n\nAnd in the `Makefile`:\n\n```Makefile\nVERSION = $(strip $(shell poetry version --short))\n\n.PHONY: build\nbuild: ## Build the Docker images\n docker build --build-arg=VERSION=$(VERSION) --tag=$(GITHUB_REPOSITORY) .\n```\n\n### To Docker registry\n\nThe config is like this:\n\n```yaml\nlatest: True\nimages:\n - # The base name of the image we want to publish\n name:\nrepository:\n <internal_name>:\n # The fqdn name of the server if not Docker hub\n server:\n # List of kinds of versions you want to publish, that can be: rebuild (specified using --type),\n # version_tag, version_branch, feature_branch, feature_tag (for pull request)\n version:\n # List of tags we want to publish interpreted with `template(version=version)`\n # e.g. if you use `{version}-lite` when you publish the version `1.2.3` the source tag\n # (that should be built by the application build) is `latest-lite`, and it will be published\n # with the tag `1.2.3-lite`.\n tags:\n # If your images are published by different jobs you can separate them in different groups\n # and publish them with `c2cciutils-publish --group=<group>`\n group:\n```\n\nBy default, the last line of the `SECURITY.md` file will be published (`docker`) with the tag\n`latest`. Set `latest` to `False` to disable it.\n\nWith the `c2cciutils-clean` the images on Docker hub for `feature_branch` will be removed on branch removing.\n\n## Download applications\n\nIn case some executables or applications from GitHub releases or any other URLs are required on the CI host\nand are not handled by any dependency manager, we provide a set of tools to install them and manage upgrades\nthrough Renovate.\n\nCreate an application file (e.-g. `applications.yaml`) with:\n\n```yaml\n# yaml-language-server: $schema=https://raw.githubusercontent.com/camptocamp/c2cciutils/master/c2cciutils/schema-applications.json\n\n# Application from GitHub release\n<organization>/<project>:\n get-file-name: <file name present in the release>\n to-file-name: <The file name you want to create in ~/.local/bin>\n finish-command: # The command you want to run after the file is downloaded\n - - chmod # To be executable (usually required)\n - +x\n - <to-file-name>\n - - <to-file-name> # Print the version of the application\n - --version\n# Application from GitHub release in a tar file (or tar.gz)\n<organization>/<project>:\n get-file-name: <file name present in the release>\n type: tar\n tar-file-name: <The file name available in the tar file>\n to-file-name: <The file name you want to create in ~/.local/bin>\n finish-command: [...] # The command you want to run after the file is downloaded\n# Application from an URL\n<application reference name>:\n url-pattern: <The URL used to download the application>\n to-file-name: <The file name you want to create in ~/.local/bin>\n finish-command: [...] # The command you want to run after the file is downloaded\n```\n\nIn the attributes `url-pattern`, `get-file-name` you can use the following variables:\n\n- `{version}`: The version of the application present in the version file.\n- `{version_quote}`: The URL encoded version.\n- `{short_version}`: The version without the `v` prefix.\n\nThe `applications-versions.yaml` file is a map of applications and their versions.\n\nAdd in your Renovate configuration:\n\n```json5\n regexManagers: [\n {\n fileMatch: [\'^applications-versions.yaml$\'],\n matchStrings: [\n \'(?<depName>[^\\\\s]+): (?<currentValue>[^\\\\s]+) # (?<datasource>[^\\\\s]+)\',\n ],\n },\n ],\n```\n\nNow you need to call `c2cciutils-download-applications --applications-file=applications.yaml --versions-file=applications-version.yaml`\nto install required applications on CI host before using them (an already installed application is installed only if needed).\n\n## Use Renovate to trigger a new build instead of the legacy rebuild\n\nRun the command `c2cciutils-docker-versions-gen camptocamp/image[:tag]` to generate a file that is a kind of package lock of the Debian packages in the file `ci/dpkg-versions.yaml`.\n\nAdd in your renovate configuration:\n\n```javascript\n regexManagers: [\n {\n fileMatch: [\'^ci/dpkg-versions.yaml$\'],\n matchStrings: [" *(?<depName>[^\'\\\\s]+): \'?(?<currentValue>[^\'\\\\s/]*[0-9][^\'\\\\s/]*)\'?"],\n datasourceTemplate: \'repology\',\n versioningTemplate: \'loose\',\n },\n ],\n```\n\nWhen a new version of a Debian package will be available:\n\n- Renovate will automatically open a pull request to update the file `ci/dpkg-versions.yaml`.\n- And the continuous integration will build a new fresh Docker image with latest versions of all Debian packages.\n\n## Kubernetes\n\nC2cciutils provide some commands for Kubernetes.\n\nYou can define a workflow like that:\n\n```yaml\n- name: Install k3s/k3d (Kubernetes cluster)\n run: c2cciutils-k8s-install\n\n- name: Create a database to do the tests\n run: c2cciutils-k8s-db --script=<my_script>.sql\n\n- name: Install the application in the Kubernetes cluster\n run: kubectl apply -f <my_application>.yaml\n\n- name: Wait that the application is ready\n run: c2cciutils-k8s-wait\n- name: Print the application status and logs\n run: c2cciutils-k8s-logs\n if: always()\n\n- name: Uninstall the application\n run: kubectl delete -f <my_application>.yaml || true\n\n- name: Cleanup the database\n run: c2cciutils-k8s-db --cleanup\n```\n\n`c2cciutils-k8s-install` can be configured in the `ci/config.yaml` file, in section `k8s/k3d/install-commands`, default is:\n\n```yaml\n- - k3d\n cluster\n create\n test-cluster\n --no-lb\n --no-rollback\n```\n\nSee also: [K3d cluster create documentation](https://k3d.io/v4.4.8/usage/commands/k3d_cluster_create/).\n\n`c2cciutils-k8s-db` can be configured in the `ci/config.yaml` file, in section `k8s/db/chart-options`, default is:\n\n```yaml\npersistence.enabled: \'false\'\ntls.enabled: \'true\'\ntls.autoGenerated: \'true\'\npostgresqlPassword: mySuperTestingPassword\nvolumePermissions.enabled: \'true\'\n```\n\nSee also: [Parameters documentations](https://github.com/bitnami/charts/tree/master/bitnami/postgresql#parameters).\n\n## Contributing\n\nInstall the pre-commit hooks:\n\n```bash\npip install pre-commit\npre-commit install --allow-missing-config\n```\n',
63
63
  'author': 'Camptocamp',