* destination-specification: add supportsNormalization and supportsDBT attributes
* address review comment
* missed this one
* output after gradle format
Release CDK 0.1.1. Unfortunately I can't release 0.1.0 because we previously released it while testing and I didn't realise once a package is released on PyPi, a package with the same name/version cannot be released regardless of whether it's deleted or not.
Updated:
- source-exchange-rates
- source-github-singer
- source-slack
- source-smartsheets (this is at 0.1.4 since someone published 0.1.3 but the change was not checked in)
- source-stripe
Only source-github-singer and source-smartsheets need to be updated. The rest are either not already published or have singer equivalents present.
As the title suggests.
Some intricacies around how various directories have diverged.
The HTTP templates now use integration_tests to house catalogs and config files instead of sample_files. After this PR, everything should be updated to use integration_tests for all files except config files. Config files use secrets since they often contain secrets. Anything, besides actual implementations that have yet to be updated, not following this is my mistake.
Even though it diverges from the generated templates, I've decided to leave the tutorial code and the tutorial as using sample_files for now. I think it's more straightforward than telling people to create a new secrets directory. We can change this at a later date.
Confirmed the checked in http python tutorial code works by running ./gradlew :airbyte-integrations:connectors:source-python-http-tutorial:standardSourceTestFile.
* Add primary_key noop to docs and PokeAPI connector.
* Small grammar fix in FAQ.
* Change empty string to None for noop.
Co-authored-by: Abhi Vaidyanatha <abhivaidyanatha@Abhis-MacBook-Pro.local>
Completely test the OAuth module and streams/core.py file.
Add pytest-mock as well as a convenience wrapper to run the type checker and the test together when developing.
Also configure pytest to pick up loggers at the INFO level and above, and pick up standard out for easier debugging.
Some of the script bits are unpolished - will improve them as we go along.
closes#2722
I don't love the current structure. There is a number of improvements that can be made:
JsonSchemaResolver can be refactored to have the following signature:
def __init__(schemas: Mapping[str, any], refs: Mapping[str, any])
# schemas are all json files in `schemas/`, refs are all json files in `schemas/shared/`
Then we can thoroughly test the resolving behavior in JsonSchemaResolver independently from the logic for where we actually load schemas from.
I was tempted to make this refactor now but I'd rather cover more ground with tests then revisit. I created an issue to track this: #3222
* Adding concepts docs, structure for CDK documentation
* Add more context to the CDK README
Co-authored-by: Abhi Vaidyanatha <abhivaidyanatha@Abhis-MacBook-Pro.local>
Allow us to publish CDK versions on PyPi via Github workflows.
This lets us:
- Version CDK moving forward
- Publish via Github actions to both PyPi and test PyPi for test releases.
Note, this will not work on this branch as Github only detects new workflows after they are checked into master, so I was forced to develop and test this from a fork. Browse this PR or this PR to see this command in action.
Added publishing instructions to the Release Document.
