Releases: stackdio/stackdio
0.8.0b8
This is the eighth beta release for 0.8.0.
Fixes a few incompatible dependency versions
0.8.0b7
This is the seventh beta release for 0.8.0.
Allows resource IDs to be longer since AWS is lengthening them.
0.8.0b6
This is the sixth beta release for 0.8.0.
There was a major bug where the UI auto refresh polling would kill the server.
0.8.0b5
This is the fifth beta release for 0.8.0.
- Environments are added as a beta feature. An environment is like a stack, except that it doesn't have any hosts associated with it. It is purely for orchestration, NOT launching.
- Added support for m5 & c5 instance types
0.8.0b4
This is the fourth beta release for 0.8.0.
It fixes a single critical bug where blueprint properties were not passed on to stacks on creation.
0.8.0b3
This is the third beta release for stackd.io 0.8.0.
- Fixes a bug where blueprint properties were not saved on creation
- Adds the newest AWS regions and instance types
0.8.0b2
This is the second beta release for 0.8.0.
Bugfixes:
- Fixed slug creation issue on blueprints
- Fixed some salt warning messages
- Fixed server error when filtering on labels
- Pre-cache the health field to avoid long response times every 5 minutes
- Fixed error when adding hosts - previously would use the wrong index for the new host
- Blueprints with components not in the formula master branch can now be created
Changes:
- All properties are now stored in the database instead of on the filesystem
- We now utilize salt's gitfs to avoid having to write our own buggy git logic for cloning formulas
0.8.0b1
This is the first beta release for 0.8.0.
New features:
- You can authenticate to the API with a user token
Bugfixes:
- The blueprint export endpoint works again
- Changing labels while a stack is launching no longer deletes all the hosts from the database
0.8.0a5
This is the fifth alpha release for 0.8.0.
It implements the ability to orchestrate single components and view component statuses via the UI.
0.8.0a4
This is the fourth alpha release for 0.8.0.
It implements more aggressive caching to ensure the /api/stacks/
endpoint returns in a timely manner.