CLI Tests: Deploy all Python Content Types

[kgartland-rstudio]

Intent

Type of Change

• • Bug Fix
• • New Feature
• • Breaking Change
• • Documentation
• • Refactor
• • Tooling

Approach

This PR deploys all content. All Connect Jumpstart examples are added as well as various supported APIs. It also introduces a CONTENT variable where you can specify a single piece of content rather than deploying all.

After deploying, we check the Content Type using the API. I've added a .env file to each content folder to specify the expected content type to compare against.

This PR also disables the nightly Cypress tests until we're ready to re-enable those (they're currently failing).

Automated Tests

These are them.

Directions for Reviewers

The deployments will only run during the Nightly tests, these are passing here:

https://github.com/posit-dev/publisher/actions/runs/7544245350/job/20537305258

This PR has 91 files but most of those are the added contents, feel free to ignore anything in the test/sample-content/python folder.

Checklist

• I have updated CHANGELOG.md to cover notable changes.

[dotNomad]

I did not fully review this but:

• looks like you have some duplicate commits in here perhaps something got a bit messed up in Git
• we are adding some large files including images in this PR, should we consider separating this out to avoid bloating the size of this repo?

[kgartland-rstudio]

• we are adding some large files including images in this PR, should we consider separating this out to avoid bloating the size of this repo?

The sample content was pulled in from the Jumpstart examples from Connect. I removed the images and README files, good catch.

[kgartland-rstudio]

• looks like you have some duplicate commits in here perhaps something got a bit messed up in Git

I think I had to pull in changes from main at one point, is that what you mean? Other than that, I did have some trouble getting the tests to work in CI with Windows so I may have made the same commit comment multiple times.

[dotNomad]

I think I had to pull in changes from main at one point, is that what you mean? Other than that, I did have some trouble getting the tests to work in CI with Windows so I may have made the same commit comment multiple times.

I'm looking at the commits in the PR you have commits you have written, but also some from me and Taylor. Like the HTML5 history one has a different SHA than the commit on main (f1cdb744f9a5399a071aaaa12d5d04214dd7b776 vs 028dd33643682c7ff580ba1715c470a2ebfa1bc6). This tells me something incorrectly was done with a merge, cherry pick, or where branching occurs. I can definitely help clean this up if you'd like to avoid the duplication of commits on merge (due to the duplicate SHAs)

[dotNomad]

The sample content was pulled in from the Jumpstart examples from Connect. I removed the images and README files, good catch.

Thanks for removing these. I never like to include non-code like images in a repo if it can be helped. I've worked with too many multiple GBs repos in the past that felt so sluggish due to this.

[tdstein]

The sample content was pulled in from the Jumpstart examples from Connect. I removed the images and README files, good catch.

Thanks for removing these. I never like to include non-code like images in a repo if it can be helped. I've worked with too many multiple GBs repos in the past that felt so sluggish due to this.

Should we have a separate repository for sample content? Is there an advantage to reusing the sample content across this project and Connect?

Also, if necessary, we can place large non-text files in S3.

[mmarchetti]

It would be good to squash this PR when merging so the images won't be included (a regular merge will preserve the commit that added them and the commit that removed them).

[kgartland-rstudio]

Since we have all of this content in Connect, I could do a sparse-checkout from Connect and get the examples folder where the Jumpstart examples are stored.

Also for context, I'm using the Jumpstart examples because we publish those in the Connect product as examples for customers so we'll want to make sure those work with the publisher.

[dotNomad]

It would be good to squash this PR when merging so the images won't be included (a regular merge will preserve the commit that added them and the commit that removed them).

Since we have all of this content in Connect, I could do a sparse-checkout from Connect and get the examples folder where the Jumpstart examples are stored.

Perhaps it would be best to close up this PR, and re-branch for the new work if we will be grabbing the sample content from Connect.

[mmarchetti]

Can this be closed now that #926 is open?

[kgartland-rstudio]

Can this be closed now that #926 is open?

Yup! Closing...