Fleio 2022.07.1 stable was released today, 19th of July, 2022.
The latest version is marked as stable and can be used in production environment. You can read more about our release model here.
API versions per region
With the 2022.07 release, we have changed the way how the API versions for OpenStack services is retrieved, and instead of retrieving the API versions only for the default region, we are now pulling the API versions for all regions.
We changed this because in most cases, different regions may have different API versions, for the same services. In some cases, some OpenStack services might not exist at all on certain regions.
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
In the 2022.06 release blog post, we have added the possibility to save the CC details, and use those credit cards to pay your invoices.
With the latest release, we continued working on this feature, and we also added the possibility to edit the expiration date of a saved credit card, or to delete a saved credit card.
Prior to this, you could only deactivate the credit card, and for deletion, staff intervention was needed.
Support for OpenStack Yoga
With 2022.07 release, we also 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.
Keep in mind that in order to upgrade Fleio to the latest version you need to follow this guide.
Fleio 2022.07.1 includes many more improvements and bug fixes. For a full list, see the full 2022.07.1 changelog.