706 Adds SaaS connection type to SaaS yaml config

[eastandwestwind]

Purpose

Adds SaaS connection type to SaaS yaml config

Changes

• Adds SaaS connection type to SaaS yaml config
• Updates test for invalid saas type
• Updates docs and postman collection

Checklist

• Update CHANGELOG.md file
  • Merge in main so the most recent CHANGELOG.md file is being appended to
  • Add description within the Unreleased section in an appropriate category. Add a new category from the list at the top of the file if the needed one isn't already there.
  • Add a link to this PR at the end of the description with the PR number as the text. example: #1
• Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram.
• If docs updated (select one):
  • documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
  • documentation issue created (tag docs-team to complete issue separately)
• Good unit test/integration test coverage
• This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
• The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket

Fixes #706

[pattisdr]

nice job in trying to find a workable solution for everyone @eastandwestwind, just a few minor things here.

[eastandwestwind]

@pattisdr I've been struggling with a CI error during init-db related to the new migration. Seems that it may be expecting an enum for ConnectionType with raw SQL:

sqlalchemy.exc.OperationalError: (psycopg2.errors.UnsafeNewEnumValueUsage) unsafe use of new value "saas" of enum type connectiontype
LINE 1: ...on_config_id WHERE connectionconfig.connection_type = 'saas'
                                                                 ^
HINT:  New enum values must be committed before they can be used.

E.g. https://github.com/ethyca/fidesops/runs/7206676793?check_suite_focus=true

I've been testing out some theories, but let me know if you've seen this before

[pattisdr]

Unit tests were failing because we were using alter type to incrementally add to the connection_type enum but in this newest migration, we wanted to use that new enum, but it hadn't yet been commited.

I've updated older migrations to not use alter type, when updating the connectino_type enum:
https://www.postgresql.org/docs/14/sql-altertype.html

If ALTER TYPE ... ADD VALUE (the form that adds a new value to an enum type) is executed inside a transaction block, the new value cannot be used until after the transaction has been committed.

[eastandwestwind]

@pattisdr I've just pushed out the changelog update (looks like some other recent PRs have been added to the 1.6.1 section also 😢 ). Otherwise, your changes look good, thanks so much for helping me out with this!

[pattisdr]

Are you sure this is updated with main? the changelog there has more items in unreleased?

https://github.com/ethyca/fidesops/blob/c5c30840d07d2c2c4b999bdf241044690c63d092/CHANGELOG.md

[eastandwestwind]

weirdddd lemme try again

[eastandwestwind]

ok, this looks better now