-
Notifications
You must be signed in to change notification settings - Fork 2
/
release-notes.txt
278 lines (189 loc) · 13.4 KB
/
release-notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
Release 0.75, 30th Apr 2024
---------------------------
Added logic to allow BitBucket upgrades to run 'restorecon' on the opensearch bin directory in order to reset SELINUX contexts, this
assumes that the SELINUX context defaults for the location has already been set (by hand or via ansible auomation etc).
This is controlled by 2 variables:
* OPENSEARCH_RESTORE_SELINUX this controls if a 'restorecon' should be attempted, 0 means no and 1 means yes, value default to 0
* OPENSEARCH_BIN_DIRECTORY, the location of the opensearch bin directory, default to "${INSTALL_DIR}/opensearch/bin"
Release 0.74, 21st Sep 2023
---------------------------
* Added logic to the bamboo startup to not set an ENDORSED_DIR if running a java version with a major number higher than 1, so
anything with a number higher than 1.8 ( as 9 is not TLS we are not covering it)
* added logic to bamboo startup when using jave 1.8 or below to honor custom ENDORSED_DIR and fallback to default if no custom
value is set
Release 0.73, 26th July 2023
----------------------------
Fixed the logic that extracts the PostgreSQL driver for standalone synchrony installs
to work with the different naming convention used for the driver in Confluuence 8.0+
Release 0.72, 15th May 2023
---------------------------
Added support for Confluence DC node discovery via "AWS", this discovers nodes by calling the EC2:DescibeInstances API and optionally
filtering those results by membership of a Security Group and/or Tags
The following config options are added to support this
* CLUSTER_CONFIG_MODE - this can be set to 'tcp' to support the current method of joining via a list of peers or 'aws' to use the new method
if not set this defaults to 'tcp'
* CLUSTER_AWS_IAM_ROLE - The name of the IAM role to be used to acces AWS
* CLUSTER_AWS_REGION - the AWS region to search for nodes
* CLUSTER_AWS_HOST_HEADER - the host header to set, this is optional and should not usually be set, defaults to "ec2.amazonaws.com"
* CLUSTER_AWS_SECURITY_GROUP_NAME - an option security group name to filter the results by
* CLUSTER_AWS_TAG_KEY - an optional AWS tag key to filter the results by, if used also set CLUSTER_AWS_TAG_VALUE
* CLUSTER_AWS_TAG_VALUE - an optional AWS tag value to filter results by, if used also set CLUSTER_AWS_TAG_KEY
Release 0.71, 6th October 2022
------------------------------
Added basic support for local Opensearch as shipped with BB >= 7.21.0
As the shipped Opensearch version has the security plugin (TLS and more) enabled by default a new avst-app config variable has been added:
* DISABLE_SEARCH_SECURITY - defaults to -1 (ignore whatever is already set and do nothing)
This new variable can be used to disable the Opensearch security plugin by setting it to 1, this adds "plugins.security.disabled: true" into
the opensearch.yml, alternativly setting it to 0 will add "plugins.security.disabled: false" to the yaml.
If the security plugin is NOT disabled them the code will check if the configired TLS cert,key and ca are present, if not it will throw a error
PLEASE NOTE: It is not recommended to disable the security plugin, instead TLS cert, key and ca files should be added to help secure the Opensearch config, the flag has been provided in order to turn off security in an emergency if access in the old (non TLS) way is required
Release 0.70, 8th Apr 2022
--------------------------
Added basic support for Amazon Linux
Release 0.69, 3rd Feb 2022
--------------------------
Added support for enabling tomcat access logging for confluence, this is principly controlled via the CONFLUENCE_ENABLE_TOMCAT_ACCESS_LOG variable, a value of
1 means that access logging should be enabled and a value of 0 means it should not.
Below are additional avst-app config variables that can be used to set various elements of the logging config, they each have a default value that is also noted:
* TOMCAT_ACCESS_LOG_CLASS - Defaults to "org.apache.catalina.valves.AccessLogValve"
* TOMCAT_ACCESS_LOG_DIRECTORY - Defaults to "logs"
* TOMCAT_ACCESS_LOG_PREFIX - Default to "conf_access_log"
* TOMCAT_ACCESS_LOG_SUFFIX - Defaults to ".log"
* TOMCAT_ACCESS_LOG_PATTERN - Defaults to "%t %{X-AUSERNAME}o %{User-Agent}i %h %m %r %b %s %D %I"
Release 0.68, 10th Jun 2021
---------------------------
Changed the way commands are run as the instance owner, previously they were run using 'su' and have now been swaped over to use 'sudo'
Release 0.67, 4th May 2021
--------------------------
Expanded the logic that handles Synchrony driver path, previously SYNCHRONY_DRIVER_PATH had to be a fully qualified path to the database driver.
The new logic now checks if the supplied path is a directory, if so it them looks for a single jar within the directory and if founds adds that file, if there are not exactly 1 file in that directory then avst-app errors out. This will allow for upgrades without needing to hard code each new jar file name.
Adding some additional exit codes to the README.MD, also updated some duplicate codes to use unique values
Release 0.66, 22nd Feb 2021
---------------------------
Added support for setting <schema-name></schema-name> in jira dbconfig.xml if the database type is postgres and a schema name is set.
This is controlled by the DB_SCHEMA_NAME avst-app.cfg.sh variable, the default value of which is nothing and results in the element not being set
In addition the logic to set "validation-query-timeout" for MySQL databases has been extended to any database type starting "mysql" instead of an exact match
for just "mysql", this allows the mysql57 database type to also set the "validation-query-timeout" element
Release 0.65, 26th Aug 2020
---------------------------
Added support for setting maxPostSize in each tomcat connector in bytes, this is controled by the following:
* MAX_POST_SIZE - deafults to 2097152
Additionally it is possible to set the value for each connector individually, the first connector will just use MAX_POST_SIZE, all
additional connectors can be set via MAX_POST_SIZE_FOR_CONNECTOR<connector number>, i.e MAX_POST_SIZE_FOR_CONNECTOR1 (second connector).
If a connector specific value is not set then that connector will fallback to the value of MAX_POST_SIZE
Release 0.64, 14th May 2020
---------------------------
Added support for Bitbucket >= 7.2.0, which ships with ElasticSearch 7.5, the service scripts need to set JAVA_HOME to support the new ES version. The location of JAVA_HOME for the service can be controlled by the below avst-app.cfg.sh variable:
* SEARCH_JAVA_HOME - defaults to /usr/java/latest
Release 0.63, 28th April 2020
-----------------------------
Modified bamboo/jira "42disable_tomcat_access_logging" logic, added the ability to skip logging management all together, this is usefull as trying to
manage the configuration (either to enable or disable) when the XML element(s) has been removed will cause the XML configuration document to be malformed.
This functionality is controlled via the SKIP_LOGGING_MANAGEMENT flag, a value of 1 means that logging will not be managed by avst-app, any other value means it will (defaults to 0)
Added support to cleanup plugin caches and the home temp directory on startup in jira and confluence.
This functionality is controlled by two new flags:
* CLEAN_PLUGIN_CACHE - This flag determines if the plugin cache folders are cleared before the application starts, a value of
1 means yes and anything else means no (defaults to 0)
* CLEAN_HOME_TEMP - This flag determines if the temp directory in home is emptied before the application starts, a value of
1 means yes and anything else means no (defaults to 0)
Release 0.62, 25th November 2019
--------------------------------
Added support to define the timeout of each tomcat connector, a global variable CONNECTOR_CONNECTION_TIMEOUT can be used to set the value for
all connectory, this defaults to 20000. It is also possible to set the value per connector via the CONNECTOR_CONNECTION_TIMEOUT_<CONNECTION_NUMBER>
i.e CONNECTOR_CONNECTION_TIMEOUT_2 variable
Release 0.61, 2nd August 2019
-----------------------------
Added basic support for Bitbucket DC, this involved:
support to set cluster config params (limited to TCP/IP discover atm) via the following variables
- CLUSTER_NAME = The name of the BB cluster
- CLUSTER_PASSWORD = The password to connect nodes to the BB cluster
- CLUSTER_PEERS = comma separated list of IP' and ports of each nodes, i.e 192.168.12.1:5701,192.168.12.2:5701
support to disable the in-build elastic search instance, this stops it being started, configured as a server
and also from being a dependent service for the main bitbucket service, this is controlled by the variable ENABLE_ELASTICSEARCH:
- 1 = enable in-built ES, as per previous functionality
- 0 = disable in-built ES, do not install ES service and do not make it a dependency of the bitbucket service
currently this flag *only* has any affect at install/upgrade time, it does not have any affect on modify operations
support to configure an external elastic search instance, the following controlled via the following parameters:
- ELASTICSEARCH_CONFIGURE_REMOTE = flag to determine if external ES is in use, values are:
- 0 = not in use, will attempt to remove any remote ES parameters from properties file
- 1 = in use, will attempt to add the any of the remote ES params that have values
- -1 = ignore, this ignores the config, leaving bitbucket.properties in whatever state its currently in
- ELASTICSEARCH_URL = URL of the remote ES instance
- ELASTICSEARCH_USER = Username to connect to the remote ES instance
- ELASTICSEARCH_PASS = Password to connect to the remote ES instance
- ELASTICSEARCH_AWS_REGION = For AWS SaaS ES instances, this identifies the AWS region they are running in
Release 0.60, 7th June 2019
---------------------------
Improved configurability of tomcat server.xml:
* Added mail based JNDI object timeout
* Made useBodyEncodingForURI and maxHttpHeaderSize configurable per connection
Added support for ElasticSearch 6.5 on Biutbucket 6 and higher
Release 0.59, 8th March 2019
----------------------------
Modified the tomcat set timeout logic to also manage the app timeout in the Jira, Confluence and Bamboo web.xml files,
if requested to do so. The following new parameters are introduced:
MANAGE_TOMCAT_AND_APP_SESSION_TIMEOUT - falg to determin if app web.xml is modified (0=no, 1=yes)
APP_SESSION_TIMEOUT - timeout for the app web.xml, if not set defaults to TOMCAT_SESSION_TIMEOUT (or current app default if not set)
Release 0.58, 29 Febuary 2019
-----------------------------
Added logic to support OpenJDK (previously threw an fatal error) but print a warning to check compatability
Release 0.57, 22 Febuary 2019
-----------------------------
Fixed logic to create mutliple resources in tomcat server.xml
Added logic to allow the setting of tomcat resource type "javax.mail.Session" as well as the default "javax.transaction.UserTransaction"
Release 0.56, 18th December 2018
--------------------------------
Removed code that sets 'synchrony.btf' value in confluence.cfg.xml for Data Center, as this was
breaking newer versions of Confluence
Release 0.55, 5st November 2018
-------------------------------
Added additional protection around accidentally deleting renamed home directory during upgrade process
Release 0.54, 1st November 2018
-------------------------------
Changed logic for pre upgrade folder renames, now if the rename target exists the code will exit
instead of deleting the rename target
Release 0.53, 25th Octoberr 2018
-------------------------------
Added Connector attributes required by the latest jira:
* relaxedPathChars
* relaxedQueryChars
Release 0.52, 29th August 2018
------------------------------
Added logic to ensure validation-query-timeout is only set in JIRA dbconfig.xml for MySQL,
previous added in 0.48 but subsequently removed by mistake
Release 0.51, 22st June 2018
----------------------------
Fixed ownership for downloaded bamboo agent jar
Release 0.50, 21st June 2018
----------------------------
Basic support for Confluence and JIRA DC
Basic OKTA plugin support for Confluence and JIRA
Release 0.49, 5th June 2018
---------------------------
Added Basic support for Synchrony DC
Added logic to ensure validation-query-timeout is only set in JIRA dbconfig.xml for MySQL
Release 0.48, 28th March 2018
-----------------------------
Added support for later versions of artifactory pro upto 5.9.3
Release 0.47, 14th March 2018
-----------------------------
Added '--no-autostart' flag to stop auto restarting of instances after upgrades
Syntax:
sudo avst-app --no-autostart <INSTANCE> upgrade <PATH_TO_TAR>
Example:
sudo avst-app --no-autostart bitbucket upgrade /tmp/atlassian-bitbucket-5.9.0.tar.gz
Release 0.46, 7th Febuary 2018
------------------------------
Fixed bug with fisheye upgrade, previously version check was not performed and therefore it
was possible to run an upgrade without setting correct version number in avst-app.cfg.sh,
causing unexpected behaviour
Release 0.45, 26th January 2018
-------------------------------
Added support for elasticsearch 5.x which is shipped in Bitbucket >= 5.7.0
Release 0.44, 25th January 2018
-------------------------------
Fixed SSO for bitbucket server, it only worked for stash previously
Release 0.43, 19th September 2017
---------------------------------
Added functionality to copy items from the old FeCru install dir into the new one, this is needed
when the FeCru install directory is also the active 'home' directory