Skip to content

Releases: Boavizta/boaviztapi

v1.3.8

09 Feb 17:55
e7f929a
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.3.7...v1.3.8

v1.3.7

13 Dec 09:40
6ff75d8
Compare
Choose a tag to compare

What's Changed

  • fix(docker): fix Docker build and update dev instructions for running image locally by @Shillaker in #353
  • Change life time of AWS servers from 4 to 6 years (#354) by @davidkopp in #354

New Contributors

Full Changelog: v1.3.6...v1.3.7

v1.3.6

11 Dec 18:25
c5f0522
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.3.4...v1.3.6

v1.3.4

10 Dec 17:27
fb33254
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.3...1.3.4

v1.3

25 Sep 15:12
Compare
Choose a tag to compare

This release adds Azure instances to the API and fixes some security issues.

What's Changed

New Contributors

Full Changelog: v1.2.4...v1.3

v1.2.4

18 Mar 12:07
5c86f53
Compare
Choose a tag to compare

What's Changed

Important

This version may slightly update the values of embedded impacts returned by he API (e.g. Boavizta/cloud-scanner#467)

New Contributors

Full Changelog: v1.2.2...v1.2.4

v1.2.2

17 Jan 21:42
23cb4b7
Compare
Choose a tag to compare
Update pyproject.toml

v1.2.1

16 Jan 00:12
Compare
Choose a tag to compare

v1.2.1

What's Changed

Adding new cloud instances is now easier. Simply define the resources they reserve and identify the server archetype on which the instance will be hosted. Refer to the contribution documentation for more information.

Internal changes

  • Externalizing impacts computation outside the asset's model by creating a service for this purpose (boaviztapi/service/impacts_computation.py)
  • Updating cloud instance model and impacts computation in line with : #252 (comment)
  • Improve impact model (boaviztapi/model/impact.py). All the assets keep the impacts as an attribute once they have been calculated. Performance is significantly improved in the event of a verbose call.

Bug fixes

  • Power consumption was modelled for one component unit. Consumption was only multiplied by the number of components when calculating impacts at device level. The consumption of the component now reflects the consumption of all the units.
  • #256
  • #257
  • #243
  • #248

Breaking changes

  • 'instance_per_instance' is no longer included in the verbose output of the cloud route.
  • Previously, the verbose returned the impacts of each platform's components in their entirety. Now, only the impacts associated with the instance are returned for each component. Components impacts returned by cloud router shouldn't be divided by instance_per_instance.

Contributors

New Contributors

Other contributors

@da-ekchajzer
@samuelrince
@JacobValdemar

Full Changelog: v1.1.0...v1.2.0

v1.1.0

19 Nov 17:12
cd7cb83
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.1...v1.1.0

v1.0.1

12 Oct 11:30
Compare
Choose a tag to compare