removing ARN from S3Artifact and cleaning up artifact-guide

docs/artifact-guide.md

@@ -1,22 +1,8 @@
 # Artifact Guide
-`Sensors` supports S3 artifact repositories. To take advantage of these artifact signals, you can use this guide to get started with installing artifact services.
-
-### Prerequisites
-Up & Running kubernetes instance
+`Sensors` support S3 artifact notifications. To take advantage of these artifact signals, you can use this guide to get started with installing artifact services.
 
 ## Minio
-[Minio](https://www.minio.io/) is an distributed object storage server. 
-
-### Install
-```
-$ brew install kubernetes-helm # mac
-$ helm init
-$ helm repo add stable https://kubernetes-charts.storage.googleapis.com
-$ helm repo update
-$ helm install stable/minio --name artifacts --set service.type=LoadBalancer
-$ helm upgrade -f docs/minio-config.yaml stable/minio
-```
+[Minio](https://www.minio.io/) is an distributed object storage server. Follow the Minio [Bucket Notification Guide](https://docs.minio.io/docs/minio-bucket-notification-guide) for help with configuring your minio server to listen and monitor for bucket event notifications. Note that you will need an `Axis` supported message queue up and running as a prerequisite for configuring your notification targets (i.e. NATS, WebHooks, Kafka, etc.). 
 
-Note: When minio is installed via Helm, it uses the following hard-wired default credentials and creates a kubernetes secret with a hash of these keys. Signal specifications rely on kubernetes secrets instead of the raw keys. 
-- AccessKey: AKIAIOSFODNN7EXAMPLE
-- SecretKey: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
+### Enabling bucket notifications
+Once the Minio server is configured with a notification target and you have restarted the server to put the changes into effect, you now need to explicitely enable event notifications for a specified bucket. Enabling these notifications are out of scope of `Axis` since bucket notifications are a construct within Minio that exists at the `bucket` level. This means that if `Axis` was responsible for the lifecycle of the bucket notifications, multiple sensors on the same S3 bucket would conflict with eachother. Thus, creating, updating, and deleting the Minio bucket notifications should be delegated to a separate process with knowledge of all notification targets including those outside of the `Axis` project.

examples/s3-sensor.yaml

@@ -10,6 +10,7 @@ spec:
       artifact:
         s3:
           bucket: hello
+          event: s3:ObjectCreated:Put
           endpoint: artifacts-minio.default:9000
           insecure: true
           accessKey:
@@ -18,13 +19,6 @@ spec:
           secretKey:
             key: secretkey
             name: artifacts-minio
-          event: s3:ObjectCreated:Put
-          arn:
-            partition: minio
-            service: sqs
-            region: us-east-1
-            accountID: "1"
-            resource: nats
         stream:
           nats:
             url: nats://example-nats-cluster:4222