Skip to content

Commit a9413ba

Browse files
committed
feat: update dependencies and tda data access
implement ENG-4118
1 parent 5d33523 commit a9413ba

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

52 files changed

+340
-4013
lines changed

.github/workflows/tests.yaml

-10
Original file line numberDiff line numberDiff line change
@@ -40,23 +40,13 @@ env:
4040
CUSTOMER_ID: ${{ secrets.CUSTOMER_ID }}
4141
CUSTOMER_ID2: ${{ secrets.CUSTOMER_ID2 }}
4242
APP_SPACE_ID: ${{ secrets.APP_SPACE_ID }}
43-
ISSUER_ID: ${{ secrets.ISSUER_ID }}
44-
TENANT_ID: ${{ secrets.TENANT_ID }}
45-
TENANT_NAME: ${{ secrets.TENANT_NAME }}
4643
APPLICATION_ID: ${{ secrets.APPLICATION_ID }}
4744
APPLICATION_NAME: ${{ secrets.APPLICATION_NAME }}
4845
APPLICATION_AGENT_ID: ${{ secrets.APPLICATION_AGENT_ID }}
4946
APPLICATION_AGENT_NAME: ${{ secrets.APPLICATION_AGENT_NAME }}
5047
APPLICATION_AGENT_CREDENTIAL_ID: ${{ secrets.APPLICATION_AGENT_CREDENTIAL_ID }}
5148
SERVICE_ACCOUNT_CREDENTIAL_ID: ${{ secrets.SERVICE_ACCOUNT_CREDENTIAL_ID }}
52-
EMAIL_SERVICE_CONFIG_NODE: ${{ secrets.EMAIL_SERVICE_CONFIG_NODE }}
53-
AUTH_FLOW_CONFIG_NODE: ${{ secrets.AUTH_FLOW_CONFIG_NODE }}
54-
OAUTH2_CLIENT_CONFIG_NODE: ${{ secrets.OAUTH2_CLIENT_CONFIG_NODE }}
55-
WEBAUTHN_PROVIDER_CONFIG_NODE: ${{ secrets.WEBAUTHN_PROVIDER_CONFIG_NODE }}
56-
READID_PROVIDER_CONFIG_NODE: ${{ secrets.READID_PROVIDER_CONFIG_NODE }}
5749
AUTHZ_POLICY_CONFIG_NODE: ${{ secrets.AUTHZ_POLICY_CONFIG_NODE }}
58-
OAUTH2_PROVIDER: ${{ secrets.OAUTH2_PROVIDER }}
59-
OAUTH2_APPLICATION: ${{ secrets.OAUTH2_APPLICATION }}
6050
CONSENT_CONFIG_NODE: ${{ secrets.CONSENT_CONFIG_NODE }}
6151
PASSWORD: ${{ secrets.PASSWORD }}
6252
NEW_PASSWORD: ${{ secrets.NEW_PASSWORD }}

Pipfile.lock

+207-201
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

README.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
This project serves as a Software Development Kit for developers of Indykite applications.
44
The Python SDK enables you to easily integrate the IndyKite platform gRPC APIs into your Python application.
5-
https://console.indykite.id/
5+
https://console2.indykite.id/
66
https://www.indykite.com/
77

88
[![codecov](https://codecov.io/gh/indykite/indykite-sdk-python/branch/master/graph/badge.svg)](https://codecov.io/gh/indykite/indykite-sdk-python)
@@ -14,13 +14,13 @@ https://www.indykite.com/
1414
## Installation
1515

1616
add to pipfile [packages]:
17-
indykite-sdk-python = {ref = "v1.39.0", git = "https://github.com/indykite/indykite-sdk-python"}
17+
indykite-sdk-python = {ref = "v1.47.0", git = "https://github.com/indykite/indykite-sdk-python"}
1818

1919

2020
## Used terminology
2121
To do anything at all in the IndyKite platform, you must first create an
22-
Organization (Customer) in the Hub (https://console.indykite.id/) — the Web interface used to interact with and do tasks in the IndyKite platform
23-
and get your credentials (https://docs.indykite.com/docs/get-started/initial-setup).
22+
Organization (Customer) in the Hub (https://console2.indykite.id/) — the Web interface used to interact with and do tasks in the IndyKite platform
23+
and get your credentials (https://docs.indykite.com/docs/get-started).
2424

2525
Once you have created a Customer, a service account, and you have your service account credentials,
2626
you can set up the SDK.
@@ -42,7 +42,7 @@ you can set up the SDK.
4242
:one: **Service account credentials**
4343

4444
You need to have a Service Account credentials json file to be able to use the IndyKite Python SDK. You can get it from the
45-
IndyKite hub: https://console.indykite.id/.
45+
IndyKite hub: https://console2.indykite.id/.
4646

4747
#### Config
4848
To manage its spaces, among other things, the **owner** of the relevant customer creates a **service account**.
@@ -114,7 +114,7 @@ You should use an absolute path for the file.
114114
:two: **AppAgent Credentials**
115115
116116
You will also need to have an Application Agent credentials json file to be able to use the other services like IKG (ingestion) and KBAC (authorization).
117-
You can get it from the IndyKite hub (https://console.indykite.id/) or using the SDK.
117+
You can get it from the IndyKite hub (https://console2.indykite.id/) or using the SDK.
118118
119119
Example configuration file:
120120

indykite_sdk/indykite/config/v1beta1/model_pb2.py

+22-22
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

indykite_sdk/indykite/events/__init__.py

Whitespace-only changes.

indykite_sdk/indykite/events/v1beta1/__init__.py

Whitespace-only changes.

indykite_sdk/indykite/events/v1beta1/events_pb2.py

-114
This file was deleted.

indykite_sdk/indykite/events/v1beta1/events_pb2_grpc.py

-4
This file was deleted.

indykite_sdk/indykite/identity/__init__.py

Whitespace-only changes.

indykite_sdk/indykite/identity/v1beta1/__init__.py

Whitespace-only changes.

indykite_sdk/indykite/identity/v1beta1/attributes_pb2.py

-76
This file was deleted.

indykite_sdk/indykite/identity/v1beta1/attributes_pb2_grpc.py

-4
This file was deleted.

indykite_sdk/indykite/identity/v1beta1/authenteq_pb2.py

-37
This file was deleted.

indykite_sdk/indykite/identity/v1beta1/authenteq_pb2_grpc.py

-4
This file was deleted.

0 commit comments

Comments
 (0)