snowplow / iglu-server Goto Github PK

Original ticket

This change also requires the following bumps:

• iglu core to 1.0.0
• iglu client to 1.0.2
• circe to 0.13.0

It must always affect all schemas in a vendor/name group. We cannot have private schemas in the middle of a group.

E.g.

curl -i http://host/api/schemas/com.snowplowanalytics.snowplow/event -X PUT -H 'apikey: 48b267d7-ABCD-DEFG-bae4-0f002008b5ad' -d '{
  "policy": "public"
}'

• BINTRAY_SNOWPLOW_GENERIC_USER
• BINTRAY_SNOWPLOW_GENERIC_API_KEY

Its not clear for everyone what are possible options and how to use some of them.

Also, application.conf should not belong to the root of worktree.

Original ticket

Original ticket

And ensure we install the correct CA bundle into the docker container to use it with RDS https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html

Original ticket

RDBMs are too expensive while we don't use most of their benefits.

Original ticket

Docker example on master branch doesn't work as expected due to init.sql having syntax error at first line and assigning ownership of igludb to a non-existing user sp_user. I'll open a PR today to address this.

Original ticket

It points to 0.6.0-rc3

Original ticket

Original ticket

This is the current implementation when listing schemas for a vendor/namespace/model:

1. Fetches all rows from the database schemas table and loads into memory
2. Deserializes all schemas into a Schema object.
3. Filters for schemas matching the vendor name / namespace / model

A better solution is to implement an efficient getSchemasByVendorName in the Postgres class rather than using the default provided by the Storage class

Original ticket

Original ticket

It was necessary because cats-effect 1.0 would prevent the app crash on OOM. In 2.0 it should be fixed and trait is not necessary anymore.

Original ticket

We need to run setup command and insert a super API key before we can start using the server. We can improve UX of Iglu Server in docker-compose world by replicating setup command within init.sql.

Original ticket

I wrapped logging action into another IO and threw away the inner value with .as(ExitCode.Success)

Original ticket

Original ticket

All endpoints requiring authentication can't be used through Swagger UI since authentication doesn't work as expected, i.e. trying any endpoint requiring authentication in any service shows that authentication header isn't added to request after entering super api key into authentication box in Swagger UI.

Swagger UI shows a cURL command each time an endpoint is used. Copy-pasting any of them into command line and adding authentication header works as expected.

• BINTRAY_SNOWPLOW_DOCKER_USER
• BINTRAY_SNOWPLOW_DOCKER_API_KEY

POST /keygen is supposed to take a vendor prefix and a super api key to generate read/write keys for given vendor prefix.

As seen in the attached screenshot, no input field is available to provide vendor prefix.

We need github actions for

• test, scalafmt, scalacheck
• upload docker images to docker hub
• attach jar file to github release
• run snyk to monitor vulnerabilities in our dependencies.

• Travis
• DockerHub (once the image migrated from Bintray)
• Codecov
• License

User tries to upload 1-0-1 schema, where its change to compared to 1-0-0 is clearly a model-bump, not addition-bump. Iglu Server need to recognize and warn about that (TBD if it needs to always refust that)

Using Iglu Server behind a proxy prevents Swagger UI to load required assets since relative paths are used to load them.

While it is possible to bypass this issue by having tweaks in proxy configuration, it degrades UX of Iglu Server.

We should be able to plug Iglu Server behind a proxy and use it smoothly without a tweak.

Original ticket

We currently return all schemas with metadata key (if requested with ?metadata=true) which contains creation and modification dates. @mikejongbloet would like to add more properties such as owner and type (event/context) and in order to make this info generic and snowplow-independent we can come up with metaschema that validates these kind of properties. These schemas could reside independently on Iglu Server themselves.