# HEA Server AWS Accounts Microservice
[Research Informatics Shared Resource](https://risr.hci.utah.edu), [Huntsman Cancer Institute](https://hci.utah.edu),
Salt Lake City, UT
The HEA Server AWS Accounts Microservice is It manages the AWS account information details.
## Version 1.1.3
* Another attempt at fixing the crash regression.
## Version 1.1.2
* Fixed crash regression.
## Version 1.1.1
* Fixed new bucket form submission.
## Version 1.1.0
* Removed the PUT and DELETE account calls because neither works.
## Version 1.0.8
* Addressed occasional slowdown getting one account.
## Version 1.0.7
* Addressed occasional slowdown getting accounts.
## Version 1.0.6
* Display type display name in properties card, and return the type display name from GET calls.
## Version 1.0.5
* Improved performance getting accounts.
## Version 1.0.4
* Corrected caching issue.
## Version 1.0.3
* Improved error handling when the user lacks authorization for some AWS account information.
## Version 1.0.2
* Avoid a 500 error when retrieving accounts when attempting to access a suspended account.
* AWS account info requests return more complete information.
* Omit shares from the properties template.
## Version 1.0.1
* Improved performance.
## Version 1
Initial release.
## Runtime requirements
* Python 3.10 or 3.11.
## Development environment
### Build requirements
* Any development environment is fine.
* On Windows, you also will need:
* Build Tools for Visual Studio 2019, found at https://visualstudio.microsoft.com/downloads/. Select the C++ tools.
* git, found at https://git-scm.com/download/win.
* On Mac, Xcode or the command line developer tools is required, found in the Apple Store app.
* Python 3.10 or 3.11: Download and install it from https://www.python.org, and select the options to install for all
users and add Python to your environment variables. The install for all users option will help keep you from
accidentally installing packages into your Python installation's site-packages directory instead of to your virtualenv
environment, described below.
* Create a virtualenv environment using the `python -m venv <venv_directory>` command, substituting `<venv_directory>`
with the directory name of your virtual environment. Run `source <venv_directory>/bin/activate` (or `<venv_directory>/Scripts/activate` on Windows) to activate the virtual
environment. You will need to activate the virtualenv every time before starting work, or your IDE may be able to do
this for you automatically. **Note that PyCharm will do this for you, but you have to create a new Terminal panel
after you newly configure a project with your virtualenv.**
* From the project's root directory, and using the activated virtualenv, run `pip install wheel` followed by
`pip install -r requirements_dev.txt`. **Do NOT run `python setup.py develop`. It will break your environment.**
### Running tests
Run tests with the `pytest` command from the project root directory. To improve performance, run tests in multiple
processes with `pytest -n auto`.
### Testing using Swagger
Run `python ./run-swaggerui.py` and open up http://locahost:8080/docs in your web browser to get a UI for making REST
API calls.
### Versioning
Use semantic versioning as described in
https://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme. In addition,
while development is underway, the version should be the next version number suffixed by `.dev`.
### Version tags in git
Version tags should follow the format `heaserver-awsaccounts-<version>`, for example, `heaserver-awsaccounts-1.0.0`.
### Uploading to an index server
The following instructions assume separate stable and staging indexes. Numbered releases, including alphas and betas, go
into the stable index. Snapshots of works in progress go into the staging index. Thus, use staging to upload numbered
releases, verify the uploaded packages, and then upload to stable.
From the project's root directory:
1. For numbered releases, remove `.dev` from the version number in setup.py, tag it in git to indicate a release,
and commit to version control. Skip this step for developer snapshot releases.
2. Run `python setup.py clean --all sdist bdist_wheel` to create the artifacts.
3. Run `twine upload -r <repository> dist/<wheel-filename> dist/<tarball-filename>` to upload to the
repository. The repository name has to be defined in a twine configuration file such as `$HOME/.pypirc`.
4. For numbered releases, increment the version number in setup.py, append `.dev` to it, and commit to version
control with a commit message like, "Prepare for next development iteration."
Raw data
{
"_id": null,
"home_page": "https://risr.hci.utah.edu",
"name": "heaserver-accounts",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": "heaserver-accounts, microservice, healthcare, cancer, research, informatics",
"author": "Research Informatics Shared Resource, Huntsman Cancer Institute, Salt Lake City, UT",
"author_email": "Andrew.Post@hci.utah.edu",
"download_url": "https://files.pythonhosted.org/packages/c0/e1/4ac129c630581e7675babe0098a38067613670120a7a25c21bbf07994d12/heaserver_accounts-1.1.3.tar.gz",
"platform": null,
"description": "# HEA Server AWS Accounts Microservice\r\n[Research Informatics Shared Resource](https://risr.hci.utah.edu), [Huntsman Cancer Institute](https://hci.utah.edu),\r\nSalt Lake City, UT\r\n\r\nThe HEA Server AWS Accounts Microservice is It manages the AWS account information details.\r\n\r\n## Version 1.1.3\r\n* Another attempt at fixing the crash regression.\r\n\r\n## Version 1.1.2\r\n* Fixed crash regression.\r\n\r\n## Version 1.1.1\r\n* Fixed new bucket form submission.\r\n\r\n## Version 1.1.0\r\n* Removed the PUT and DELETE account calls because neither works.\r\n\r\n## Version 1.0.8\r\n* Addressed occasional slowdown getting one account.\r\n\r\n## Version 1.0.7\r\n* Addressed occasional slowdown getting accounts.\r\n\r\n## Version 1.0.6\r\n* Display type display name in properties card, and return the type display name from GET calls.\r\n\r\n## Version 1.0.5\r\n* Improved performance getting accounts.\r\n\r\n## Version 1.0.4\r\n* Corrected caching issue.\r\n\r\n## Version 1.0.3\r\n* Improved error handling when the user lacks authorization for some AWS account information.\r\n\r\n## Version 1.0.2\r\n* Avoid a 500 error when retrieving accounts when attempting to access a suspended account.\r\n* AWS account info requests return more complete information.\r\n* Omit shares from the properties template.\r\n\r\n## Version 1.0.1\r\n* Improved performance.\r\n\r\n## Version 1\r\nInitial release.\r\n\r\n## Runtime requirements\r\n* Python 3.10 or 3.11.\r\n\r\n## Development environment\r\n\r\n### Build requirements\r\n* Any development environment is fine.\r\n* On Windows, you also will need:\r\n * Build Tools for Visual Studio 2019, found at https://visualstudio.microsoft.com/downloads/. Select the C++ tools.\r\n * git, found at https://git-scm.com/download/win.\r\n* On Mac, Xcode or the command line developer tools is required, found in the Apple Store app.\r\n* Python 3.10 or 3.11: Download and install it from https://www.python.org, and select the options to install for all\r\nusers and add Python to your environment variables. The install for all users option will help keep you from\r\naccidentally installing packages into your Python installation's site-packages directory instead of to your virtualenv\r\nenvironment, described below.\r\n* Create a virtualenv environment using the `python -m venv <venv_directory>` command, substituting `<venv_directory>`\r\nwith the directory name of your virtual environment. Run `source <venv_directory>/bin/activate` (or `<venv_directory>/Scripts/activate` on Windows) to activate the virtual\r\nenvironment. You will need to activate the virtualenv every time before starting work, or your IDE may be able to do\r\nthis for you automatically. **Note that PyCharm will do this for you, but you have to create a new Terminal panel\r\nafter you newly configure a project with your virtualenv.**\r\n* From the project's root directory, and using the activated virtualenv, run `pip install wheel` followed by\r\n `pip install -r requirements_dev.txt`. **Do NOT run `python setup.py develop`. It will break your environment.**\r\n\r\n### Running tests\r\nRun tests with the `pytest` command from the project root directory. To improve performance, run tests in multiple\r\nprocesses with `pytest -n auto`.\r\n\r\n### Testing using Swagger\r\nRun `python ./run-swaggerui.py` and open up http://locahost:8080/docs in your web browser to get a UI for making REST\r\nAPI calls.\r\n\r\n### Versioning\r\nUse semantic versioning as described in\r\nhttps://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme. In addition,\r\nwhile development is underway, the version should be the next version number suffixed by `.dev`.\r\n\r\n### Version tags in git\r\nVersion tags should follow the format `heaserver-awsaccounts-<version>`, for example, `heaserver-awsaccounts-1.0.0`.\r\n\r\n### Uploading to an index server\r\nThe following instructions assume separate stable and staging indexes. Numbered releases, including alphas and betas, go\r\ninto the stable index. Snapshots of works in progress go into the staging index. Thus, use staging to upload numbered\r\nreleases, verify the uploaded packages, and then upload to stable.\r\n\r\nFrom the project's root directory:\r\n1. For numbered releases, remove `.dev` from the version number in setup.py, tag it in git to indicate a release,\r\nand commit to version control. Skip this step for developer snapshot releases.\r\n2. Run `python setup.py clean --all sdist bdist_wheel` to create the artifacts.\r\n3. Run `twine upload -r <repository> dist/<wheel-filename> dist/<tarball-filename>` to upload to the\r\n repository. The repository name has to be defined in a twine configuration file such as `$HOME/.pypirc`.\r\n4. For numbered releases, increment the version number in setup.py, append `.dev` to it, and commit to version\r\ncontrol with a commit message like, \"Prepare for next development iteration.\"\r\n",
"bugtrack_url": null,
"license": null,
"summary": "Manages account information",
"version": "1.1.3",
"project_urls": {
"Homepage": "https://risr.hci.utah.edu"
},
"split_keywords": [
"heaserver-accounts",
" microservice",
" healthcare",
" cancer",
" research",
" informatics"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "083ffea2ed807c6a37b5dbcbb984e0271db30e3ae3f2218a238f983e529f488b",
"md5": "3c9c78361f34e690b99ac69a3dc69dbd",
"sha256": "93c005750263014afdd9c9674d13adcae5a77c9e45a59aa5d8a4e29d374d665b"
},
"downloads": -1,
"filename": "heaserver_accounts-1.1.3-py3-none-any.whl",
"has_sig": false,
"md5_digest": "3c9c78361f34e690b99ac69a3dc69dbd",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 16732,
"upload_time": "2024-05-05T19:43:59",
"upload_time_iso_8601": "2024-05-05T19:43:59.988557Z",
"url": "https://files.pythonhosted.org/packages/08/3f/fea2ed807c6a37b5dbcbb984e0271db30e3ae3f2218a238f983e529f488b/heaserver_accounts-1.1.3-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "c0e14ac129c630581e7675babe0098a38067613670120a7a25c21bbf07994d12",
"md5": "c303d7f76e4662327e65a8dad7ad4efa",
"sha256": "3bb1d9f9a1ab8ae1684d8f924e63b1ab0b95fee4dbf426f8bb7645f55833ddcd"
},
"downloads": -1,
"filename": "heaserver_accounts-1.1.3.tar.gz",
"has_sig": false,
"md5_digest": "c303d7f76e4662327e65a8dad7ad4efa",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 26005,
"upload_time": "2024-05-05T19:44:03",
"upload_time_iso_8601": "2024-05-05T19:44:03.195578Z",
"url": "https://files.pythonhosted.org/packages/c0/e1/4ac129c630581e7675babe0098a38067613670120a7a25c21bbf07994d12/heaserver_accounts-1.1.3.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-05-05 19:44:03",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "heaserver-accounts"
}
JSON