8000 Tags · A-SunsetMkt-Forks/diffgram · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Tags: A-SunsetMkt-Forks/diffgram

Tags

1.0.1

Toggle 1.0.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
DAD-276 Fix Label Dict Endpoint to Include Schema Concept (diffgram#879)

* fix: add schema_id support to endpoint

* fix: get labels from schema

* fix: add session

Co-authored-by: Pablo <pjestradac@gmail.com>

1.0.0

Toggle 1.0.0's commit message
fix: alembic action template, old bindings removal

0.16.0

Toggle 0.16.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request diffgram#829 from diffgram/DAD-66-dip-2-ui-for-aud…

…io-annotation

Audio interface V1

0.15.0

Toggle 0.15.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
add minio support (diffgram#857)

* add minio support

* Remove print DIFFGRAM_MINIO_ENDPOINT_URL

* Minio Only Allow Expiry time is less than 7 days (value in seconds).

* add quickstart without config in docker

* Add Export UI support for minio

* Add input searchbar support for minio

* Refactor

1) generic None config instead of duplication
2) Add get_client() We use the client in multiple places, eg. in the S3 connector. I think we should keep trying to abstract that. For example when we add more IAM / SAS things it will be helpful to have it in one place.  A directional step.

* Wordsmith

* Fix filename on windows type machines

relevant if using minio as local storage for example
fixes `An error occurred (XMinioInvalidObjectName) when calling the PutObject operation: Object name contains unsupported characters.`

* Add Export UI support for minio

* Add input searchbar support for minio

* Refactor

1) generic None config instead of duplication
2) Add get_client() We use the client in multiple places, eg. in the S3 connector. I think we should keep trying to abstract that. For example when we add more IAM / SAS things it will be helpful to have it in one place.  A directional step.

* Wordsmith

* Fix filename on windows type machines

relevant if using minio as local storage for example
fixes `An error occurred (XMinioInvalidObjectName) when calling the PutObject operation: Object name contains unsupported characters.`

* Fix DIFFGRAM_MINIO_DISABLED_SSL_VERIFY settings loading use env_adapter.bool

* Delete install_local_without_config.py

Also copied to https://gist.github.com/anthony-sarkis/f339ec2668321a93d4b08b19c3c0d572 for easy reference

* Update settings.py

* Revert "add quickstart without config in docker"

This reverts commit d637d2f.

* Update kubernetes_diffgram_enterprise_deploy.yaml

* Update kubernetes_diffgram_enterprise_deploy.yaml

Co-authored-by: Anthony Sarkis <18080164+anthony-sarkis@users.noreply.github.com>

0.14.5

Toggle 0.14.5's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Refactor signed URL generation into one place (diffgram#858)

* Add generic for regen determination

Context that each file type usually has slightly different specific conventions, but we can still generalize the bulk of it in one place.

This is still very brittle in some ways, but it solves the immediate need of being able to use the rest across all types

And when we build out more on the IAM per file side, this will be a launch point potentially to generating this URL. And/or an alternative instead of caching for convenience for example)

* add standard regen + regen check in serialize

Without regen check in serialize whenever the URLs expired there would be issues

* Add standard regen 2 places

* Add standard regen and add serialize

if it doesn't have the regen potential on serialize then can get into odd cases

* add standard regen, remove old method

1) source control method was old / out of place, replace it
2) there's the option to have a different expiry built in determine_if_should_regenerate_url()  but it seemed to add complexity with unclear benefits for this case. If there's a reason to have those tracked separately then would just need to pass it and handle edge cases
remove `keyframe` was unused

* remove old comment and move to standard regen

old comment was moved here for keeping https://docs.google.com/document/d/1P2FrVEN74ZZ3w-_8ag1LzXTOCz1ez8xxwOvocXR4SKA/edit

* handle edge cases

usually `url_signed_expiry` is always an int. but it seems like certain cases it somehow has ended up as something odd so just doing this for now

* Align with new regen, improve resue

Not clear why we weren't reusing the existing serialize_with_type(),
and then adding the key.
Much better to reuse if we can, and can still modify keys as needed eg with instance list

* Tiny assumptions fix

* re add guards

* add support for SIGNED_URL_CACHE settings

0.14.4

Toggle 0.14.4's commit message
Migration Refresh timestamp

0.14.3

Toggle 0.14.3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix: export generation, use user making the request instead of project (

diffgram#838)

Co-authored-by: Pablo <pjestradac@gmail.com>

0.14.2

Toggle 0.14.2's commit message
max_allowed_instances is allowed to be None

0.14.1

Toggle 0.14.1's commit message
fix: tag compose

0.14.0

Toggle 0.14.0's commit message
fix: tests export geofiles

0