I see there are list active version of karate available.
Our team develop tool for reporting (reportportal.io) and our users are asking for support of various versions.
As far as i see, there is no back compatibility between 0.9.2 - 0.9.3 - 0.9.4 - 0.9.5RC5
support and track integrations for each of minor versions is overhead.
Could you please updated on any roadmap, ETA and strategy for version compatibility, so we can focus on 1 certain version.
thank you in advance.
Use 0.9.5.RC5 and the develop branch in GitHub. The plan is to release 0.9.5 final within a month.
Related
I'm getting "One or more of the requested capabilities are not supported." error when trying to mount a volume from Amazon EFS on AWS FARGATE.
Edit your service and update "Platform version" to 1.4.0
You can do this in terraform by adding an optional variable platform_version to the aws_ecs_service resource
Here is the official AWS communication about the platform version 1.4.0
Here is an important quote:
The primer blog post goes into more detail about the philosophy behind why we introduced Fargate platform versions and, for example, the practical reasons why we are not tagging platform version 1.4.0 as LATEST just yet.
The primer blog post is here. Keep the focus on this "critical" point:
Starting with the introduction of this platform version (1.4.0), we will hold on moving the LATEST tag. We want to provide a runway for users that use LATEST as an additional precaution. This means that if you are deploying today using the tag LATEST to identify a Fargate platform version, the system will keep referencing platform version 1.3.0 for now (albeit, technically, the latest platform version available today is 1.4.0).
These users could either start experimenting with 1.4.0 by explicitly deploying to it or wait until we move the tag LATEST to point to platform version 1.4.0. [Updated on 6/17/2020] We plan to make this change in the May 2020 time frame We plan to make this change at some point in Q3/2020, thus giving customers [Updated on 6/17/2020] about a month a few months to test 1.4.0 before it gets tagged as LATEST. Expect a formal announcement for this change.
This is intended to give users a window of time to test 1.4.0 without being forced to use it if they use the tag LATEST. We do not anticipate disruption but we decided to be conservative.
That's why you should use, at the time of writing, version 1.4.0, instead of LATEST in order to use AWS EFS.
I am attempting to begin building an automation sequence for a client however they are only able to use Blueprism version 6.2 right now. Does anyone know of installing, coding, scheduling, or running issues with this version? Can you also link where the issue has been discussed/resolved?
Ensure they are using the latest patch level for 6.2 (which is 6.2.2) in order to ensure they do not experience issues around scheduling. Details will be available in the Release Notes for 6.2.2 on the Blue Prism portal.
I want to know what is the difference between installing HortonWorks HDP vs installing the components directly from Apache projects? One thing I can think of is that Horton works probably has the packages aligned so that the version of each component is compatible with that of the others within the suite, while getting them directly from Apache projects, I may have to handle version compatibility myself. Is that correct? Is there any other difference involved ignoring the support subscription aspect of it.
Thanks.
There are a lot of differences between "roll your own" and using a distribution. Some of the most obvious include:
All of the various components and versions have been tested and built to work together - incompatibility between versions (e.g. Hive, Hadoop, Spark, etc.) can be a painful problem to sort through on your own
Most distribution providers, including Hortonworks, will bring patches in from unstable releases into stable releases, so even for the "same" version (e.g. Hive 1.2.1) you're getting a better release than vanilla - these can include both bug fixes and "safe" feature changes
Most distribution providers, including Hortonworks, provide some flavor of centralized platform management. I'm a big fan of Ambari (the one that comes with HDP), for example - it makes configuration and monitoring significantly easier than coordinating a vanilla install
I would strongly recommend against trying to deploy vanilla, unless it's just for learning and playing. HDP community edition is free (both definitions) and a major improvement over doing it yourself. My last deployment of HDP was entirely based on the community edition.
I need to build my project with Worklight version 6.1.0.02.20141216-0421, but I didn't find it. Please who has this version ?
If you absolutely must have this specific build, you can find it here if you use Worklight Consumer Edition, or here if you use Worklight Enterprise Edition, if you are an IBM customer with a valid support entitlement.
However, if there isn't a very specific reason that you absolutely must have this specific build, I strongly agree with Idan's answer that you should use the most recent iFix build available on IBM Fix Central. As of right now, the latest build contains fixes for 93 separate APARs that are not contained in the build you are asking about (from more than 2 years ago).
That is an extremely old build and unless this build was an official iFix release - it will no longer exist. So, if you are an IBM customer you can look for this build number in the IBM Fix Central website.
Note however that you should always use the latest available iFix release... and not a build from more than two years ago, especially for production. If you will request official support, you will be told to use the latest build.
We have a requirement to connect SAP ERP. As per Mule documentation, to connect SAP( Jco jars) it says 3.0.11 ( Latest) is not supported by the connector.
[http://www.mulesoft.org/documentation/display/current/SAP+Connector][1]
We have reached SAP - they says like only Latest version ( 3.0.11) should be downloaded from Marker place.They were not supporting the SAP old version jars since latest is released( with bug fixed) .
Please suggest, how do we get older version of jars ( 3.0.9 or 3.0.6). It will be very helpful. We are looking for options.
Thanks in advance.
SAP do not release older versions of the SAPJCO or SAPIDOC libraries as the latest versions are fully backward compatible.
The difference between 3.0.9 and 3.0.11 are very minor bug fixes, so its surprising to hear that 3.0.11 does not work. MuleSoft should liaise directly with SAP as they are an SAP Certified Integration Partner and their software should always run on the latest versions of the various SAP connectors.
As a certified partner MuleSoft will be abundantly aware that customers only have access to the most recent versions of the SAPJCO/IDOC libraries, and that SAP do not release older versions.
You would also think that MuleSoft would have access to older versions of the libraries from engagements with existing/previous SAP customers.
I would advise you to go back to MuleSoft and have them speak directly with SAP. This is not a problem for the customer.