Releases: Worklytics/psoxy
Releases Β· Worklytics/psoxy
v0.4.13
Features
- use refresh endpoint envvar #269
- add azure-ad to msft example #266
- yaml config values all from worklytics-connector-specs module #268
- add arch diagrams, nicer tables of source prereqs to docs #272
- update slack docs #277
- some tests of Google credential auth (used for Google Workspace sources) #278
Fixes
- docs and TODO files fixes #271
- clarify permissions in docs #270
- fix API Gateway example #273
- improve zoom rules #275
- test tool fixes #274
- relax az provider version constraints #281
Full Changelog: v0.4.12...v0.4.13
v0.4.12
v0.4.11
Features
- support for encrypting ssm params with AWS KMS keys #241
- test tool health check #245
- testing tool support for API Gateway #248
- msft apps with federation #242
- filter by json schema #238
- outlook-mail, cal sanitized examples #244
- avoid setting ENV vars for config paths if default values #239
Improvements
- trouble shooting and doc improvements #240
- improve gcp connector todos #243
- more defensive header handling #246
- troubleshooting docs #217
- update npm dependencies #247
Full Changelog: v0.4.10...v0.4.11
v0.4.10
What's Changed
- google projects in examples #229
- expose metadata from config service #232
- persist
refresh_token
if changed; randomize proactiveaccess_token
refreshes to avoid race cases #231 - avoid caching accessTokens in process memory #230
- invert semantics of
noRefreshNeeded
method, give clearer name, avoid two return #234 - improve tf extensibility #235
- fix ssm namespace support; add support in terraform examples #233
- deep link todos to Worklytics #236
- generate simpler bash test script, to facilitate rapid integration tests #237
Full Changelog: v0.4.9...v0.4.10
v0.4.9
Features
- vault support - alpha #210
- GCP update for Asana, Dropbox and bulk #211
- GCP: Psoxy logs and Psoxy "bulk" test tools #213
- document broken jdk, give some downgrade advice #216
- doc improvements #218
- memory as parameter #220
- bulk connection instructions #222
- include instructions re Google Workspace Service Account setup #221
- avoid lots of logs, java compliation #226
- Pseudonym implementation as a config setting #225
Fixes
- Fix default values for
environment_name
#212 - Add missing param for Asana rules #214
- fix google workspace examples #215
- Update test commands in
local_file
resource #204 - explicitly force sha1, as some openssl default to sha256 #219
Full Changelog: v0.4.8...v0.4.9
v0.4.8
What's Changed
- AWS-google-workspace example as module #191
- reversibly encode asana user gids #190
- modular examples, simplifying usage/upgrades
- Using env variables #198
- dropbox support + logging fixes #195
- support restricting HTTP method in rules #194
- logging #199
- lookup table builder use case, with examples #197
- global param read shouldn't be needed #201
- Updated Asana rules #196
- npm: bulk + logs #202
- Fix environment variables resolution #205
- trouble shooting #206
- trouble shooting tools #207
- CLI call logging fixes #208
Features:
- tools to support for testing
bulk
cases, quick review of logs - lookup table builder examples
- restricting HTTP methods in rules
Upgrade notes:
- examples have been refactored; old ones should work, but recommend moving to modularized ones going forward
- AWS IAM roles/policies have been renamed; you may see many deletes/creates, but should be no
effective changes - an unneeded SSM Parameter AWS policy has been removed; it is superceded by more granular policies
created in v0.4.6
Full Changelog: v0.4.7...v0.4.8
v0.4.7
Features
- better msft examples #175
- support rules to limit query params #179
- refactor secrets management into distinct terraform modules #185
Fixes
- redact a few more group fields #174
- update zoom documentation #178
- outlook mailbox settings rules #180
- restricting endpoints to pseudonyms #177
- GCP troubleshooting #176
- defaults for psoxy_instance_id #181
- add env variables from specs #182
- fix zoom rules #183
- aws entity names #186
- testing tool AWS fixes #184
- connector variables #187
- add asana endpoints/rules asana #188
Upgrade Guide
- asana rules are NOT backwards compatible. if you've previously connected asana via psoxy to Worklytics, you must either 1) set the prior rules as custom rules, or 2) contact worklytics to wipe your existing asana data and re-connect.
- secret management has been refactored; you may see indications of some secrets being moved, or
even destroyed and recreated. If you plan shows SALT or ENCRYPTION_KEY as being destroyed,
DO NOT apply the plan and contact Worklytics support for assistance.
Full Changelog: v0.4.6...v0.4.7
v0.4.6
v0.4.5
Major Features
- Store and share short-lived OAuth access token across AWS lambda instances for Zoom Server-to-server OAuth connector. #165
- AWS secured parameters. New set of policies limiting access to just the subset of parameters used by the lambda function.
What's Changed
- Improved MSFT AWS examples #155
- New node js based testing tool #146 #147 #148
- Support for Dropbox connector #149 #150
- CSV import: column renaming, better examples #156 #157 #158
- Terraform scripts misc improvements #159
- Asana connector example calls #160
- Rules fixes and improvements #161 #162 #164
- AWS MSFT parameters as env vars #166
Full Changelog: v0.4.4...v0.4.5
Upgrade Guide:
- ensure your
terraform
version is at least1.3.x
(terraform --version
); if not, upgrade it - replace all references to your current version (eg,
0.4.4
) with0.4.5
terraform init --upgrade
β get latest AWS provider- if you haven't explicitly defined
psoxy_base_dir
in yourterrafom.tfvars
file, you'll need to. This is no longer optional, as defaults didn't really work for anyone.
NOTE:
- aws + msft : the
CLIENT_ID
/REFRESH_ENDPOINT
values for MSFT connectors were previously stored as AWS SSM parameters; they are now stored as env vars on the lambda itself; 'destroy' of the SSM versions of these is to be expected, as well as an update to each lambda to add the values there
Warning
This release was originally published 29 Sept 2022, but not all references to release version were updated properly to point to the release rather than the release candidate. Due to potential of this to break builds, we updated the release with the correct references on 4 Oct 2022.
If you have used this release in your Terraform configurations within these dates, you should try terraform get -update
at the root of your configuration to ensure you have the latest version of the release.