| Name | datateer-cli JSON |
| Version |
0.26.2
JSON |
| download |
| home_page | None |
| Summary | Datateer CLI to support devops and infrastructure |
| upload_time | 2024-04-03 21:26:24 |
| maintainer | None |
| docs_url | None |
| author | Datateer |
| requires_python | <4.0,>=3.9 |
| license | None |
| keywords |
|
| VCS |
|
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# Scripts for devops
- [Scripts for devops](#scripts-for-devops)
- [Development](#development)
- [Setup](#setup)
- [Fixing Semantic Release](#fixing-semantic-release)
- [Disclaimer](#disclaimer)
- [Steps](#steps)
## Development
### Setup
1. poetry install
2. poetry shell
## Fixing Semantic Release
* [Source](https://github.com/relekang/python-semantic-release)
* [Action](https://python-semantic-release.readthedocs.io/en/latest/automatic-releases/github-actions.html)
* [Documentation](https://python-semantic-release.readthedocs.io/en/latest/#getting-started)
* [Configuration](https://python-semantic-release.readthedocs.io/en/latest/configuration.html)
* These are being stored in the file `pyproject.toml` and its `tools.semantic_release` section
This is to resolve issues cuased by manually creating a version tag in conflict with what the CI process wants to create.
### Disclaimer
The below needs to be completed as an administrator of the git repo
This process is required because the semantic release action being used requires matching information
### Steps
1) Pull down the current main branch to your local
1) Ensure that your git status shows no changes
2) Record the current tag without the `v` prefix
3) Update files:
1) datateer_cli/\_\_init__.py
1) set `__version__` to the currnet version
2) CHANGELOG.md
1) follow the format seen in the file adding the current version
4) git add .
5) git commit -m "<current version>"
1) ensure that there isn't any other text other than the version for the commit message
6) git push
Now you have brought the repo back into a state where the semantic release can work as expected
Raw data
{
"_id": null,
"home_page": null,
"name": "datateer-cli",
"maintainer": null,
"docs_url": null,
"requires_python": "<4.0,>=3.9",
"maintainer_email": null,
"keywords": null,
"author": "Datateer",
"author_email": "dev@datateer.com",
"download_url": "https://files.pythonhosted.org/packages/74/a8/df2622f15815e140095fc3417d308be221394d55f78da7649389dd9242df/datateer_cli-0.26.2.tar.gz",
"platform": null,
"description": "# Scripts for devops\n\n- [Scripts for devops](#scripts-for-devops)\n - [Development](#development)\n - [Setup](#setup)\n - [Fixing Semantic Release](#fixing-semantic-release)\n - [Disclaimer](#disclaimer)\n - [Steps](#steps)\n\n## Development\n\n### Setup\n1. poetry install\n2. poetry shell\n\n## Fixing Semantic Release\n\n* [Source](https://github.com/relekang/python-semantic-release)\n* [Action](https://python-semantic-release.readthedocs.io/en/latest/automatic-releases/github-actions.html)\n* [Documentation](https://python-semantic-release.readthedocs.io/en/latest/#getting-started)\n* [Configuration](https://python-semantic-release.readthedocs.io/en/latest/configuration.html)\n * These are being stored in the file `pyproject.toml` and its `tools.semantic_release` section\n\nThis is to resolve issues cuased by manually creating a version tag in conflict with what the CI process wants to create.\n\n### Disclaimer\n\nThe below needs to be completed as an administrator of the git repo\n\nThis process is required because the semantic release action being used requires matching information\n\n### Steps\n\n1) Pull down the current main branch to your local\n 1) Ensure that your git status shows no changes\n2) Record the current tag without the `v` prefix\n3) Update files:\n 1) datateer_cli/\\_\\_init__.py\n 1) set `__version__` to the currnet version\n 2) CHANGELOG.md\n 1) follow the format seen in the file adding the current version\n4) git add .\n5) git commit -m \"<current version>\"\n 1) ensure that there isn't any other text other than the version for the commit message\n6) git push\n\nNow you have brought the repo back into a state where the semantic release can work as expected\n",
"bugtrack_url": null,
"license": null,
"summary": "Datateer CLI to support devops and infrastructure",
"version": "0.26.2",
"project_urls": null,
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "fd52502899474d7269fe3cd5a043aa9e06e5b29f46345e19b72f82817bce31d8",
"md5": "87fb406e81df269bc99714787d081b1e",
"sha256": "039dfd0872b3f884be07a18f9625a986e4314ec2a7630ac827813800b8238117"
},
"downloads": -1,
"filename": "datateer_cli-0.26.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "87fb406e81df269bc99714787d081b1e",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4.0,>=3.9",
"size": 33164,
"upload_time": "2024-04-03T21:26:22",
"upload_time_iso_8601": "2024-04-03T21:26:22.474780Z",
"url": "https://files.pythonhosted.org/packages/fd/52/502899474d7269fe3cd5a043aa9e06e5b29f46345e19b72f82817bce31d8/datateer_cli-0.26.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "74a8df2622f15815e140095fc3417d308be221394d55f78da7649389dd9242df",
"md5": "e4c8a0c720420ce52673d759fd96716d",
"sha256": "148c3a03cbb500c05af2af433e0a28b6767890980d0823f0999749bd527d7531"
},
"downloads": -1,
"filename": "datateer_cli-0.26.2.tar.gz",
"has_sig": false,
"md5_digest": "e4c8a0c720420ce52673d759fd96716d",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4.0,>=3.9",
"size": 22212,
"upload_time": "2024-04-03T21:26:24",
"upload_time_iso_8601": "2024-04-03T21:26:24.808396Z",
"url": "https://files.pythonhosted.org/packages/74/a8/df2622f15815e140095fc3417d308be221394d55f78da7649389dd9242df/datateer_cli-0.26.2.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-03 21:26:24",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "datateer-cli"
}
