Release v3.0.1

[joshmarsh]

Proposed changes

• Moved quick start to readthedocs
• Download deployment assets from the public url rather than using Github's GraphQL API

Types of changes

• [x] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Refactor (changes to code, which do not change application behavior)

Checklist

• [x] I have filled out this PR template
• [x] I have read the CONTRIBUTING doc
• [ ] I have added automated tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (README.md, inline comments, etc.)
• [x] I have updated the CHANGELOG.md under a ## next release, with a short summary of my changes

Relevant Links

Further comments

[eschwartz]

@joshmarsh -- you mentioned offline that this would resolve https://github.com/Optum/dce/issues/209

Can you provide more details? What's the deal with those s3 policies, and how does this release fix it?

[joshmarsh]

Good clarifying question, and it looks like there may actually be a deeper issue here.

This release solves the issue of the Github v4 API requiring a personal access token to download deployment artifacts, and I suspect that’s what caused the failure that lead to https://github.com/Optum/dce/issues/209 being noticed.

I don’t have an answer right now, so let’s mark this as a bug and revisit it after https://github.com/Optum/dce-cli/pull/59 is merged. As a cursory observation, I don’t see the MalformedPolicy error present in the deployment logs from https://github.com/Optum/dce-cli/pull/59.