Upgrading npm dependencies with ciritical vulnerabililities (#103)

* Upgrading two npm packages which contained critical vulnerabilities.

* Upgrading webpack. 

* Setting ajv-keywords and ajv versions for version resolution. 

* Adding required webpack-cli to dependencies as its required by the latest version of webpack. 

* Pinning node version to be the latest LTS. 
2 files changed
tree: 6629101423cb388c84f0bd52067a6eea9e7036e3
  1. .auroraversion
  2. .bowerrc
  3. .gitattributes
  4. .github/
  5. .gitignore
  6. .isort.cfg
  7. .reviewboardrc
  8. 3rdparty/
  9. CHANGELOG
  10. CONTRIBUTING.md
  11. KEYS
  12. LICENSE
  13. NOTICE
  14. README.md
  15. RELEASE-NOTES.md
  16. Vagrantfile
  17. api/
  18. build-support/
  19. build.gradle
  20. buildSrc/
  21. commons/
  22. config/
  23. docs/
  24. examples/
  25. gradle/
  26. gradlew
  27. pants
  28. pants.ini
  29. rbt
  30. settings.gradle
  31. src/
  32. ui/
README.md

Aurora Logo

Build Status

Apache Aurora lets you use an Apache Mesos cluster as a private cloud. It supports running long-running services, cron jobs, and ad-hoc jobs. Aurora aims to make it extremely quick and easy to take a built application and run it on machines in a cluster, with an emphasis on reliability. It provides basic operations to manage services running in a cluster, such as rolling upgrades.

To very concisely describe Aurora, it is like a distributed monit or distributed supervisord that you can instruct to do things like run 100 of these, somewhere, forever.

Features

Aurora is built for users and operators.

  • User-facing Features:

  • Under the hood, to help you rest easy:

    • Preemption: important services can ‘steal’ resources when they need it
    • High-availability: resists machine failures and disk failures
    • Scalable: proven to work in data center-sized clusters, with hundreds of users and thousands of jobs
    • Instrumented: a wealth of information makes it easy to monitor and debug

When and when not to use Aurora

Aurora can take over for most uses of software like monit and chef. Aurora can manage applications, while these tools are still useful to manage Aurora and Mesos themselves.

However, if you have very specific scheduling requirements, or are building a system that looks like a scheduler itself, you may want to explore developing your own framework.

Companies using Aurora

Are you using Aurora too? Let us know, or submit a patch to join the list!

Getting Help

If you have questions that aren‘t answered in our documentation, you can reach out to one of our mailing lists. We’re also often available in Slack: #aurora on mesos.slack.com. Invites to our slack channel may be requested via mesos-slackin.herokuapp.com

You can also file bugs/issues in our Github repo.

License

Except as otherwise noted this software is licensed under the Apache License, Version 2.0

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.