Fleio 2022.07.0 is now available in beta and you can test it in your staging environment, since this is not recommended for production.
You can read more about our release model here.
API versions per region
Prior to 2022.07.0 release, the API version for OpenStack services were retrieved from OpenStack, only for the default region:
This could have caused issues since different regions may have different API versions for the same services (or some service my not exist at all on certain regions).
With the latest release, we have changed this and now Fleio is retrieving and saving the API versions for all regions, and it’s using the region’s specific API version when calling the OpenStack API.
Note that after upgrading to 2022.07.0, you might need to run
fleio sync --region to sync the OpenStack API versions with Fleio.
Possibility to change saved CC details
If you remember from our 2022.06.1 release blog post, in that release we have added the possibility to save CC and use those credit cards to pay your invoices.
With the 2022.07 release, we also added the possibility to edit the expiration date of a saved credit cards, or delete a saved credit card. Prior to this, you could only deactivate a credit card, and for deletion would need staff intervention.
Support for OpenStack Yoga
With the latest release we added the latest OpenStack release (Yoga) on the OpenStack Supported Versions.
Username removal preparation
In the 2022.07 release we started preparing for removing the username, which was used in the login forms.
In the following releases, the
username will be replaced with the
email address, and with the latest release, we have added the following changes:
- username field label was replaced on all login panels (enduser, staff, reseller) with email address (functionality currently remains unchanged)
- the login API will now accept an
- all users will now be able to login using either username or email address
We took this decision because the mix of username and username as email address was constantly causing confusion, and was potentially leading to inconsistent username/email state.
Besides this, the end user was not able to change his username, and this could lead to having an old email address as username and a new email address as email.
Email address as username is widely used in the industry (Google, Microsoft, etc.), and this can be a security risk (an attacker will only have to brute force the password). However, we are mitigating this risk by having a default login attempts throttle settings in Fleio (60 logins per hour, adjustable), and by having a required password complexity setting. You can also enable two factor authentication, to make the process even more secure.
After upgrading to 2022.07 release, we recommend to inform your users to start using the email address for authentication, and also inform them that only email will be accepted as username in the following releases.
We’ll talk about some of the other features in the stable release, 2022.07.1, which should be out in about one week.
In the meanwhile, see a complete list of changes in the 2022.07.0 changelog.