chore: release 0.14.0 (#590)

Author: VaibhavPage

CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## v0.14.0
+
++ Introducing Slack notification trigger. #576
++ Introducing OpenWhisk trigger. #585
++ TLS support for messaging queue gateways. #580
++ Support for list of event types for resource gateway. #561
++ Added label and field selectors for resource gateway. #571
++ Basic Auth for HTTP trigger. #559 
++ Namespace defined in event sources for secret retrieval is optional. #569 
+
 ## v0.13.0
 + Add AWS-SQS Cross Account Queue Monitoring #547
 + Enhanced Data Filter Comparator #544 

Makefile

@@ -17,7 +17,7 @@ override LDFLAGS += \
 #  docker image publishing options
 DOCKER_PUSH?=true
 IMAGE_NAMESPACE?=argoproj
-IMAGE_TAG?=v0.13.0
+IMAGE_TAG?=v0.14.0
 BUILD_BINARY?=true
 
 ifeq (${DOCKER_PUSH},true)

README.md

@@ -54,30 +54,11 @@ Follow these [instruction](https://argoproj.github.io/argo-events/installation/)
 
 
 ## Event Sources
-1. AMQP
-2. AWS SNS
-3. AWS SQS
-4. Cron Schedules
-5. GCP PubSub
-6. GitHub
-7. GitLab
-8. HDFS
-9. File Based Events
-10. Kafka
-11. Minio
-12. NATS
-13. MQTT
-14. K8s Resources
-15. Slack
-16. NetApp StorageGrid
-17. Webhooks
-18. Stripe
-19. NSQ
-20. Emitter
-21. Redis
-22. Azure Events Hub
+
+Argo-Events supports 20+ event sources. The complete list of event sources is available [here](https://argoproj.github.io/argo-events/concepts/event_source/).
 
 ## Who uses Argo Events?
+
 Organizations below are **officially** using Argo Events. Please send a PR with your organization name if you are using Argo Events.
 1. [BioBox Analytics](https://biobox.io)
 1. [BlackRock](https://www.blackrock.com/)
@@ -88,14 +69,17 @@ Organizations below are **officially** using Argo Events. Please send a PR with
 1. [Viaduct](https://www.viaduct.ai/)
 
 ## Community Blogs and Presentations
+
 * [Automating Research Workflows at BlackRock](https://www.youtube.com/watch?v=ZK510prml8o)
 * [Designing A Complete CI/CD Pipeline CI/CD Pipeline Using Argo Events, Workflows, and CD](https://www.slideshare.net/JulianMazzitelli/designing-a-complete-ci-cd-pipeline-using-argo-events-workflow-and-cd-products-228452500)
 * TGI Kubernetes with Joe Beda: [CloudEvents and Argo Events](https://www.youtube.com/watch?v=LQbBgQnUs_k&list=PL7bmigfV0EqQzxcNpmcdTJ9eFRPBe-iZa&index=2&t=0s)
 
 ## Contribute
+
 Read and abide by the [Argo Events Code of Conduct](https://github.com/argoproj/argo-events/blob/master/CODE_OF_CONDUCT.md).
 
 [Contributions](https://github.com/argoproj/argo-events/issues) are more than welcome, if you are interested please take a look at our [Contributing Guidelines](./CONTRIBUTING.md).
 
 ## License
+
 Apache License Version 2.0, see [LICENSE](./LICENSE)

ROADMAP.md

@@ -1,11 +1,5 @@
 # Roadmap
 
-- Microsoft Azure Blob Gateway
-- Emitter Gateway
-- NSQ Gateway
-- Redis PubSub Gateway
-- Stripe Webhook Gateway
-- Argo Workflow specific operations with argo cli as trigger
-- Support OpenFaas, Kubeless, AWS Lambda, Google Cloud Functions, IBM OpenWhisk as triggers
-- Support Twilio messages, Email and Slack messages as triggers
-- Support for HTTP, NATS, Kafka triggers
+- Custom trigger for Kubeflow, Airflow and TektonCD pipeline.
+- Read-Only UI
+- Apache Pulsar Gateway

VERSION

@@ -1 +1 @@
-v0.13.0
+v0.14.0

api/openapi-spec/swagger.json

@@ -2,7 +2,7 @@
   "swagger": "2.0",
   "info": {
     "title": "Argo",
-    "version": "v0.13.0"
+    "version": "v0.14.0"
   },
   "paths": {},
   "definitions": {

docs/assets/argo-events-top-level.png

@@ -3,6 +3,33 @@
 Event Sources are the configuration store for gateways. The configuration stored in an Event Source is used by a gateway to consume events from
 external entities like AWS SNS, SQS, GCP PubSub, Webhooks etc.
 
+
+Currently supported event sources -
+
+1. AMQP
+1. AWS SNS
+1. AWS SQS
+1. Cron Schedules
+1. GCP PubSub
+1. GitHub
+1. GitLab
+1. HDFS
+1. File Based Events
+1. Kafka
+1. Minio
+1. NATS
+1. MQTT
+1. K8s Resources
+1. Slack
+1. NetApp StorageGrid
+1. Webhooks
+1. Stripe
+1. NSQ
+1. Emitter
+1. Redis
+1. Azure Events Hub
+
+
 ## Specification
 Complete specification is available [here](https://github.com/argoproj/argo-events/blob/master/api/event-source.md).
 

docs/concepts/event_source.md

@@ -17,6 +17,7 @@ There are two components for a gateway,
 Gateway client manages the event source for the gateway.
 
 Its responsibilities are,
+
 1. Monitor and manage the event sources.
 2. Monitor and manage the subscribers.
 3. Convert the events received from the gateway server into CloudEvents.
@@ -26,6 +27,7 @@ Its responsibilities are,
 Gateway server listens to events from event sources.
 
 Its responsibilities are,
+
 1. Validate an event source.
 2. Implement the logic for consuming events from an event source.
 3. Dispatch events to gateway client.

docs/concepts/gateway.md

@@ -12,6 +12,5 @@ A Trigger is the resource/workload executed by the sensor once the event depende
 1. Kafka Messages
 1. Slack Notifications
 1. Argo Rollouts CR
-1. Custom Triggers
-
-
+1. Custom / Build Your Own Triggers
+1. Apache OpenWhisk