Skip to content

Commit a700710

Browse files
author
Tobias Fuhrimann
committed
Merge branch 'master' of github.com:swisscom/docs-appcloud-devguide
2 parents d19e710 + e92adf6 commit a700710

File tree

1 file changed

+273
-0
lines changed

1 file changed

+273
-0
lines changed

release-notes.html.md.erb

+273
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,277 @@ title: APC Release Notes
44

55
<strong><%= modified_date %></strong>
66

7+
## <a id='6.3.0'></a> 6.3.0
8+
9+
Release date: 01.5.2017
10+
11+
### Cloud Foundry Core
12+
13+
Cloud Foundry version V257 ([release notes](https://github.com/cloudfoundry/cf-release/releases/tag/v257)) with Diego version 1.12.0 ([release notes](https://github.com/cloudfoundry/diego-release/releases/tag/v1.12.0)).
14+
15+
## <a id='6.2.0'></a> 6.2.0
16+
17+
Release date: 20.4.2017
18+
19+
### Billing and Portal
20+
21+
#### More flexible buildpack management
22+
23+
In virtual private environments it is desirable to allow certain users to manage buildpacks without giving them superuser permissions. Hence, we have introduced a new role buildpack_admin which can be assigned to any user and allows them to update non-system buildpacks.
24+
25+
#### API for technical user creation
26+
27+
We have added an option to enable arbitrary users to create technical users for use in tooling such as a CI/CD pipeline. Technical users are currently created at space level and are deleted when they are no longer associated with any space.
28+
29+
#### Enable credit card update in status "cancellation pending"
30+
31+
Until now users did not have permission to update the credit card information when their account was in status "cancellation pending". In particular, this led to the situation, that if an account could not be cancelled due to an invalid credit card (e.g. due to expiry), the user could update the credit card to rectify the situation. This has now been corrected.
32+
33+
#### Improved user invitation and notifications
34+
35+
We have made the UI for inviting users to orgs and spaces easier to understand. Furthermore we have improved the email messages which users receive when they are invited.
36+
37+
#### Improved user view for support users
38+
39+
Inactive users are often irrelevant when looking up users in support scenarios. We have added the option to filter out inactive users from the user list for support users.
40+
41+
#### UI improvements and fixes
42+
43+
We have provided fixes for a number of UI issues.
44+
45+
#### API improvements and fixes
46+
47+
We have provided a fix for an API issue.
48+
49+
### Cloud Foundry Core
50+
51+
Cloud Foundry version V254 ([release notes](https://github.com/cloudfoundry/cf-release/releases/tag/v254)) with Diego version 1.10.1 ([release notes](https://github.com/cloudfoundry/diego-release/releases/tag/v1.10.1)).
52+
53+
## <a id='6.1.0'></a> 6.1.0
54+
55+
Release date: 16.3.2017
56+
57+
### Billing and Portal
58+
59+
#### Connectivity as a Service: zone assignment made optional
60+
61+
Until now, security group requests could only be created in spaces belonging to orgs which have a security zone assigned. We have now removed this restriction to enable users to be more flexible with respect to point in time at which they define the zone assignment.
62+
63+
#### Improved info boxes in Developer Console
64+
65+
On many screens of the Developer Console we use info boxes to guide the user with respect to options and restrictions. More experienced users have expressed the wish to remove these info boxes. Hence, we have added an option to close individual boxes persistently and to reset the state of the UI to make all boxes appear again.
66+
67+
#### Improved UI for support users
68+
69+
As our user base and the number of instances of our cloud grows, the need for support functionality increases. We have added pagination of the list of all users in the system, available to support users. Furthermore, we have enabled support users to search users by name in addition to the username and the email address.
70+
71+
#### Improved scaling limit for apps in Developer Console
72+
73+
Until now, scaling an app's memory in the Developer Console was limited to a hardcoded value of 2GB. We have removed this unnecessary restriction and instead have linked the memory scaling limit of apps to the instance_memory_limit value of the organisation quota.
74+
75+
#### Show service events in Developer Console
76+
77+
So far, only the app detail view of the Developer Console featured an events tab. We have now also added an events tab to the service details.
78+
79+
#### Improved validation of fully qualified domain names for SSL certificates
80+
81+
Our F5-based entry server currently only allows CSR generation for fully qualified domain names with up to 63 octets. For longer names the generation process fails and causes the corresponding certificate request to fail intransparently. To make this restriction more transparent, we have added a validation to our API to disallow longer FQDNs.
82+
83+
#### Custom service parameters during service creation
84+
85+
We have prepared the service creation wizard for services which need to collect custom parameters during the creation step.
86+
87+
#### Make data loading in UI more flexible
88+
89+
We have improved the way data from the backend is propagated through the component hierarchy in our UI.
90+
91+
#### UI improvements and fixes
92+
93+
We have provided fixes for a number for UI issues.
94+
95+
## <a id='6.0.0'></a> 6.0.0
96+
97+
Release date: 16.3.2017 (deployed with 6.1.0)
98+
99+
### Cloud Foundry Core
100+
101+
Cloud Foundry version V251 ([release notes](https://github.com/cloudfoundry/cf-release/releases/tag/v251)) with Diego version 1.5.4 ([release notes](https://github.com/cloudfoundry/diego-release/releases/tag/v1.5.4)).
102+
With this Cloud Foundry version the minimum required cf-cli version is v6.22.2.
103+
104+
## <a id='5.7.0'></a> 5.7.0
105+
106+
Release date: 6.3.2017
107+
108+
### Billing and Portal
109+
110+
#### Connectivity as a Service: added UI support for additional protocols
111+
112+
Until now, security group requests and default groups supported only the protocols 'tcp' and 'udp'. We have now extended support for 'icmp' and the option 'all' to the UI.
113+
114+
#### Improved email notifications
115+
116+
Invitation emails for spaces, organizations and billing accounts were confusing when the targeted user was already known to the inviter as invitations to new entities were notified in the same way as role changes. We have changed this behaviour to distinguish between new roles and changed roles.
117+
118+
#### Support for long invoice lists
119+
120+
With every month of operation, the list of invoices in the account screen of each account becomes longer. We have implemented infinite scrolling to avoid loading all invoices in the UI when the list is too long.
121+
122+
#### Improved user search for support users
123+
124+
When support users are looking for a particular user, they can now use first and last names in addition to the username and the email address.
125+
126+
#### More robust automatic renewal process for ssl certificates
127+
128+
In some cases the authentication callback from Let's Encrypt for an automatic certificate renewal reaches our cloud too late and the corresponding renewal process becomes stuck, requiring a manual intervention. We have increased the amount of time for which we wait for this callback.
129+
130+
#### UI improvements and fixes
131+
132+
We have provided fixes for a number of UI issues.
133+
134+
#### API improvements and fixes
135+
136+
We have provided fixes for a number of API issues.
137+
138+
## <a id='5.6.0'></a> 5.6.0
139+
140+
Release date: 21.2.2017
141+
142+
### Billing and Portal
143+
144+
#### Improved asynchronous job processing (Part II)
145+
146+
We have analysed our processing model for asynchronous jobs and have identified a number of improvements which will lead to a significant decrease in regular maintenance work. This second improvement addresses an issue which caused asynchronous jobs to be executed out of sequence in our clustered environment.
147+
148+
#### Connectivity as a Service: added API support for additional protocols
149+
150+
Until now, security group requests and default groups supported only the protocols 'tcp' and 'udp'. We have now added support for 'icmp' and the option 'all'.
151+
152+
#### UI improvements and fixes
153+
154+
We have provided fixes for a number of UI issues.
155+
156+
#### API improvements and fixes
157+
158+
We have provided fixes for a number of API issues.
159+
160+
## <a id='5.5.0'></a> 5.5.0
161+
162+
Release date: 31.1.2017
163+
164+
### Billing and Portal
165+
166+
#### UI updated to new Swisscom SDX styling
167+
168+
We have adapted our CSS stylesheet to reflect the most important style changes of SDX, the new Swisscom design guideline for web applications.
169+
170+
#### UI log view switched from Loggregator to Doppler
171+
172+
To prepare for upcoming releases which will upgrade the version of Cloud Foundry we have switched our log view from Loggregator to Doppler, as Loggregator will be deprecated in newer versions of Cloud Foundry.
173+
174+
#### UI consistency improvements
175+
176+
We are constantly striving to streamline our usabilty and improve the consistency of our UI.
177+
178+
#### Improved asynchronous job processing (Part I)
179+
180+
We have analysed our processing model for asynchronous jobs and have identified a number of improvements which will lead to a significant decrease in regular maintenance work. The first improvement addresses a concurrency issue when scheduling jobs in our clustered environment.
181+
182+
#### Fixed issue with deletion of local users
183+
184+
When local users are deleted, they are only deactivated in UAA to guarantee a minimal audit trace. This fix ensures that the origin of such users is correctly recorded.
185+
186+
#### UI improvements and fixes
187+
188+
We have provided fixes for a number of UI issues.
189+
190+
#### API improvements and fixes
191+
192+
We have provided fixes for a number of API issues.
193+
194+
## <a id='5.4.0'></a> 5.4.0
195+
196+
Release date: 18.1.2017
197+
198+
### Billing and Portal
199+
200+
#### Performance improvements
201+
202+
We have made further significant steps in our campaign to improve the performance of the Developer Console and the API. We were able to optimize the way in which permissions are loaded and checked. Furthermore, we were able to speed up the loading of service plans and of the list of organizations.
203+
204+
#### Multicloud preparations
205+
206+
We have prepared the way our components are deployed to the context of multicloud. These improvements are not directly noticeable to the end-user but they constitute a significant step towards making our entire cloud solution even more reliable.
207+
208+
#### Billing improvements
209+
210+
We have made several minor improvements in the area of billing and pricing. In particular, estimated prices are now displayed with higher precision in the portal. In addition, we have made further improvements in the way our API component communicates with the billing component.
211+
212+
#### Connectivity as a Service: improvements
213+
214+
We are constantly improving the Connectivity as a Service features. In particular, we have improved the search function on connectivity requests for security officers.
215+
216+
#### Routes services support in Developer Console
217+
218+
We have taken a further step towards integrating the concept of route services in the Developer Console by enabling the user to edit route services.
219+
220+
#### UI consistency improvements
221+
222+
We are constantly striving to streamline our usabilty and improve the consistency of our UI.
223+
224+
#### SSL self service improvements
225+
226+
We have made further improvements of our SSL self-service feature. In particular, we give the user an option to retry certificate creation in certain error cases.
227+
228+
#### UI improvements and fixes
229+
230+
We have provided fixes for a number of UI issues.
231+
232+
## <a id='5.3.0'></a> 5.3.0
233+
234+
Release date: 9.1.17
235+
236+
### Billing and Portal
237+
238+
#### Improved account status transitions
239+
240+
Following a detailed analysis we were able to greatly simplify the way our API component communicates with the billing component for determining the status of a billing account. In particular, we were able to entirely eliminate the need for calls from the billing component back to the API component. These improvements are not directly noticeable to the end-user but they are making our components more stable and are eliminating a substantial amount of configuration and maintenance overhead.
241+
242+
#### Prepared interactive service provisioning
243+
244+
We have added the option for a service to include a service-specific dashboard which can be used to configure the service at the time of provisioning or during its operation.
245+
246+
#### Connectivity as a Service: improvements
247+
248+
We are constantly improving the Connectivity as a Service fetaures, as our experience with these features broadens. In particular, we have added a detail view for connectivity requests.
249+
250+
#### Display routes services in Developer Console
251+
252+
We have taken a first step to integrate the concept of route services in the Developer Console by displaying information about them in the service tiles and service details.
253+
254+
#### Fixed an XSS vulnerability in Developer Console
255+
256+
We discovered that error messages pointing to already existing names of orgs, spaces, services and apps were not properly sanitized and hence vulnerable to XSS attacks in the entity name. This vulnerability is now fixed.
257+
258+
#### Performance improvements
259+
260+
We have started a new campaign to further improve loading times in the Developer Console by maximizing parallel asynchronous data loading. We were already able to improve loading of space details, of the navigation tree and of permission in general. More improvements will follow in the next release.
261+
262+
#### UI consistency improvements
263+
264+
We are constantly striving to streamline our usabilty and improve the consistency of our UI.
265+
266+
#### UI improvements and fixes
267+
268+
We have provided fixes for a number of UI issues as well as various small improvements.
269+
270+
#### API improvements and fixes
271+
272+
We have provided fixes for a number of API issues as well as various small improvements. In particular, we fixed a bug which led to problems when some locally managed users were deleted.
273+
7274
## <a id='5.2.0'></a> 5.2.0
8275

276+
Release date: 6.12.2016
277+
9278
### Cloud Foundry Core
10279

11280
Cloud Foundry version V247 ([release notes](https://github.com/cloudfoundry/cf-release/releases/tag/v247)) with Diego version 1.0.0 ([release notes](https://github.com/cloudfoundry/diego-release/releases/tag/v1.0.0)).
@@ -46,6 +315,8 @@ We have provided fixes for a number of API issues as well as various small impro
46315

47316
## <a id='5.1.0'></a> 5.1.0
48317

318+
Release date: 16.11.2016
319+
49320
### Cloud Foundry Core
50321

51322
- Cloud Foundry version V246 ([release notes](https://github.com/cloudfoundry/cf-release/releases/tag/v246)) with Diego version 0.1488.0 ([release notes](https://github.com/cloudfoundry/diego-release/releases/tag/v0.1488.0)).
@@ -67,6 +338,8 @@ We have provided fixes for the following four mostly technical API issues.
67338

68339
## <a id='5.0.0'></a> 5.0.0
69340

341+
Release date: 27.10.2016
342+
70343
### Cloud Foundry Core
71344

72345
Cloud Foundry version V245 ([release notes](https://github.com/cloudfoundry/cf-release/releases/tag/v245)) with Diego version 0.1487.0 ([release notes](https://github.com/cloudfoundry/diego-release/releases/tag/v0.1487.0)).

0 commit comments

Comments
 (0)